Since our JBoss Developer Materials BOMs are aligned with a single
product I don't have any objections on it. Does anyone have any?
It also can be included as part of EAP build.
If we move forward, how will we name it? My proposal:
org.jboss.bom.eap:jboss-javaee-7.0-bom
On 4/9/15 11:46, Paul Gier wrote:
Hi Everyone,
I'd like to propose that we consolidate our current JBoss EAP BOMs into
a single BOM. We currently have several smallish BOMs with names like
"jboss-javaee-6.0-with-hibernate" and
"jboss-javaee-6.0-with-security".
Instead I think we could make a single BOM which contains all public
API jar versions and is used throughout the quickstarts whenever an API
is needed.
The specs project would continue to provide a JavaEE specs BOM for
simple use cases. And the eap BOM project would provide the JavaEE APIs
and public EAP specific APIs. Note that using this BOM in a quickstart
would not cause the quickstart to download "all" the API jars, the BOM
only manages the versions of the jars which have already been added to
the dependency tree.
The advantage of this is easier maintenance and a simpler configuration
for users who currently use more than one of our current BOMs in their
application.
WDYT?
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper