lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2268) Add test to check maven artifacts and their poms
Date Wed, 22 Sep 2010 13:12:34 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913534#action_12913534
] 

Robert Muir commented on LUCENE-2268:
-------------------------------------

Chris: to get better bang for our buck, one way would be to look at the maven bugs with previous
releases.

Can we create checks that would have detected any of the issues that went wrong? 

Later, we could add some of the more thorough checks you have suggested here.


> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message