> I think the problem with Eclipse is also that the classpath.xsl file collects > all JAR files from all lib folders into Eclipse's classpath. Our "Ant > eclipse" command does not create an IvyDE project, it just resolves all JAR > files, afterwards collecting them via the XSL above.
Yes, it's true but those two files shouldn't even be copied to lib/* because they're effectively not used by any of Lucene/Solr. Their only reason of existence in the ivy file is because we need those JARs to execute randomizedrunner's ANT tasks; otherwise we'd need to have another ivy file or a static JAR inside the repo. Dawid > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > >> -----Original Message----- >> From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf >> Of Dawid Weiss >> Sent: Friday, February 06, 2015 9:41 AM >> To: dev@lucene.apache.org >> Cc: Steve Rowe >> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1341: POMs out >> of sync >> >> Eclipse shouldn't be seeing these because ivy shouldn't be exporting them... >> I recall when I wrote the ivy.xml file I specifically included two different >> configs -- one for ANT (execution, task defs) and one for IDEs and >> compilation. This used to work but now everything is copied to lib/ >> (including >> ant and junit4-ant, which are not required at all except for ant buildfile >> taskdefs. >> >> I see Steve was playing with ivy files -- I've tried to fix it in 5 mins, >> but failed >> so far. Steve, do you know how to exclude these two deps from the default >> configuration (junit4-stdalone is still used in ivy dependency collection in >> the >> buildfile's taskdef). >> >> <!-- Only needed for ANT taskdefs. --> >> <dependency org="org.apache.ant" name="ant" ... >> <dependency org="com.carrotsearch.randomizedtesting" name="junit4- >> ant" ... >> >> Dawid >> >> On Fri, Feb 6, 2015 at 9:21 AM, Uwe Schindler <u...@thetaphi.de> wrote: >> > Moin, >> > >> >> It's a repackaged, trimmed guava dependency, but it shouldn't be >> >> visible; only the test runner should be on test classpath; the ant >> >> runner code for randomizedtesting should only be present for the ANT >> build file. >> > >> > But Eclipse sees it and sometimes makes those stupid suggestions for >> imports... >> > >> >> > I suspect the junit4 jar is not on the Maven test classpath because >> >> > the >> >> Maven build uses the surefire plugin as its test runner rather than >> >> the junit4 runner. >> >> >> >> Traitors! :) >> >> >> >> Dawid >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For >> >> additional commands, e-mail: dev-h...@lucene.apache.org >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For >> > additional commands, e-mail: dev-h...@lucene.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional >> commands, e-mail: dev-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
