[
https://issues.apache.org/jira/browse/LUCENE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913519#action_12913519
]
Robert Muir commented on LUCENE-2268:
-------------------------------------
Chris, these sound like great checks...
I'm not really sure what is involved to know that poms/artifacts are correct,
but at the moment since we have no checks, even adding one of these checks is
an improvement (for example: is the pom even valid xml at all)...
I figure its like any other feature, we won't immediately have perfect tests
but we can improve them iteratively.
> 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
