You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steven Rowe (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/26 20:40:49 UTC
[jira] [Resolved] (LUCENE-2268) Add test to check maven artifacts
and their poms
[ https://issues.apache.org/jira/browse/LUCENE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe resolved LUCENE-2268.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.0
3.6
Assignee: Steven Rowe
Nightly Maven Jenkins builds test the Maven build and artifacts via Jenkins's local repository.
LUCENE-3655 added thorough checks of Maven release artifacts to {{dev-tools/scripts/smokeTestRelease.py}}.
> 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: general/build
> Affects Versions: 2.9.2, 3.0.1
> Reporter: Uwe Schindler
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org