leverage dependencyManagement from jbossas

Hi Paul,

in order to leverage the AS50 dependencyManagement, I define
this parent

    	   <parent>
  	    <groupId>org.jboss.jbossas</groupId>
  	   
<artifactId>jboss-as-component-matrix</artifactId&g
t;
  	    <version>5.0.0-SNAPSHOT</version>
  	  </parent>

http://fisheye
.jboss.com/browse/JBossWS/container/jboss50/branches/jbossws
-jboss501/pom.xml?r=6679

However, I would like to use the jbossws parent instead. Is
there 
another way to pull in the dependency management?

cheers
-thomas

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Thomas Diesler wrote:
> Hi Paul,
>
> in order to leverage the AS50 dependencyManagement, I
define this parent
>
>           <parent>
>         
<groupId>org.jboss.jbossas</groupId>
>         
<artifactId>jboss-as-component-matrix</artifactId&g
t;
>          <version>5.0.0-SNAPSHOT</version>
>        </parent>
>
> http://fisheye
.jboss.com/browse/JBossWS/container/jboss50/branches/jbossws
-jboss501/pom.xml?r=6679 
>
>
> However, I would like to use the jbossws parent
instead. Is there 
> another way to pull in the dependency management?
>
> cheers
> -thomas
>
Yes, but only if you use Maven 2.0.9.

"The 'import' scope is only used on a dependency of
type pom in the 
<dependencyManagement> section. It indicates that the
specified POM 
should be replaced with the dependencies in that POM's 
<dependencyManagement> section. Since they are
replaced, dependencies 
with a scope of import do not actually participate in
limiting the 
transitivity of a dependency. Please note that the use of
this scope 
will break backwards compatibility with older Maven
versions. If you use 
this, you should use the maven-enforcer-plugin to require a
minimum 
maven version of 2.0.9."

(for more details, see 
http
://maven.apache.org/guides/introduction/introduction-to-depe
ndency-mechanism.html#Importing_Dependencies)

_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment

Thomas Diesler wrote:
> Hi Paul,
> 
> in order to leverage the AS50 dependencyManagement, I
define this parent
> 
>           <parent>
>         
<groupId>org.jboss.jbossas</groupId>
>         
<artifactId>jboss-as-component-matrix</artifactId&g
t;
>          <version>5.0.0-SNAPSHOT</version>
>        </parent>
> 
> http://fisheye
.jboss.com/browse/JBossWS/container/jboss50/branches/jbossws
-jboss501/pom.xml?r=6679 
> 
> 
> However, I would like to use the jbossws parent
instead. Is there 
> another way to pull in the dependency management?
> 
> cheers
> -thomas
> 

You can't depend on jboss-as-component-matrix, nor import
it, because 
that would create a cyclic dependency.

Very simply put: jboss-as-component-matrix goes GA the
moment jboss-as 
goes GA, but before that WS has to deliver a GA.

If we want a common component matrix, then it must live
outside of AS trunk.

Carlo
_______________________________________________
jboss-development mailing list
jboss-developmentlists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-develop
ment