That's not the Maven build. Here's the leading context from the Jenkins build log:
----- -validate-maven-dependencies: [artifact:dependencies] Downloading: org/carrot2/carrot2-core/3.6.2/carrot2-core-3.6.2.pom from repository central at http://repo1.maven.org/maven2 [artifact:dependencies] Transferring 7K from central [artifact:dependencies] Downloading: org/carrot2/carrot2/3.6.2/carrot2-3.6.2.pom from repository central at http://repo1.maven.org/maven2 [artifact:dependencies] Transferring 7K from central [artifact:dependencies] Downloading: org/apache/lucene/lucene-memory/3.6.0/lucene-memory-3.6.0.pom from repository sonatype.releases at http://oss.sonatype.org/content/repositories/releases ----- If you look further down, you can see that only POMs are downloaded - presumably these are consulted in order to first build the full dependency graph, from which the Lucene 3.6.0 dependencies are then pruned. Steve On Jan 2, 2013, at 11:12 AM, Robert Muir <[email protected]> wrote: > It doesnt? Is it only downloading the .pom? > > [artifact:dependencies] Downloading: > org/apache/lucene/lucene-memory/3.6.0/lucene-memory-3.6.0.pom from > repository central at http://repo1.maven.org/maven2 > [artifact:dependencies] Transferring 3K from central > > On Wed, Jan 2, 2013 at 11:10 AM, Steve Rowe <[email protected]> wrote: >> >> The Maven build does not download Lucene 3.6.0. There are already >> transitive dependency exclusions for this in the clustering POM. >> >> +1 to fix the checker though. >> >> Steve >> >> On Jan 2, 2013, at 11:02 AM, "Uwe Schindler" <[email protected]> wrote: >> >>> Hi, >>> >>> It is worse: The Maven build also download Lucene 3.6.0 (because carrot >>> clustering depends on this). Our maven dependency checker does not fail on >>> this because we have an exclusion: >>> >>> <target name="-validate-maven-dependencies"> >>> <property name="top.level.dir" location="${common.dir}/.."/> >>> <pathconvert property="pom.xml"> >>> <mapper> >>> <chainedmapper> >>> <globmapper from="${top.level.dir}*" >>> to="${filtered.pom.templates.dir}*"/> >>> <globmapper from="*build.xml" to="*pom.xml"/> >>> </chainedmapper> >>> </mapper> >>> <path location="${ant.file}"/> >>> </pathconvert> >>> <m2-validate-dependencies pom.xml="${pom.xml}" >>> licenseDirectory="${license.dir}"> >>> <excludes> >>> <rsel:name name="**/lucene-*.jar" handledirsep="true"/> >>> </excludes> >>> </m2-validate-dependencies> >>> </target> >>> >>> We should fix this pattern in rsel:name to add the lucene version. >>> >>> Uwe >>> >>> ----- >>> Uwe Schindler >>> H.-H.-Meier-Allee 63, D-28213 Bremen >>> http://www.thetaphi.de >>> eMail: [email protected] >>> >>> >>>> -----Original Message----- >>>> From: Uwe Schindler [mailto:[email protected]] >>>> Sent: Wednesday, January 02, 2013 4:54 PM >>>> To: [email protected] >>>> Subject: RE: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #198: POMs out of >>>> sync >>>> >>>> Since the commit oft he carrotsearch updates, the maven build downloads >>>> additional JAR files without a license/sha1 sum. >>>> >>>> Uwe >>>> >>>> ----- >>>> Uwe Schindler >>>> H.-H.-Meier-Allee 63, D-28213 Bremen >>>> http://www.thetaphi.de >>>> eMail: [email protected] >>>> >>>> >>>>> -----Original Message----- >>>>> From: Apache Jenkins Server [mailto:[email protected]] >>>>> Sent: Wednesday, January 02, 2013 2:37 PM >>>>> To: [email protected] >>>>> Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #198: POMs out of sync >>>>> >>>>> Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/198/ >>>>> >>>>> No tests ran. >>>>> >>>>> Build Log: >>>>> [...truncated 11216 lines...] >>>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] For additional >>>> commands, e-mail: [email protected] >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
