maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trenton (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-295) Internal dependencies left at old snapshot
Date Tue, 09 Sep 2008 21:56:48 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147489#action_147489
] 

Trenton commented on MRELEASE-295:
----------------------------------

I am having the same issue.  It happens on a dependency of a profile within the pom.

For example, after a dryRun, I have the following...
web/pom.xml.tag
    <profile>
      <!-- use full rmi when doing development, even if inproc server -->
      <id>inproc</id>
      <properties>
        <inProcServer>true</inProcServer>
      </properties>
      <build>
        <resources>
          <!-- Copy configurations over to webapp folder -->
          <resource>
            <filtering>true</filtering>
            <directory>${basedir}/src/main/resources</directory>
          </resource>
        </resources>
      </build>
      <dependencies>
        <dependency>
          <groupId>ca.athabascau.banner.oros</groupId>
          <artifactId>rmi</artifactId>
          <version>1.2.0-SNAPSHOT</version>
          <scope>compile</scope>
        </dependency>
      </dependencies>
    </profile>


> Internal dependencies left at old snapshot
> ------------------------------------------
>
>                 Key: MRELEASE-295
>                 URL: http://jira.codehaus.org/browse/MRELEASE-295
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-6
>            Reporter: Chris Searle
>         Attachments: release_test.zip
>
>
> I'm having a problem with version numbering when releasing a given reactor with modules
within the reactor that have dependencies inside the reactor.
> I have narrowed this to the following structure
> A parent test/pom.xml (basically a pom packging grouping pom - but here is where the
scm and repos are also defined) with
>   <groupId>test</groupId>
>   <artifactId>test</artifactId>
>   <packaging>pom</packaging>
>   <version>1.0-SNAPSHOT</version>
> and
>   <modules>
>     <module>test-1</module>
>     <module>test-2</module>
>   </modules>
> Then - the two modules:
> test/test-1/pom.xml with
>   <parent>
>     <groupId>test</groupId>
>     <artifactId>test</artifactId>
>     <version>1.0-SNAPSHOT</version>
>   </parent>
>   <groupId>test</groupId>
>   <artifactId>test-1</artifactId>
>   <version>1.0-SNAPSHOT</version>
> test/test-2/pom.xml with
>   <parent>
>     <groupId>test</groupId>
>     <artifactId>test</artifactId>
>     <version>1.0-SNAPSHOT</version>
>   </parent>
>   <groupId>test</groupId>
>   <artifactId>test-2</artifactId>
>   <version>1.0-SNAPSHOT</version>
>   <dependencies>
>     <dependency>
>       <groupId>test</groupId>
>       <artifactId>test-1</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>   </dependencies>
> Then run mvn -DdryRun=true release:prepare
> test/pom.xml.tag version=1.0 - good
> test/pom.xml.next version=1.1-SNAPSHOT - good
> test-1/pom.xml.tag version=1.0, parent version=1.0 good
> test-1/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> test-2/pom.xml.tag version=1.0, parent version=1.0, dependency to test-1 version=1.0
good
> test-2/pom.xml.next version=1.1-SNAPSHOT, parent version=1.1-SNAPSHOT - good
> BUT
> test-2/pom.xml.next dependency to test-1 version=1.0-SNAPSHOT
> This seems wrong to me - I would expect it to also get 1.1-SNAPSHOT for the dependency
on test-1 since it has the same parent and is being run in the same reactor.

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

        

Mime
View raw message