[jboss-as7-dev] Transitive deps to be removed from the AS7 build

David M. Lloyd david.lloyd at redhat.com
Tue Jun 7 12:43:31 EDT 2011


On 06/07/2011 11:02 AM, Paul Gier wrote:
> On 06/07/2011 10:35 AM, Alessio Soldano wrote:
>> Hi Paul,
>> from a ws point of view the following is required of course:
>>
>> [INFO] +- org.apache.velocity:velocity:jar:1.6.2:compile
>> [INFO] |  +- commons-lang:commons-lang:jar:2.4:compile
>> ..
>> [INFO] +- org.apache.ws.security:wss4j:jar:1.6.0:compile
>> ..
>> [INFO] |  \- org.jboss:jboss-vfs:jar:3.0.0.GA:compile
>> ..
>> [INFO] |  \- org.jboss.com.sun.httpserver:httpserver:jar:1.0.0.Beta1:compile
>> ..
>> [INFO] +-
>> org.jboss.as:jboss-as-webservices-server-integration:jar:7.0.0.Beta4-SNAPSHOT:compile
>> [INFO] |  +- org.jboss.ws:jbossws-api:jar:1.0.0.Beta1:compile
>> [INFO] |  +- org.jboss.ws:jbossws-common:jar:2.0.0.Beta2:compile
>> [INFO] |  \- org.jboss.ws:jbossws-spi:jar:2.0.0.Beta2:compile
>>
>> In any case, please leave me a chance to trigger a jbossws-testsuite run
>> on our jbws hudson between your changes and the next AS release ;-)
>>
>
> Doh, I realized I didn't do very good filtering in my list.  Those deps
> are already listed in the dependencyManagement in the root pom, so I
> won't remove any of them.  I'll send a new list in a bit.

One advantage to excluding all transitive deps is that you don't need to 
do any filtering.  When I was maintaining the exclusions, being able to 
immediately see transitive deps at a glance was pretty helpful.

Things are quite a lot more complicated now, granted.

The policy I used to follow was that jboss-as submodules could have 
dependencies, and that's it.  It meant a lot of exclusions but like I 
said it made the list very easy to take in at a glance.
-- 
- DML


More information about the jboss-as7-dev mailing list