JBoss development,
A new message was posted in the thread "EJBTHREE-2007: VFS Abstraction":
http://community.jboss.org/message/524557#524557
Author : jaikiran pai
Profile :
http://community.jboss.org/people/jaikiran
Message:
--------------------------------------------------------------
jaikiran wrote:
I don't mind having this new enforcer rule, but eventually i suspect that we are
going to end up with a lengthy (trial and error, ever changing) excludes list
A bit
OT - If Maven allowed a way to exclude an artifact irrespective of from which artifact it
get's pulled in transitively from, then instead of something like this:
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-annotations</artifactId>
<version>${version.org.hibernate}</version>
<!-- Exclude org.hibernate:hibernate which is banned in
favour of org.hibernate:hibernate-core -->
<exclusions>
<exclusion>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>${version.org.hibernate.hibernate-entitymanager}</version>
<!-- Exclude org.hibernate:hibernate which is banned in
favour of org.hibernate:hibernate-core -->
<exclusions>
<exclusion>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
</exclusion>
</exclusions>
</dependency>
we could just have had:
<exclusions>
<exclusion>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<!-- Instruct Maven to exclude this artifact from any dependency
of this project which pulls this in -->
<include-transitive/>
</exclusion>
</exclusions>
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/524557#524557