[
http://jira.codehaus.org/browse/MNG-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4963:
-----------------------------------
Summary: [regression] Parent POM not downloaded when settings define global
mirror and one snapshot repo but no other release repository (was: Parent
Artifact ist not downloaded from repository with certain settings)
> [regression] Parent POM not downloaded when settings define global mirror and
> one snapshot repo but no other release repository
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4963
> URL: http://jira.codehaus.org/browse/MNG-4963
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, POM
> Affects Versions: 3.0, 3.0.1
> Reporter: Stephan Pauxberger
> Attachments: parent-projects.zip
>
>
> Given the following two projects:
> {{parent}}, released as organization POM
> {{child}}, uses parent as its parent
> parent pom is *NOT* in the local repository (i.e. new developer machine or
> build node of the CI)
> settings.xml defines:
> a) a global mirror for all repositories
> (http://local-nexus.srv/content/groups/public)
> {code:xml}
> <mirrors>
> <mirror>
> <id>Nexus</id>
> <name>Coporate Nexus</name>
> <url>http://local-nexus.srv/content/groups/public</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
> </mirrors>
> {code}
> b) a profile "repos" including a snapshot repository and an active-profiles
> entry activating this profile
> {code:xml}
> <profiles>
> <profile>
> <id>repos</id>
> <repositories>
> <repository>
> <id>nexus-snapshots</id>
> <name>Projektserver Snapshots</name>
> <url>http://local-nexus.srv/content/repositories/snapshots</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <checksumPolicy>fail</checksumPolicy>
> <updatePolicy>always</updatePolicy>
> </snapshots>
> </repository>
> </repositories>
> </profile>
> </profiles>
> <activeProfiles>
> <activeProfile>repos</activeProfile>
> </activeProfiles>
> {code}
> This is a fairly standard setup for copporate development.
> now, when trying to compile the project, the following error is thrown:
> {noformat}
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project de.eucodos.bugs.maven:child:0.1-SNAPSHOT
> (X:\ACM\test\child\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> de.eucodos.bugs.maven:parent:pom:0.1 and 'parent.relative
> Path' points at wrong local POM @ line 3, column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {noformat}
> Without maven trying to download the parent from the corp-repo.
> Sidenote: with Maven 2.x, this works without problems.
> If an additional *release*-repository is included in profile "repos",
> everything works as expected:
> {code:xml}
> <profiles>
> <profile>
> <id>repos</id>
> <repositories>
> <repository>
> <id>nexus</id>
> <name>Projektserver</name>
> <url>http://msgs722i.msg.de:8080/nexus/content/groups/public</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> </repository>
> <repository>
> <id>nexus-snapshots</id>
> ...
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
