[
http://jira.codehaus.org/browse/MNG-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268140#action_268140
]
amaresh mourya commented on MNG-5094:
-------------------------------------
Any update on this?
Thanks,
Amaresh
> If POM's parent is not availabe in local repository then
> DefaultProjectBuilder is unable to resolve this parent while POM build
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5094
> URL: http://jira.codehaus.org/browse/MNG-5094
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.3
> Environment: Linux, Using maven 3.0.3 apis to build a MavenProject
> from a POM file via DefaultProjectBuilder.
> Reporter: amaresh mourya
>
> I created a maven project via "mvn archetype:generate" with selection item
> no as 3. Project I created was abc:xyz:1.0:jar.
> I am using build( File pomFile, ProjectBuildingRequest request ) method of
> DefaultProjectBuilder which returns ProjectBuildingResult containing
> MavenProject of POM file.
> Here is parent section of POM
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <parent>
> <groupId>com.cedarsoft</groupId>
> <artifactId>open</artifactId>
> <version>4.0.2</version>
> </parent>
> <groupId>abc</groupId>
> <artifactId>xyz</artifactId>
> <version>1.0</version>
> ---
> </project>
> Problem: My local repository doesn't contain com.cedarsoft:open:4.0.2. So
> while building with this build method I was expecting it to download parent
> (com.cedarsoft:open:4.0.2) and move ahead with the building work, but it
> didn't happen. This used to happen with maven 2.2.1 apis using
> DefaultMavenProjectBuilder.
> I debugged and found that while resolving parent (com.cedarsoft:open:4.0.2)
> repositories list is empty whereas it should provide Central repository from
> Super POM to resolve this parent artifact. This used to happen with maven
> 2.2.1 apis
> What I did to avoid this : Either I add central repository in my POM or add
> Central repository in ProjectBuildingRequest.
> So I think this is a bug of maven 3.0.3 where its unable to pass central
> repository while resolving artifacts.
--
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
