[
http://jira.codehaus.org/browse/MRELEASE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108515
]
vincent dupain commented on MRELEASE-161:
-----------------------------------------
There a workflow to this bug: generate one jar that merge main jar and test jar:
<build>
<resources>
<resource>
<directory>src/main/java</directory>
<targetPath>../../src/merge/java</targetPath>
</resource>
<resource>
<directory>src/test/java</directory>
<targetPath>../../src/merge/java</targetPath>
</resource>
</resources>
<sourceDirectory>src/merge/java</sourceDirectory>
<plugins>
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<configuration>
<filesets>
<fileset>
<directory>src/merge/java</directory>
</fileset>
</filesets>
</configuration>
</plugin>
...
<build>
and in the pom that depends on the 2 jars, you only have to depend on the main
jar
<dependencies>
<!-- Kamayo Dependencies -->
<!--
<dependency>
<groupId>com.kamayo</groupId>
<artifactId>core</artifactId>
<version>${version}</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
-->
<dependency>
<groupId>com.kamayo</groupId>
<artifactId>core</artifactId>
<version>${version}</version>
<type>jar</type>
</dependency>
...
</dependencies>
> If there is more than one artifact with the same artifactId in
> dependencyManagement only the first one is updated
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-161
> URL: http://jira.codehaus.org/browse/MRELEASE-161
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven 2.0.4 under windows
> Reporter: Sébastien Cesbron
> Attachments: multipleArtifacts.patch, release-test.zip
>
>
> I have a multi module project. When I do release:prepare, the release plugin
> update the version tag of all my submodules in the dependencyManagement
> section.
> For the same module I have declared two artifacts like this :
> <dependency>
> <groupId>com.bla</groupId>
> <artifactId>blabla</artifactId>
> <version>1.0-SNAPSHOT</version>
> <type>test-jar</type>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>com.bla</groupId>
> <artifactId>blabla</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> In this case, the release plugin only update the first dependency.
> This is due to element search in the "updateDomVersion" method of the
> AbstractRewritePomsPhase class. I've attached a patch to solve the problem. I
> don't know if this is the right way to do. I change all the artifacts in the
> same pass. I don't take car of different type/classifier
--
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
