http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4136235#4136235
The http://maven.apache.org/release-notes.html show a number of issues related to version ranges as being fixed. The question is, what happens when you use them?

Code: 
    <dependency>
      <groupid>org.jboss.x</groupid>
      <artifactid>x-api</artifactid>
      <!-- Compatible with all 3.3.* versions -->
      <version>[3.3.0,3.4.0)</version>
    </dependency>

Heiko Braun wrote: 
I need to test the new SPI with EJB3 first,
but I think I need to release both EJB3 and Meta Data along
with the new SPI.

Or do you see a way to declare a compatible version with maven
that allows us to just touch the repository?

/Heiko

On Thu, 2008-03-13 at 02:28 -0700, Scott M Stark wrote:
  
There are no open issues, so it would appear it can be done today. Is 
there anything that needs to be done that is no in Jira Alexey?

Heiko Braun wrote:
    
We have a shared dependency between AS and EJB3 towards the meta data
project. Which in turn depends on the WS SPI.

I need to update the WS SPI and was wondering when the next release is
planned? Basically both EJB3 and AS must depend on the same version
(else EJB3 compiles against one, and AS puts another in runtime).

This relates to this thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4136182#4136182

/Heiko


_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
  
      
_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
    

_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development