ok i have sent a message to [email protected] to see if
they can help
On 26/11/2017 14:22, Romain Manni-Bucau wrote:
guess taglib community will have a more relevant feedback but that's
what I had in mind at least, yes
avoiding it in tomee means either removing the libs or deactivating
the auto registration but none of these solutions are really stable
and reliable on the long term.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-26 13:28 GMT+01:00 Matthew Broadhead <[email protected]>:
sorry i meant javax.xml.*
On 26/11/2017 13:21, Matthew Broadhead wrote:
not really sure what XalanUtil.getContext is doing
public static XPathContext getContext(Tag child, PageContext pageContext)
{
// if within a forEach tag, use its context
ForEachTag forEachTag = (ForEachTag)
TagSupport.findAncestorWithClass(child, ForEachTag.class);
if (forEachTag != null) {
return forEachTag.getContext();
}
// otherwise, create a new context referring to an empty document
XPathContext context = new XPathContext(false);
VariableStack variableStack = new JSTLVariableStack(pageContext);
context.setVarStack(variableStack);
int dtm =
context.getDTMHandleFromNode(XmlUtil.newEmptyDocument());
context.pushCurrentNodeAndExpression(dtm, dtm);
return context;
}
seems to be returning a document fragment but I am not familiar with what
a VariableStack is or does. it feels like i can replace everything with
jaxa.xml.* but this function needs clarification
another question...i don't even use jsp (only jsf) so is there someway to
remove or disable it in TomEE and this will avoid the whole issue?
On 25/11/2017 18:40, Romain Manni-Bucau wrote:
tomcat doesnt, taglib does implicitly
you can try to hack openejb.classloader properties to make it work -
without any guarantees
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-25 17:26 GMT+01:00 Matthew Broadhead
<[email protected]>:
does tomcat still ship with Xalan as a dependency? if so can we just
use
that? i don't really understand what is causing the error. is there
some
way i can get the correct instance of DTMManager from the classloader?
java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
cannot be cast to org.apache.xml.dtm.DTMManager
at org.apache.xml.dtm.DTMManager.newInstance(DTMManager.java:137)
at org.apache.xpath.XPathContext.<init>(XPathContext.java:102)
at org.apache.xpath.XPathContext.<init>(XPathContext.java:349)
at org.apache.xpath.XPathContext.<init>(XPathContext.java:337)
at
org.apache.xalan.transformer.TransformerImpl.<init>(TransformerImpl.java:397)
at
org.apache.xalan.templates.StylesheetRoot.newTransformer(StylesheetRoot.java:200)
On 21/11/2017 11:53, Romain Manni-Bucau wrote:
depends the perfs. If javax gives the same no need of xalan, otherwise
we would need some flag.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-21 11:52 GMT+01:00 Matthew Broadhead
<[email protected]>:
should xalan be available through some route or does everything need
switching to some generic xml parser like javax.xml.xpath.XPath
On 21/11/2017 11:28, Romain Manni-Bucau wrote:
yes, that's the ones to fix - make it compiling + validate perfs are
still ok.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-21 11:25 GMT+01:00 Matthew Broadhead
<[email protected]>:
it is imported in these ones in main as well as loads in test
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ExprSupport.java:28:import
org.apache.xpath.XPath;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ExprSupport.java:29:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ForEachTag.java:26:import
org.apache.xpath.XPath;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ForEachTag.java:27:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/ForEachTag.java:28:import
org.apache.xpath.objects.XObject;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/IfTag.java:24:import
org.apache.xpath.XPath;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/IfTag.java:25:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/JSTLVariableStack.java:29:import
org.apache.xpath.VariableStack;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/JSTLVariableStack.java:30:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/JSTLVariableStack.java:31:import
org.apache.xpath.objects.XObject;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/JSTLVariableStack.java:32:import
org.apache.xpath.objects.XObjectFactory;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/SetTag.java:27:import
org.apache.xpath.XPath;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/SetTag.java:28:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/SetTag.java:29:import
org.apache.xpath.objects.XObject;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/WhenTag.java:24:import
org.apache.xpath.XPath;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/WhenTag.java:25:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:25:import
org.apache.xpath.VariableStack;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:26:import
org.apache.xpath.XPathContext;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:27:import
org.apache.xpath.objects.XBoolean;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:28:import
org.apache.xpath.objects.XNodeSet;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:29:import
org.apache.xpath.objects.XNumber;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:30:import
org.apache.xpath.objects.XObject;
./impl/src/main/java/org/apache/taglibs/standard/tag/common/xml/XalanUtil.java:31:import
org.apache.xpath.objects.XString;
On 21/11/2017 11:17, Romain Manni-Bucau wrote:
No, you see this stack cause the test cant be loaded but it is in
several classes of taglib project, XalanUtil and a few others.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-21 11:14 GMT+01:00 Matthew Broadhead
<[email protected]>:
so do i need to replace it with something else? is that inside
ReflectionUtils?
On 21/11/2017 11:08, Romain Manni-Bucau wrote:
That's the one, org.apache.xpath is provided by xalan (don't ask
me
why xalan is not in the name ;))
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-21 10:57 GMT+01:00 Matthew Broadhead
<[email protected]>:
mvn install outputs this:
org.apache.maven.surefire.util.SurefireReflectionException:
java.lang.reflect.InvocationTargetException; nested exception is
java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: java.lang.NoClassDefFoundError:
org/apache/xpath/VariableStack
at java.lang.Class.getDeclaredMethods0(Native Method)
at
java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at
java.lang.Class.privateGetMethodRecursive(Class.java:3048)
at java.lang.Class.getMethod0(Class.java:3018)
at java.lang.Class.getMethod(Class.java:1784)
at
org.apache.maven.surefire.util.ReflectionUtils.tryGetMethod(ReflectionUtils.java:57)
at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.isSuiteOnly(JUnit3TestChecker.java:64)
at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.isValidJUnit3Test(JUnit3TestChecker.java:59)
at
org.apache.maven.surefire.common.junit3.JUnit3TestChecker.accept(JUnit3TestChecker.java:54)
at
org.apache.maven.surefire.common.junit4.JUnit4TestChecker.accept(JUnit4TestChecker.java:51)
at
org.apache.maven.surefire.util.DefaultDirectoryScanner.locateTestClasses(DefaultDirectoryScanner.java:84)
at
org.apache.maven.surefire.junit4.JUnit4Provider.scanClassPath(JUnit4Provider.java:186)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:93)
... 9 more
Caused by: java.lang.ClassNotFoundException:
org.apache.xpath.VariableStack
at
java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang
On 21/11/2017 10:53, Matthew Broadhead wrote:
Hi Romain,
the dependency is listed in each pom.xml in
- compat
- impl
- jstlel
- standard-test
it is listed as provided in all of them except standard-test.
would i just remove all references and then do a mvn install to
check
the
output?
Matthew
On 21/11/2017 10:38, Romain Manni-Bucau wrote:
Hi Matthew,
if you checkout
https://svn.apache.org/repos/asf/tomcat/taglibs/standard/trunk
and
drop xalan dependency you should be on track. You can have a
look
to
XalanUtil class but the xalan dependency is mainly here for
XPath
usage IIRC. There are some replacements in the JRE so it
should
be
the
way to go I think.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-21 10:27 GMT+01:00 Matthew Broadhead
<[email protected]>:
hi rmannibucau,
i tried to contact you by IRC about this. i am ready to
continue
after
a
busy period.
what do you mean about moving up the svn tree?
On 11/10/2017 09:06, Romain Manni-Bucau wrote:
There are imports in .java but you need to move up in the
svn
tree
IIRC
Le 11 oct. 2017 07:59, "Matthew Broadhead"
<[email protected]>
a écrit :
just the ones from the poms? the target and .svn ones can
be
ignored?
Mac-mini-2:apache-taglibs matthewbroadhead$ grep -rnw '.'
-e
'xalan'
./rdc/.svn/pristine/36/3681b927c636bd3adf5237f40af67c9742b9f76b.svn-base:45:
xmlns:xalan="http://xml.apache.org/xslt";
./rdc/.svn/pristine/36/3681b927c636bd3adf5237f40af67c9742b9f76b.svn-base:52:
xalan:indent-amount="2"/>
./rdc/taglibs-rdc/src/main/tld/taglibs-rdc.tld:7: <taglib
xmlns:xalan="
http://xml.apache.org/xslt"; xmlns:xsi="http://www.w3.org/2
001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/j2ee";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd";
version="2.0">
./rdc/taglibs-rdc/src/util/tld20.xsl:45:
xmlns:xalan="http://xml.apache
.org/xslt"
./rdc/taglibs-rdc/src/util/tld20.xsl:52:
xalan:indent-amount="2"/>
./rdc/taglibs-rdc/target/classes/META-INF/DEPENDENCIES:18:
-
xalan
xalan:xalan:jar:2.5.1
./rdc/taglibs-rdc/target/classes/META-INF/taglibs-rdc.tld:7:
<taglib
xmlns:xalan="http://xml.apache.org/xslt";
xmlns:xsi="http://www.w3.org/2
001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/j2ee";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd";
version="2.0">
./rdc/taglibs-rdc/target/maven-shared-archive-resources/META-INF/DEPENDENCIES:18:
- xalan xalan:xalan:jar:2.5.1
./rdc/taglibs-rdc/target/test-classes/META-INF/DEPENDENCIES:18:
-
xalan
xalan:xalan:jar:2.5.1
./rdc/taglibs-rdc-dist/target/maven-shared-archive-resources/META-INF/DEPENDENCIES:18:
- xalan xalan:xalan:jar:2.5.1
Binary file
./rdc/taglibs-rdc-dist/target/taglibs-rdc-dist-1.1-SNAPSHOT-bin.tar.gz
matches
Binary file
./rdc/taglibs-rdc-dist/target/taglibs-rdc-dist-1.1-SNAPSHOT-bin.zip
matches
./rdc/taglibs-rdc-examples/target/classes/META-INF/DEPENDENCIES:14:
-
xalan xalan:xalan:jar:2.5.1
./rdc/taglibs-rdc-examples/target/maven-shared-archive-resources/META-INF/DEPENDENCIES:14:
- xalan xalan:xalan:jar:2.5.1
./rdc/taglibs-rdc-examples/target/taglibs-rdc-examples-1.1-
SNAPSHOT/WEB-INF/classes/META-INF/DEPENDENCIES:14: - xalan
xalan:xalan:jar:2.5.1
Binary file
./rdc/taglibs-rdc-examples/target/taglibs-rdc-examples-1.1-
SNAPSHOT/WEB-INF/lib/xalan-2.5.1.jar matches
Binary file
./rdc/taglibs-rdc-examples/target/taglibs-rdc-examples-1.1-SNAPSHOT.war
matches
./rdc/taglibs-rdc-examples/target/test-classes/META-INF/DEPENDENCIES:14:
- xalan xalan:xalan:jar:2.5.1
./standard/.svn/pristine/08/08170df2a64cad924ad41ed7a83f549a7f932c8d.svn-base:47:50462
xalan import should not be optional in maven-bundle-plugin
./standard/.svn/pristine/09/09b81f3124eb457e32dbf676ed709ff97642b38c.svn-base:93:
<groupId>xalan</groupId>
./standard/.svn/pristine/09/09b81f3124eb457e32dbf676ed709ff97642b38c.svn-base:94:
<artifactId>xalan</artifactId>
./standard/.svn/pristine/23/2358183c62068e9fbc86b63a7b01532e05591222.svn-base:95:
<groupId>xalan</groupId>
./standard/.svn/pristine/23/2358183c62068e9fbc86b63a7b01532e05591222.svn-base:96:
<artifactId>xalan</artifactId>
./standard/.svn/pristine/2e/2eceffae8d205d2aa5e85d3a199c7332fe364173.svn-base:21:
* [lifted from xalan]
./standard/.svn/pristine/6b/6ba3a3954445faf3617d6988104909c332ddc2df.svn-base:99:
<groupId>xalan</groupId>
./standard/.svn/pristine/6b/6ba3a3954445faf3617d6988104909c332ddc2df.svn-base:100:
<artifactId>xalan</artifactId>
./standard/.svn/pristine/b5/b503d369c07bf237404c1f63f5aa1d3319242531.svn-base:36:
- xalan-2.7.1.jar
./standard/.svn/pristine/b5/b503d369c07bf237404c1f63f5aa1d3319242531.svn-base:47:
- xalan-2.7.1.jar
./standard/.svn/pristine/f7/f7d9123b300f031d838d59a618167a9828ee79be.svn-base:100:
<groupId>xalan</groupId>
./standard/.svn/pristine/f7/f7d9123b300f031d838d59a618167a9828ee79be.svn-base:101:
<artifactId>xalan</artifactId>
./standard/CHANGES.txt:47:50462 xalan import should not be
optional
in
maven-bundle-plugin
./standard/compat/pom.xml:99: <groupId>xalan</groupId>
./standard/compat/pom.xml:100:
<artifactId>xalan</artifactId>
./standard/impl/pom.xml:95: <groupId>xalan</groupId>
./standard/impl/pom.xml:96: <artifactId>xalan</artifactId>
./standard/impl/src/main/java/org/apache/taglibs/standard/Version.java:21:
* [lifted from xalan]
./standard/jstlel/pom.xml:100: <groupId>xalan</groupId>
./standard/jstlel/pom.xml:101:
<artifactId>xalan</artifactId>
./standard/README_bin.txt:36: - xalan-2.7.1.jar
./standard/README_bin.txt:47: - xalan-2.7.1.jar
./standard/standard-test/pom.xml:93:
<groupId>xalan</groupId>
./standard/standard-test/pom.xml:94:
<artifactId>xalan</artifactId>
On 11/10/2017 00:12, Romain Manni-Bucau wrote:
Yes
Le 10 oct. 2017 21:21, "Matthew Broadhead"
<[email protected]
k>
a écrit :
ok i cloned and built. but what am i supposed to do?
remove
all
xalan
refs?
On 10/10/2017 19:10, Romain Manni-Bucau wrote:
If I'm not mistaken this should be up to date
http://tomcat.apache.org/taglibs/site/building.html
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <
https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
2017-10-10 19:08 GMT+02:00 Matthew Broadhead <
[email protected]
:
is that something i can take a look at? is it in
openejb?
On 10/10/2017 18:21, Romain Manni-Bucau wrote:
Yes fix taglib as identified since last year ;)
Le 10 oct. 2017 16:05, "Matthew Broadhead"
<[email protected]
k>
a écrit :
is there a cure for this? we previously tried to
exclude
other
versions
of xalan from the pom but it didn't work
On 10/10/2017 16:33, Romain Manni-Bucau wrote:
Yep
It is one of the reasons why we dont want xalan in
tomee
lib
folder
-
fop
is not particular since xalan is very common
Le 10 oct. 2017 15:03, "Matthew Broadhead"
<[email protected]
k>
a écrit :
with 7.0.4 i am getting this
java.lang.ClassCastException:
org.apache.xml.dtm.ref.DTMMana
gerDefault
cannot be cast to org.apache.xml.dtm.DTMManager
at org.apache.xml.dtm.DTMManager.
newInstance(DTMManager.java:13
7)
at org.apache.xpath.XPathContext.
<init>(XPathContext.java:102)
at org.apache.xpath.XPathContext.
<init>(XPathContext.java:349)
at org.apache.xpath.XPathContext.
<init>(XPathContext.java:337)
at org.apache.xalan.transformer.T
ransformerImpl.<init>(Transfor
merImpl.java:397)
at org.apache.xalan.templates.Sty
lesheetRoot.newTransformer(Sty
lesheetRoot.java:200)
with 7.0.3 it happened sometimes if i redeployed a
webapp.
Romain
said
it
was the class loader mixing xalan versions. i
include
apache
fop
in
one
of
my projects in case that helps but mostly try to
stick
to
TomEE
stack
On 09/10/2017 17:24, Jonathan Gallimore wrote:
That's awesome, thank you for the feedback so far!
Jon
On Mon, Oct 9, 2017 at 4:22 PM, Matthew Broadhead
<
[email protected]> wrote:
Hi Jon,
That is good as I wanted to test the 7.0.4 with my
development
setup.
So
I downloaded the apache-tomee-7.0.4-plus.tar.gz
and
i
am
running
it
on
my
local machine in place of 7.0.3.
It has started up fine and no problems so far. I
will
just
keep
working
and report back if there are any issues
Matthew
On 09/10/2017 17:14, Jonathan Gallimore wrote:
Hi
That's the staging repo for the vote - if the
vote
passes,
its
those
binaries that will be promoted as version 7.0.4.
Snapshots
won't
be
deployed here (they'll go to here:
https://repository.apache.org/content/groups/snapshots/
I
believe). I
think
there is an issue with the buildbot job that
deploys
these,
so
if
you're
waiting on a snapshot, let us know and I can
deploy
one
manually.
Jon
On Mon, Oct 9, 2017 at 4:07 PM, Matthew
Broadhead <
[email protected]> wrote:
are the dist builds still at
https://dist.apache.org/repos/
dist/dev/tomee/staging-1107/tomee-7.0.4/?
On 09/10/2017 14:58, Mark Struberg wrote:
Hi folks!
Sorry for the delay!
Running the new 7.0.4 attempt with a few
customer
projects
now.
Will ping back once I know more.
txs and LieGrue,
strub
Am 08.10.2017 um 16:43 schrieb Romain
Manni-Bucau
<
[email protected]
:
It is http://repository.apache.org/snapshots/
(openejb.deployer.snapshot.repository
system property) but there is not yet a 8
snapshot
Romain Manni-Bucau
@rmannibucau
<https://twitter.com/rmannibucau> |
Blog
<https://rmannibucau.metawerx.net/> | Old
Blog
<http://rmannibucau.wordpress.com> | Github <
https://github.com/rmannibucau> |
LinkedIn
<https://www.linkedin.com/in/rmannibucau>
2017-10-08 16:26 GMT+02:00 Alex The Rocker <
[email protected]
:
Hi Romain,
But how to find the repo for TomEE 8.0.0
based
testing?
Best regards,
Alexandre
2017-10-08 16:20 GMT+02:00 Romain
Manni-Bucau <
[email protected]
:
Hi Alex,
you can set as system property (through
surefire)
openejb.deployer.repository=<the
repo>
Romain Manni-Bucau
@rmannibucau
<https://twitter.com/rmannibucau>
|
Blog
<https://rmannibucau.metawerx.net/> | Old
Blog
<http://rmannibucau.wordpress.com> | Github
<
https://github.com/
rmannibucau> |
LinkedIn
<https://www.linkedin.com/in/rmannibucau>
2017-10-08 14:07 GMT+02:00 Alex The Rocker
<
[email protected]
:
Hi Romain,
Thank you very much for your answer:I was
able
to
run
my
Arquilian
test by adding the following line into my
projet's
pom.xml:
<repositories>
<repository>
<id>my-tomee704repo</id>
<name>TomEE704 repo</name>
<url>https://repository.apach
e.org/content/
repositories/orgapachetomee-1107/</url>
</repository>
</repositories>
(and by the way my feedback on TomEE 7.0.4
is
still
+1)
Question: in the general case, how one can
tell
which
is
the
appropriate repository URL to use
Arquilian
which
a
TomEE+
version
which isn't yet officialized?
For example, if I want to try TomEE+
8.0.0,
the
above
repository
does't allow to resolve dependencies on:
<dependency>
<groupId>org.apache.tomee</gr
oupId>
<artifactId>arquillian-tomee-e
mbedded</artifactId>
<version>8.0.0</version>
<!--Current
version
-->
</dependency>
So what's the "rule of thumb"? (and can it
be
documented
somewhere
on
tomee.apache.org?)
Best regards,
Alexandre
2017-10-08 10:51 GMT+02:00 Romain
Manni-Bucau
<
[email protected]
:
@Alex: did you add this repo
https://repository.apache.org/
content/repositories/orgapachetomee-1107/
?
Romain Manni-Bucau
@rmannibucau
<https://twitter.com/rmannibucau>
|
Blog
<https://rmannibucau.metawerx.net/> | Old
Blog
<http://rmannibucau.wordpress.com> |
Github
<
https://github.com/
rmannibucau> |
LinkedIn
<https://www.linkedin.com/in/rmannibucau>
2017-10-08 10:48 GMT+02:00 Alex The
Rocker <
[email protected]
:
Hello,
I am starting to use Arquilian, in
particular
in
order
to
check
the
impact of TomEE+ version changes on our
REST
services
(annotations
sometimes change, such as the
introduction
of
@JohnzonIgnore
in
TomEE
+ 7.x).
I naively tried changing my dependency
from
7.0.3
to
7.0.4,
but
it's
not being resolved:
<dependency>
<groupId>org.apache.tomee</gr
oupId>
<artifactId>arquillian-tomee-
embedded</artifactId>
<version>7.0.4</version>
<!--Current
version
-->
</dependency>
I guess that this is because TomEE 7.0.4
isn't
yet
officialized.
But yet, I fell that it would be great if
I
could
use
the
current
TomEE+ 7.0.4 release candidate with
Arqulian
in
order
to
give
feedback
on this RC before it's final.
What would be the simplest way to setup
my
pom.xml
in
order
to
run
my
Arquilan tests using latest TomEE+ 7.0.4
release
candidate,
*using
the
embedded adapter* ?
(I guess that using the remote adapter
with
the
RC
I
downloaded
is
an
alternative, but yet I want also the use
embedded
version).
Best regards,
Alexandre
2017-10-05 19:29 GMT+02:00 Alex The
Rocker
<
[email protected]
:
Hello Andy,
And thank you very much for your
answer. I
already
voted
a
+1
based on
my applicative tests which showed no
regressions
of
this
TomEE+
7.0.4
vs. TomEE+ 7.0.3.
I can wait for a week for the "final
freeze"
:)
Best regards,
Alexandre
2017-10-05 19:25 GMT+02:00 Andy Gumbrecht
<
[email protected]
:
The vote is open for 'at least' 72
hours,
or
until
we
get
3+
binding
votes.
I know that many of the guys are ultra
busy
with
JavaOne at
the
moment,
so I
don't expect to get a response until next
week.
The review process is basically
downloading
the
binaries
and
checking
them
for complete functionality. That
includes
running
apps
and
testing
everything possible, including the legal
headers
etc.
This
always
takes
time, but we do it to ensure you get a
good
distribution.
Thanks for your understanding. We
still
really
appreciate
your
help
and
votes, which should mean that you have
just
as
thoroughly
tested
all
your
environments. The more eyes on, the
better!
Andy Gumbrecht.
I'm adding my binding vote, as I have not
found
any
issues:
+1
On 04/10/17 00:42, Alex The Rocker
wrote:
Hello Andy
Would you please specific until when
this
vote
for
TomEE+
7.0.4
is
supposed to last?
Best regards,
Alex
2017-09-28 13:37 GMT+02:00 Felipe Jaekel
<
[email protected]
:
+1
2017-09-26 18:24 GMT-03:00 Andy
Gumbrecht
<
[email protected]>:
Hi Everyone,
I'd kindly like to ask you all to
take
a
look
at
this
build
and
place
your
votes for a 7.0.4 release.
The re-roll updates to CXF 3.1.13 and
JAXB
2.3.0
(Provided).
I added comments in the previous vote
that
relate
to
Java
9,
which is
experimental and requires the
following
(corrected)
flag:
--add-module java.xml.bind
Staging repo:
https://repository.apache.org/content/repositories/
orgapachetomee-1107/
Source zip:
https://repository.apache.org/
content/repositories/orgapache
tomee-1107/org/apache/tomee/to
mee-project/7.0.4/tomee-
project-7.0.4-source-release.zip
Dist area:
https://dist.apache.org/repos/
dist/dev/tomee/staging-1107/
tomee-7.0.4/
Legal:
https://dist.apache.org/repos/
dist/dev/tomee/staging-1107/to
mee-7.0.4/legal.zip
Keys:
https://dist.apache.org/repos/
dist/release/tomee/KEYS
Changelog:
https://issues.apache.org/jira
/secure/ReleaseNote.jspa?proje
ctId=12312320&version=12339959
Green buildbot:
https://ci.apache.org/builders/tomee-trunk-ubuntu-
jvm8/builds/725
https://ci.apache.org/builders
/tomee-trunk-ubuntu/builds/839
The RAT report indicates 0 Unknown
Licenses.
Please vote:
+1: Release
-1 Do not release because ...
See
below.
If you vote -1 then please create a
JIRA
ticket
here:
https://issues.apache.org/jira/projects/TOMEE
-
Include
as
much
information as possible and, if
applicable,
a
unit
test.
The vote will be open for 3 days or
the
consensus
is
binding
(At
least 3
binding votes).
Everyone, committer or not, is
encouraged
to
test
and
vote.
Thank
you
very
much for your time.
Andy Gumbrecht.
