Re: [weld-dev] Maven Archetype Bill of Materials - How should we handle minor variations in point releases of Java EE 6 containers?

Hello All, The Weld archetypes need to be updated to reflect the latest Weld 1.0.1 release. Presently, we're using the weld-extensions-bom <dependency> <groupId>org.jboss.weld</groupId> <artifactId>weld-extensions-bom</artifactId> <version>1.0.0-CR2</version> <type>pom</type> <scope>import</scope> </dependency> The immediate issue is that the archetypes need to reflect the changes. The hairier issue is dealing with minor point release differences Now there's 2 variants of weld in the wild, via 2 Java EE containers. Glassfish has weld-1.0.0 and JBoss 6 will have 1.0.1. Should this be reflected via different BOMs? Should there be a weld-jboss-6.0.0-bom? glassfish-v3-bom? Presumably, down the road, there will be more variants as other APIs have minor point increases. If not, does anyone have suggestions for dealing with trivial variations in versions between container point releases? Thanks, Steven _______________________________________________ weld-dev mailing list weld-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev