Hi,
My idea with: <rsel:name name="**/lucene-*-${version}.jar" handledirsep="true"/>
Does not work for standard builds, as the ${version}=="5.0-SNAPSHOT" produces
another filename (not ending in SNAPSHOT, instead a random date-like number).
This is caused by some magic in the internet downloader:
-validate-maven-dependencies:
[licenses] MISSING sha1 checksum file for: C:\Users\Uwe
Schindler\.m2\repository\org\apache\lucene\lucene-codecs\5.0-SNAPSHOT\lucene-codecs-5.0-20130102.164639-2.jar
[licenses] MISSING sha1 checksum file for: C:\Users\Uwe
Schindler\.m2\repository\org\apache\lucene\lucene-core\5.0-SNAPSHOT\lucene-core-5.0-20130102.164408-2.jar
[licenses] Scanned 4 JAR file(s) for licenses (in 0.02s.), 2 error(s).
That is the problem I have here. So maybe we need a regex as Robert suggests.
One for snapshot releases and one for builds with real version numbers where
the filenames can be guessed easily.
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]
> -----Original Message-----
> From: Robert Muir [mailto:[email protected]]
> Sent: Wednesday, January 02, 2013 5:08 PM
> To: [email protected]
> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #198: POMs out of
> sync
>
> On Wed, Jan 2, 2013 at 11:05 AM, Robert Muir <[email protected]> wrote:
> > On Wed, 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:
> > ...
> >> <excludes>
> >> <rsel:name name="**/lucene-*.jar" handledirsep="true"/>
> >> </excludes>
> > ...
> >>
> >> We should fix this pattern in rsel:name to add the lucene version.
>
> In case it helps: we dont have to use the ant-style patterns.
> rsel:name can take a regexp instead
>
> http://ant.apache.org/manual/Types/resources.html#rsel.name
>
> ---------------------------------------------------------------------
> 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]
