On Jul 4, 2013, at 11:01 AM, Robert Muir <[email protected]> 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 <[email protected]> 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: [email protected] > > > > From: Robert Muir [mailto:[email protected]] > Sent: Thursday, July 04, 2013 4:51 PM > To: [email protected] > 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 > <[email protected]> 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: [email protected] For additional commands, e-mail: [email protected]
