I have run into this as well. It'd be great to allow arbitary strings for versioning of custom releases.
This is the culprit: https://github.com/apache/lucene-solr/blob/branch_4x/lucene/tools/src/java/org/apache/lucene/dependencies/GetMavenDependenciesTask.java#L627 On Tue, Jan 28, 2014 at 4:10 AM, Ryan McKinley <ryan...@gmail.com> wrote: > 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 > > >
