[ 
http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann updated MNG-4834:
-----------------------------------

    Summary: [regression] MavenProject.getParent() ignores configured 
repositories  (was: Site descriptor of parent is no longer found in local 
repository)

> [regression] MavenProject.getParent() ignores configured repositories
> ---------------------------------------------------------------------
>
>                 Key: MNG-4834
>                 URL: http://jira.codehaus.org/browse/MNG-4834
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0-beta-3
>         Environment: $ mvn -v
> Apache Maven 3.0-RC2 (r1000119; 2010-09-22 20:23:26+0200)
> Java version: 1.6.0_21
> Java home: /opt/sun-jdk-1.6.0.21/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.34-gentoo-r6" arch: "i386" Family: "unix"
>            Reporter: Joerg Schaible
>            Assignee: Benjamin Bentmann
>            Priority: Minor
>         Attachments: MNG-4834-remote-repo.tgz, MNG-4834.tgz, MNG-settings.xml
>
>
> The site descriptor from the parent project is no longer found in the local 
> repository. The site plugin tries always to resolve the artifact from the 
> remote repository using the attach-descriptor goal. This is nasty if that 
> repo is not reachable and Maven will wait always until the connection times 
> out before continuing. With M2 this descriptor is found in the local repo: 
> "Parent project loaded from repository.". In both cases version 2.1.1 of the 
> site plugin is used. There's no change in behavior for M3 if the site plugin 
> is upgraded to 3.x.

-- 
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

        

Reply via email to