[
https://issues.apache.org/jira/browse/LUCENE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885599#comment-13885599
]
ASF subversion and git services commented on LUCENE-5420:
---------------------------------------------------------
Commit 1562533 from [~steve_rowe] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1562533 ]
LUCENE-5420: 'ant get-maven-poms' should support custom version formats (merged
trunk r1562530)
> 'ant get-maven-poms' should support custom version formats
> ----------------------------------------------------------
>
> Key: LUCENE-5420
> URL: https://issues.apache.org/jira/browse/LUCENE-5420
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Reporter: Steve Rowe
> Priority: Minor
> Attachments: LUCENE-5420.patch
>
>
> LUCENE-5217 changed the way {{ant get-maven-poms}} works, so that
> dependencies are pulled from the Ant build, instead of being hard-coded in
> the POM templates. To parse the versions from internal module dependencies,
> the new internal Ant task {{GetMavenDependenciesTask}} uses a regex that
> expects a dotted/slashed/underscored numeric + optional -SNAPSHOT version
> format. As a result, non-conforming versions trigger a build failure - see
> the lucene-dev mailing list thread "maven build issues with non-numeric
> custom version":
> <http://mail-archives.apache.org/mod_mbox/lucene-dev/201401.mbox/%3cCAF=Pa5-0sXE9Su1PgF5M+F0T+g3Q=fetwgxdh5ry1ab3zrh...@mail.gmail.com%3e>
> This is a regression, since previously, custom version strings worked
> properly, e.g. {{ant -Dversion=my-custom-version get-maven-poms}}.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
