[jboss-dev-forums] [Design of JBoss Build System] - Re: Maven Version ranges - generateReleasePoms

[adrian@jboss.org]

The other thing I don't understand is why it is resolving the versions to
a suggestion rather than a hard constraint.

e.g. My constraint

  |     <dependency>
  |       <groupId>test</groupId>
  |       <artifactId>project1</artifactId>
  |       <version>1.0.0-Beta-1</version>
  |       <scope>compile</scope>
  |     </dependency>
  | 

becomes in the release-pom.xml


  |     <dependency>
  |       <groupId>test</groupId>
  |       <artifactId>project1</artifactId>
  |       <version>1.0.0-Beta-1</version>
  |       <scope>compile</scope>
  |     </dependency>
  | 

why isn't this?


  |     <dependency>
  |       <groupId>test</groupId>
  |       <artifactId>project1</artifactId>
  |       <version>[1.0.0-Beta-1]</version>
  |       <scope>compile</scope>
  |     </dependency>
  | 

which is what would be required to properly reproduce the build.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139827#4139827

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139827