Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <25167057.1211827521874.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Mon, 26 May 2008 13:45:21 -0500 (CDT)
From: "Herve Boutemy (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Reopened: (MANTTASKS-87) Using a pom.xml for dependencies,
 in which the pom.xml has a parent pom.xml will cause a "Error downloading
 parent pom" error
In-Reply-To: 
 <14582472.1188517511438.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Herve Boutemy reopened MANTTASKS-87:
------------------------------------


I reopen the issue since the "checkParentPom()" workaround doesn't work in the case reported now.
I don't understand why Maven manages the case and not Maven Ant Task: AFAIK, it's same code.
Need to investigate deeper...

> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MANTTASKS-87
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-87
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: POM Integration
>    Affects Versions: 2.0.9
>         Environment: WindowsXP
> Ant version 1.7.0
>            Reporter: Jeff Campbell
>            Assignee: Herve Boutemy
>            Priority: Blocker
>         Attachments: CASE.tar.gz
>
>
> Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error.
> This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to maven-ant-tasks-2.0.7.jar and still an issue with the latest maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)).
> Just to see if I had done something wrong with the pom.xml file I tried to run a Maven goal against the pom.xml file.  I found that if I run "mvn clean" from this same directory (where the build.xml and pom.xml file is located), using Maven-2.0.7, I get a build successfull (it was able to find the parent pom.xml file...  so this seems to be isolated to JUST the maven-ant-task not being able to find the parent pom.xml)
> **** Sample of the pom.xml file ****
> <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>
>     <groupId>intuit.sbconnect</groupId>
>     <artifactId>sbclogin</artifactId>
>     <version>1.0.3</version>
>     <name>SBCLogin</name>
>     
>     <parent>
>         <groupId>mygroup</groupId>
>         <artifactId>CommonPOM</artifactId>
>         <version>1.0.2</version>
>     </parent>
>     
>       <dependencies>
>         <dependency>
>             <groupId>myothergroup</groupId>
>             <artifactId>myartifact</artifactId>
>             <version>1.0</version>
>         </dependency> 
>    </dependencies>
> </project>
> **** Line in Ant build.xml file that causes the error: ****
> <artifact:pom id="maven.project" file="pom.xml"/>
> **** Error that occurs when this line is executed in ant: ****
> Error downloading parent pom: Missing:
> ----------
> 1) mygroup:CommonPOM:pom:1.0.2
>   Path to dependency:
>          1) unspecified:unspecified:jar:0.0
>          2) mygroup:CommonPOM:pom:1.0.2
> ----------
> 1 required artifact is missing.
> for artifact:
>   unspecified:unspecified:jar:0.0
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)

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