You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/07/04 07:28:34 UTC
[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still
Failing
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/96/
No tests ran.
Build Log:
[...truncated 33246 lines...]
prepare-release-no-sign:
[mkdir] Created dir: /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeRelease
[copy] Copying 416 files to /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeRelease/lucene
[copy] Copying 185 files to /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeRelease/solr
[exec] JAVA7_HOME is /home/hudson/tools/java/latest1.7
[exec] NOTE: output encoding is US-ASCII
[exec]
[exec] Load release URL "file:/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeRelease/"...
[exec]
[exec] Test Lucene...
[exec] test basics...
[exec] get KEYS
[exec] 0.1 MB in 0.01 sec (10.8 MB/sec)
[exec] check changes HTML...
[exec] download lucene-5.0.0-src.tgz...
[exec] 26.6 MB in 0.04 sec (672.0 MB/sec)
[exec] verify md5/sha1 digests
[exec] download lucene-5.0.0.tgz...
[exec] 48.5 MB in 0.07 sec (674.5 MB/sec)
[exec] verify md5/sha1 digests
[exec] download lucene-5.0.0.zip...
[exec] 57.9 MB in 0.07 sec (885.4 MB/sec)
[exec] verify md5/sha1 digests
[exec] unpack lucene-5.0.0.tgz...
[exec] verify JAR/WAR metadata...
[exec] test demo with 1.7...
[exec] got 5506 hits for query "lucene"
[exec] check Lucene's javadoc JAR
[exec] unpack lucene-5.0.0.zip...
[exec] verify JAR/WAR metadata...
[exec] test demo with 1.7...
[exec] got 5506 hits for query "lucene"
[exec] check Lucene's javadoc JAR
[exec] unpack lucene-5.0.0-src.tgz...
[exec] make sure no JARs/WARs in src dist...
[exec] run "ant validate"
[exec] run tests w/ Java 7 and testArgs='-Dtests.jettyConnector=Socket'...
[exec] test demo with 1.7...
[exec] got 210 hits for query "lucene"
[exec] generate javadocs w/ Java 7...
[exec]
[exec] Crawl/parse...
[exec]
[exec] Verify...
[exec]
[exec] Test Solr...
[exec] test basics...
[exec] get KEYS
[exec] 0.1 MB in 0.00 sec (46.1 MB/sec)
[exec] check changes HTML...
[exec] download solr-5.0.0-src.tgz...
[exec] 30.5 MB in 0.08 sec (369.7 MB/sec)
[exec] verify md5/sha1 digests
[exec] download solr-5.0.0.tgz...
[exec] 105.9 MB in 0.22 sec (478.4 MB/sec)
[exec] verify md5/sha1 digests
[exec] download solr-5.0.0.zip...
[exec] 110.6 MB in 0.21 sec (525.3 MB/sec)
[exec] verify md5/sha1 digests
[exec] unpack solr-5.0.0.tgz...
[exec] verify JAR/WAR metadata...
[exec] **WARNING**: skipping check of /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/contrib/dataimporthandler/lib/mail-1.4.1.jar: it has javax.* classes
[exec] **WARNING**: skipping check of /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/contrib/dataimporthandler/lib/activation-1.1.jar: it has javax.* classes
[exec] Traceback (most recent call last):
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 1406, in <module>
[exec] main()
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 1350, in main
[exec] smokeTest(baseURL, svnRevision, version, tmpDir, isSigned, testArgs)
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 1394, in smokeTest
[exec] unpackAndVerify('solr', tmpDir, artifact, svnRevision, version, testArgs)
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 598, in unpackAndVerify
[exec] verifyUnpacked(project, artifact, unpackPath, svnRevision, version, testArgs)
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 723, in verifyUnpacked
[exec] checkAllJARs(os.getcwd(), project, svnRevision, version)
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 272, in checkAllJARs
[exec] noJavaPackageClasses('JAR file "%s"' % fullPath, fullPath)
[exec] File "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/dev-tools/scripts/smokeTestRelease.py", line 169, in noJavaPackageClasses
[exec] raise RuntimeError('%s contains sheisty class "%s"' % (desc, name2))
[exec] RuntimeError: JAR file "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar" contains sheisty class "javax/ws/rs/ApplicationPath.class"
BUILD FAILED
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/build.xml:306: exec returned: 1
Total time: 39 minutes 12 seconds
Build step 'Invoke Ant' marked build as failure
Email was triggered for: Failure
Sending email for trigger: Failure
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Mark Miller <ma...@gmail.com>.
On Jul 4, 2013, at 11:02 AM, "Uwe Schindler" <uw...@thetaphi.de> wrote:
> If we expose this JAR file as part of Solr,
It's not shipped as part of Solr - it's a test dependency. Take a look before you go nuts.
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Uwe Schindler <uw...@thetaphi.de>.
The additional problem now: If we expose this JAR file as part of Solr, it is incompatible to Java Enterprise! A classpath clash would occur leading to unexpected behavior in maybe other modules that expect the original (and maybe newer/older implementation as part of the EnterpiseJDK).
Like a WAR is not allowed to contain a servlet.jar (and the webapp container hides it from the WebappClassloader), this should also not be installed. The user should install it manually!
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Uwe Schindler [mailto:uwe@thetaphi.de]
Sent: Thursday, July 04, 2013 4:55 PM
To: dev@lucene.apache.org
Subject: RE: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Caused by Slowdoop commit of Mark Miller! This classes are used by Java Enterprise Edition, should never be used on a Client VM (my opinion). If somebody wants to run Slowdoop, use an Enterprise JDK.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Robert Muir [mailto:rcmuir@gmail.com]
Sent: Thursday, July 04, 2013 4:51 PM
To: dev@lucene.apache.org
Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
When was this dependency introduced? Is it really needed?
The smoketesting has been failing for days because of this.
On Thu, Jul 4, 2013 at 1:28 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
[exec] raise RuntimeError('%s contains sheisty class "%s"' % (desc, name2))
[exec] RuntimeError: JAR file "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar" contains sheisty class "javax/ws/rs/ApplicationPath.class"
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
I committed a fix, but there are more problems with the smoke-checking
(problems with NOTICE.txt). Its just now the checker makes it further along.
I can look at it tomorrow maybe, its way past beer time.
On Thu, Jul 4, 2013 at 11:46 AM, Robert Muir <rc...@gmail.com> wrote:
> I will exclude this file from the smoke tester then. I just have to wait
> until it succeeds locally because my python is not very good.
>
>
> On Thu, Jul 4, 2013 at 11:14 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
>
>> Hi,
>>
>> I have no problem with it i fit is *not* part oft he WAR or the example
>> folder's lib! If it would be it would be a bug!
>>
>> In general we should split all JARs needed for "compilation" and those
>> for "test runtime" and "production runtime" by 3 different configurations.
>> The test runtime is only added to classpath when tests are ran. The
>> production env is used for building the webapp/example app. The compile
>> classpath only contains direct dependencies, no transient ones.
>>
>> See e.g. forbidden-apis as an example. It splits those classpaths
>> completely (and uses ivy:cachepath for classpath / ivy:cachefileset for
>> packaging zips).
>>
>> -----
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>>
>> > -----Original Message-----
>> > From: Mark Miller [mailto:markrmiller@gmail.com]
>> > Sent: Thursday, July 04, 2013 5:09 PM
>> > To: dev@lucene.apache.org
>> > Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 -
>> Still
>> > Failing
>> >
>> >
>> > On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
>> >
>> > >> we could solve that with an ivy configuration for 'tests' instead
>> >
>> > Or perhaps solved by that? I don't really know what you are suggesting
>> > though - ivy is half as mysterious as maven to me.
>> >
>> > - Mark
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For
>> additional
>> > commands, e-mail: dev-help@lucene.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
I will exclude this file from the smoke tester then. I just have to wait
until it succeeds locally because my python is not very good.
On Thu, Jul 4, 2013 at 11:14 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi,
>
> I have no problem with it i fit is *not* part oft he WAR or the example
> folder's lib! If it would be it would be a bug!
>
> In general we should split all JARs needed for "compilation" and those for
> "test runtime" and "production runtime" by 3 different configurations. The
> test runtime is only added to classpath when tests are ran. The production
> env is used for building the webapp/example app. The compile classpath only
> contains direct dependencies, no transient ones.
>
> See e.g. forbidden-apis as an example. It splits those classpaths
> completely (and uses ivy:cachepath for classpath / ivy:cachefileset for
> packaging zips).
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
> > -----Original Message-----
> > From: Mark Miller [mailto:markrmiller@gmail.com]
> > Sent: Thursday, July 04, 2013 5:09 PM
> > To: dev@lucene.apache.org
> > Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 -
> Still
> > Failing
> >
> >
> > On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
> >
> > >> we could solve that with an ivy configuration for 'tests' instead
> >
> > Or perhaps solved by that? I don't really know what you are suggesting
> > though - ivy is half as mysterious as maven to me.
> >
> > - Mark
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
> > commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
On Thu, Jul 4, 2013 at 11:14 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi,
>
> I have no problem with it i fit is *not* part oft he WAR or the example
> folder's lib! If it would be it would be a bug!
>
> In general we should split all JARs needed for "compilation" and those for
> "test runtime" and "production runtime" by 3 different configurations. The
> test runtime is only added to classpath when tests are ran. The production
> env is used for building the webapp/example app. The compile classpath only
> contains direct dependencies, no transient ones.
>
> See e.g. forbidden-apis as an example. It splits those classpaths
> completely (and uses ivy:cachepath for classpath / ivy:cachefileset for
> packaging zips).
>
And this is also much easier to implement if you are using
ivy:cachepath/cachefileset. As long as we have lib/ directories, its harder
because then we would have to add additional ones and make things more
complicated.
On the other hand, the cachepath/fileset is faster and does still work with
IDEs (at least with intellij and eclipse IDEs it seems, but you need ivyDE).
RE: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
I have no problem with it i fit is *not* part oft he WAR or the example folder's lib! If it would be it would be a bug!
In general we should split all JARs needed for "compilation" and those for "test runtime" and "production runtime" by 3 different configurations. The test runtime is only added to classpath when tests are ran. The production env is used for building the webapp/example app. The compile classpath only contains direct dependencies, no transient ones.
See e.g. forbidden-apis as an example. It splits those classpaths completely (and uses ivy:cachepath for classpath / ivy:cachefileset for packaging zips).
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Mark Miller [mailto:markrmiller@gmail.com]
> Sent: Thursday, July 04, 2013 5:09 PM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still
> Failing
>
>
> On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
>
> >> we could solve that with an ivy configuration for 'tests' instead
>
> Or perhaps solved by that? I don't really know what you are suggesting
> though - ivy is half as mysterious as maven to me.
>
> - Mark
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
> commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Mark Miller <ma...@gmail.com>.
On Jul 4, 2013, at 11:12 AM, Robert Muir <rc...@gmail.com> wrote:
>
>
> On Thu, Jul 4, 2013 at 11:09 AM, Mark Miller <ma...@gmail.com> wrote:
>
> On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
>
> >> we could solve that with an ivy configuration for 'tests' instead
>
> Or perhaps solved by that? I don't really know what you are suggesting though - ivy is half as mysterious as maven to me.
>
>
> Basically you have the ability to say that src/java depends on libfoo.jar and libbar.jar, but that src/test also needs libbaz.jar (only for running those tests).
>
> It might add some complexity, but then the dependencies would be "more correct" I think, because test-framework doesnt really have any classes that need these dependencies (from what I see).
Yeah, it seems like that should be doable then. The tests that use those dependencies are all in solr/core - like I said, the reason they went into test-framework was to avoid having them go out as part of Solr - not because classes there use them.
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
On Thu, Jul 4, 2013 at 11:09 AM, Mark Miller <ma...@gmail.com> wrote:
>
> On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
>
> >> we could solve that with an ivy configuration for 'tests' instead
>
> Or perhaps solved by that? I don't really know what you are suggesting
> though - ivy is half as mysterious as maven to me.
>
>
Basically you have the ability to say that src/java depends on libfoo.jar
and libbar.jar, but that src/test also needs libbaz.jar (only for running
those tests).
It might add some complexity, but then the dependencies would be "more
correct" I think, because test-framework doesnt really have any classes
that need these dependencies (from what I see).
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Mark Miller <ma...@gmail.com>.
On Jul 4, 2013, at 11:06 AM, Mark Miller <ma...@gmail.com> wrote:
>> we could solve that with an ivy configuration for 'tests' instead
Or perhaps solved by that? I don't really know what you are suggesting though - ivy is half as mysterious as maven to me.
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Mark Miller <ma...@gmail.com>.
On Jul 4, 2013, at 11:01 AM, Robert Muir <rc...@gmail.com> wrote:
> I'm confused why test-framework depends upon the jersey-core, hadoop-tests, and jetty 6. Is there really anything in test-framework that depends on these (I looked, I see nothing).
>
> The reason I ask is because if test-framework doesnt need this (only *concrete* tests), we could solve that with an ivy configuration for 'tests' instead. In my opinion this would be better: we wouldn't need to ship it in our distribution at all (e.g. tests dont work from the binary distribution anyway).
The main reason they are in test-framework is because we don't want to ship any of it. I don't know the build well enough to say anything for sure, but it seems it could be part of another module that is not shipped.
- Mark
>
> On Thu, Jul 4, 2013 at 10:55 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Caused by Slowdoop commit of Mark Miller! This classes are used by Java Enterprise Edition, should never be used on a Client VM (my opinion). If somebody wants to run Slowdoop, use an Enterprise JDK.
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> From: Robert Muir [mailto:rcmuir@gmail.com]
> Sent: Thursday, July 04, 2013 4:51 PM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
>
>
>
> When was this dependency introduced? Is it really needed?
>
> The smoketesting has been failing for days because of this.
>
> On Thu, Jul 4, 2013 at 1:28 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
>
> [exec] raise RuntimeError('%s contains sheisty class "%s"' % (desc, name2))
> [exec] RuntimeError: JAR file "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar" contains sheisty class "javax/ws/rs/ApplicationPath.class"
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
I'm confused why test-framework depends upon the jersey-core, hadoop-tests,
and jetty 6. Is there really anything in test-framework that depends on
these (I looked, I see nothing).
The reason I ask is because if test-framework doesnt need this (only
*concrete* tests), we could solve that with an ivy configuration for
'tests' instead. In my opinion this would be better: we wouldn't need to
ship it in our distribution at all (e.g. tests dont work from the binary
distribution anyway).
On Thu, Jul 4, 2013 at 10:55 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Caused by Slowdoop commit of Mark Miller! This classes are used by Java
> Enterprise Edition, should never be used on a Client VM (my opinion). If
> somebody wants to run Slowdoop, use an Enterprise JDK.****
>
> ** **
>
> -----****
>
> Uwe Schindler****
>
> H.-H.-Meier-Allee 63, D-28213 Bremen****
>
> http://www.thetaphi.de****
>
> eMail: uwe@thetaphi.de****
>
> ** **
>
> *From:* Robert Muir [mailto:rcmuir@gmail.com]
> *Sent:* Thursday, July 04, 2013 4:51 PM
> *To:* dev@lucene.apache.org
> *Subject:* Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 -
> Still Failing****
>
> ** **
>
> When was this dependency introduced? Is it really needed?
>
> The smoketesting has been failing for days because of this.****
>
> On Thu, Jul 4, 2013 at 1:28 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:****
>
> [exec] raise RuntimeError('%s contains sheisty class "%s"' %
> (desc, name2))
> [exec] RuntimeError: JAR file
> "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar"
> contains sheisty class "javax/ws/rs/ApplicationPath.class"****
>
RE: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Uwe Schindler <uw...@thetaphi.de>.
Caused by Slowdoop commit of Mark Miller! This classes are used by Java Enterprise Edition, should never be used on a Client VM (my opinion). If somebody wants to run Slowdoop, use an Enterprise JDK.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: uwe@thetaphi.de
From: Robert Muir [mailto:rcmuir@gmail.com]
Sent: Thursday, July 04, 2013 4:51 PM
To: dev@lucene.apache.org
Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
When was this dependency introduced? Is it really needed?
The smoketesting has been failing for days because of this.
On Thu, Jul 4, 2013 at 1:28 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
[exec] raise RuntimeError('%s contains sheisty class "%s"' % (desc, name2))
[exec] RuntimeError: JAR file "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar" contains sheisty class "javax/ws/rs/ApplicationPath.class"
Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - Still Failing
Posted by Robert Muir <rc...@gmail.com>.
When was this dependency introduced? Is it really needed?
The smoketesting has been failing for days because of this.
On Thu, Jul 4, 2013 at 1:28 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> [exec] raise RuntimeError('%s contains sheisty class "%s"' %
> (desc, name2))
> [exec] RuntimeError: JAR file
> "/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/fakeReleaseTmp/unpack/solr-5.0.0/dist/test-framework/lib/jersey-core-1.16.jar"
> contains sheisty class "javax/ws/rs/ApplicationPath.class"
>