lucene-dev mailing list archives

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


Chris Male commented on LUCENE-2268:

Hi Robert,

Have you mentioned somewhere recently what you'd like tested in regards to the artifacts and
poms? Is the test that Uwe suggests here sufficient or is there more you'd like tested?

So far I can think of the following things that might need to be checked:

- Poms are valid XML/maven poms
- Poms include all dependencies with correct versions for their modules
- Poms have correct groupId and artifactId
- Artifacts for all modules are created
- Artifacts match those created through the official ant build

Too far or have I missed some?

> Add test to check maven artifacts and their poms
> ------------------------------------------------
>                 Key: LUCENE-2268
>                 URL:
>             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:
For additional commands, e-mail:

View raw message