You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Harold Shinsato (JIRA)" <ji...@codehaus.org> on 2007/02/15 02:18:21 UTC
[jira] Created: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Subprojects using m2 dependency plugin causes release:prepare to fail
---------------------------------------------------------------------
Key: MDEP-64
URL: http://jira.codehaus.org/browse/MDEP-64
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Environment: winxp
Reporter: Harold Shinsato
Assigned To: Brian Fox
We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
superproject/
A/ -> no dependencies
B/ -> dependency:copy A
//superproject/pom.xml (abbrieviated)
<project>
<artifactId>superproject</artifactId>
<packaging>pom</packaging>
<version>1.0.0.1-SNAPSHOT</version>
<modules>
<module>A</module>
<module>B</module>
</modules>
</project>
// superproject/A/pom.xml (abbrievated)
<project>
<parent>
<artifactId>superproject</artifactId>
<version>1.0.0.1-SNAPSHOT</version>
</parent>
<artifactId>A</artifactId>
<version>1.0.0.1-SNAPSHOT</version>
</project>
// superproject/B/pom.xml (abbreviated)
<project>
<parent>
<artifactId>superproject</artifactId>
<version>1.0.0.1-SNAPSHOT</version>
</parent>
<artifactId>B</artifactId>
<packaging>war</packaging>
<version>1.0.0.1-SNAPSHOT</version>
<build>
<finalName>FooWar</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy</id>
<goals>
<goal>copy</goal>
</goals>
<phase>package</phase>
<configuration>
<artifactItems>
<artifactItem>
<artifactId>A</artifactId>
<version>${pom.version}</version>
<type>jar</type>
</artifactItem>
</artifactItems>
<outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<artifactId>A</artifactId>
<version>${pom.version}</version>
</dependency>
</dependencies>
</project>
The error message during mvn release:prepare is basically:
[INFO] Building B
[INFO] task-segment: [clean, integration-test]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean] <skip deleting directories>
[INFO] [dependency:copy {execution: copy}]
[INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
[WARNING] Unable to get resource from repository sizzle (<our repository details>)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: <groupId>
ArtifactId: A
Version: 1.0.0.1
Reason: Unable to download the artifact from any repository
--
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
[jira] Updated: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Harold Shinsato (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harold Shinsato updated MDEP-64:
--------------------------------
Attachment: summary.txt
The summary seems to avoid the removal of the indenting that happened in the description field.
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assigned To: Brian Fox
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Commented: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Juraj Lonc (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245778#action_245778 ]
Juraj Lonc commented on MDEP-64:
--------------------------------
I don't this is fixed. Current version is 2.2.1 and I am able to produce this bug.
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assignee: Brian Fox
> Fix For: 2.0-alpha-3
>
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Closed: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MDEP-64.
-------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0-alpha-4)
2.0-alpha-3
This will be fixed automatically once maven 2.0.6 is released.
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-3
>
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Updated: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MDEP-64:
--------------------------
Fix Version/s: 2.0-alpha-3
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-3
>
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Updated: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MDEP-64:
--------------------------
Fix Version/s: (was: 2.0-alpha-3)
2.0-alpha-4
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-4
>
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Issue Comment Edited: (MDEP-64) Subprojects using m2
dependency plugin causes release:prepare to fail
Posted by "Juraj Lonc (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245778#action_245778 ]
Juraj Lonc edited comment on MDEP-64 at 11/30/10 3:44 AM:
----------------------------------------------------------
I don't think this is fixed. Current version is 2.2.1 and I am able to produce this bug.
was (Author: chupacabras):
I don't this is fixed. Current version is 2.2.1 and I am able to produce this bug.
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assignee: Brian Fox
> Fix For: 2.0-alpha-3
>
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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
[jira] Commented: (MDEP-64) Subprojects using m2 dependency plugin
causes release:prepare to fail
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87631 ]
Brian Fox commented on MDEP-64:
-------------------------------
Have you tried the patch attached to MDEP-44 to see if it works?
> Subprojects using m2 dependency plugin causes release:prepare to fail
> ---------------------------------------------------------------------
>
> Key: MDEP-64
> URL: http://jira.codehaus.org/browse/MDEP-64
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Environment: winxp
> Reporter: Harold Shinsato
> Assigned To: Brian Fox
> Attachments: summary.txt
>
>
> We have a project with a few sub-projects. Only one of those subprojects uses the maven-dependency-plugin, copying the jar file artifact from one of the sibling sub-projects. The dependency plugin has worked fine in another multi-project m2 buld and release when the dependency copy was only referencing projects outside the multi-project's project tree.
> But in the present multi-project release, copying that sibling jar file with the dependency plugin causes the mvn release:prepare step to fail, because it can't find the released version in the release repository. It doesn't care about referencing sibling project dependencies from the regular pom dependencies, it only chokes for the dependency:copy.
> Here's a diagram for the issue with three pseudo-poms. I omitted groupId's, scm, distributionManagement, and other content from the poms that were not necessary to communicate the basic issue. I've worked around this by using the antrun plugin, which is unpleasant and untidy. This seems like it might be related to MDEP-44.
> superproject/
> A/ -> no dependencies
> B/ -> dependency:copy A
> //superproject/pom.xml (abbrieviated)
> <project>
> <artifactId>superproject</artifactId>
> <packaging>pom</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <modules>
> <module>A</module>
> <module>B</module>
> </modules>
> </project>
> // superproject/A/pom.xml (abbrievated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>A</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </project>
> // superproject/B/pom.xml (abbreviated)
> <project>
> <parent>
> <artifactId>superproject</artifactId>
> <version>1.0.0.1-SNAPSHOT</version>
> </parent>
> <artifactId>B</artifactId>
> <packaging>war</packaging>
> <version>1.0.0.1-SNAPSHOT</version>
> <build>
> <finalName>FooWar</finalName>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <executions>
> <execution>
> <id>copy</id>
> <goals>
> <goal>copy</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <artifactItems>
> <artifactItem>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> <type>jar</type>
> </artifactItem>
> </artifactItems>
> <outputDirectory>${project.build.directory}/${pom.build.finalName}/jars</outputDirectory>
> </configuration>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <dependencies>
> <dependency>
> <artifactId>A</artifactId>
> <version>${pom.version}</version>
> </dependency>
> </dependencies>
> </project>
> The error message during mvn release:prepare is basically:
> [INFO] Building B
> [INFO] task-segment: [clean, integration-test]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean] <skip deleting directories>
> [INFO] [dependency:copy {execution: copy}]
> [INFO] Configured Artifact: <groupId>:A:null:1.0.0.1:jar
> Downloading: <details>/1.0.0.1/A-1.0.0.1.jar
> [WARNING] Unable to get resource from repository sizzle (<our repository details>)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: <groupId>
> ArtifactId: A
> Version: 1.0.0.1
> Reason: Unable to download the artifact from any repository
--
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