maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] (MNGSITE-161) core-its references non-existant snapshot of maven-parent
Date Mon, 03 Sep 2012 19:39:21 GMT


Olivier Lamy moved MNG-5340 to MNGSITE-161:

     Complexity:   (was: Intermediate)
    Component/s:     (was: Integration Tests)
            Key: MNGSITE-161  (was: MNG-5340)
        Project: Maven Project Web Site  (was: Maven 2 & 3)
> core-its references non-existant snapshot of maven-parent
> ---------------------------------------------------------
>                 Key: MNGSITE-161
>                 URL:
>             Project: Maven Project Web Site
>          Issue Type: Bug
>            Reporter: Søren Boisen
> Couldn't find a project for the Maven IT stuff, so filing against core:
> Tried following the instructions in:
> After figuring out the first failure due to the archetype catalog specifying the wrong
repository (maven IT stuff have been moved to the
repo), I hit a dead end trying to build the sample IT project:
> [INFO] Unable to find resource 'org.apache.maven:maven-parent:pom:21-SNAPSHOT' in repository
apache.snapshots (
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.maven.its:core-its:pom:2.1-SNAPSHOT
> Reason: Cannot find parent: org.apache.maven:maven-parent for project: org.apache.maven.its:core-its:pom:2.1-SNAPSHOT
for project org.apache.maven.its:core-its:pom:2.1-SNAPSHOT
> The problem is that the newest snapshot of core-its declares maven-parent 21-SNAPSHOT
as its parent, but 21-SNAPSHOT was never properly pushed to the repository.
> Please update core-its parent reference to either an existing snapshot version or a released
version of maven-parent.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message