[
https://issues.apache.org/jira/browse/LUCENE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913581#action_12913581
]
Chris Male commented on LUCENE-2268:
------------------------------------
Hi,
So far I've just gathered some anecdotal information from people of which none
is about what we've discussed here :D
Issues so far seem to be around the releasing of the maven artifacts rather
than the artifacts themselves. Problems include signing issues, syncing
permissions and most importantly very bad documentation. These will be tackled
in some other JIRA issues that'll spring up shortly, but I'll tackle this as
well.
> Add test to check maven artifacts and their poms
> ------------------------------------------------
>
> Key: LUCENE-2268
> URL: https://issues.apache.org/jira/browse/LUCENE-2268
> Project: Lucene - Java
> Issue Type: Test
> Components: Build
> Affects Versions: 2.9.2, 3.0.1
> Reporter: Uwe Schindler
>
> As release manager it is hard to find out if the maven artifacts work
> correct. It would be good to have an ant task that executes maven with a .pom
> file that requires all contrib/core artifacts (or one for each contrib) that
> "downloads" the artifacts from the local dist/maven folder and builds that
> test project. This would require maven to execute the build script. Also it
> should pass the ${version} ANT property to this pom.xml
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
