You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by shinsato <ha...@shinsato.com> on 2007/02/12 19:12:04 UTC

Subproject dependency copy trips up release plugin?

We have a project with a few sub-projects.  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.

Is this a bug or a usage issue?

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.  Any ideas or workaround would be
appreciated.

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>
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <source>1.5</source>
          <target>1.5</target>
        </configuration>
      </plugin>
</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</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <executions>
          <execution>
            <id>copy</id>
            <goals>
              <goal>copy</goal>
            </goals>
            <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

-- 
View this message in context: http://www.nabble.com/Subproject-dependency-copy-trips-up-release-plugin--tf3215460s177.html#a8929542
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org