The real version number i was trying was:
-Dversion=4.7.r1562172M

essentially a standard lucene build with a few chances.  Having the
non-numbers in the version make it fail

This used to work -- and now seems to fail only for
lucene-analyzers-phonetic

but i don't have any idea where to start!

ryan


On Tue, Jan 28, 2014 at 9:30 AM, Uwe Schindler <u...@thetaphi.de> wrote:

> You should not use a version like this to build artifacts, because it
> violates the Maven specs for versioning. You can define a custom version,
> but you have to prepend it with a valid Maven-version number, like:
>
>
>
> -Dversion="4.6-my-special-version"
>
>
>
> Ideally do it like Jenkins with build number:
>
>
>
> -Ddev.version.suffix="my-special-version", which will produce the above
> version number with the 4.6 checkout.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: u...@thetaphi.de
>
>
>
> *From:* Ryan McKinley [mailto:ryan...@gmail.com]
> *Sent:* Monday, January 27, 2014 11:41 PM
> *To:* solr-...@lucene.apache.org
> *Subject:* maven build issues with non-numeric custom version
>
>
>
> From:
>
>
> http://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/dev-tools/maven/README.maven
>
>
>
> It says we can get a custom build number using:
>
> ant -Dversion=my-special-version get-maven-poms
>
>
>
> but this fails with:
>
> BUILD FAILED
>
> /Users/ryan/workspace/apache/lucene_4x/build.xml:141: The following error
> occurred while executing this line:
>
> /Users/ryan/workspace/apache/lucene_4x/lucene/common-build.xml:1578: The
> following error occurred while executing this line:
>
> /Users/ryan/workspace/apache/lucene_4x/lucene/tools/custom-tasks.xml:122:
> Malformed module dependency from
> 'lucene-analyzers-phonetic.internal.test.dependencies':
> 'lucene/build/analysis/common/lucene-analyzers-common-my-special-version.jar'
>
>
>
>
>
> Using a numeric version number things work OK.
>
>
>
> Any ideas?
>
>
>
> ryan
>
>
>

Reply via email to