[
https://issues.jboss.org/browse/AS7-5941?page=com.atlassian.jira.plugin.s...
]
Horia Chiorean updated AS7-5941:
--------------------------------
Description:
In order for ModeShape 3.1 to be productized, we were asked to update our build system and
only use the _jboss-as-parent-7.1.2.Final_ BOM, importing it in our
_<dependencyManagement>_ section.
While trying to do so, we've identified a couple of blocker issues (from our
perspective) with the BOM:
*1.* Some of the core artifacts which we need: Infinispan and Resteasy to name a few, have
almost all (if not all) of their mandatory transitive dependencies excluded from the BOM.
For example, in the case of _infinispan-core_, the _jboss-marhshalling_ and
_jboss-marshalling-river_ dependencies are required for some basic test cases/uses. We
don't use these directly in our API, but Infinispan uses them by default in many
cases. The only workaround is to redefine these dependencies (in order to avoid the
excludes) in our pom(s) which defeats the entire purpose of a BOM.
*2.* Since we're based on Infinispan, a lot of our modules use for testing
Infinispan's _test-jar_ artifact which isn't present in the BOM. Again, to work
around this we're basically having to define a local dependency with a version and the
_<type>test-jar<type>_
was:
In order for ModeShape 3.1 to be productized, we were asked to update our build system and
only use the _jboss-as-parent-7.1.2.Final_ BOM, importing it in our
_<dependencyManagement>_ section.
While trying to do so, we've identified a couple of blocker issues (from our
perspective) with the BOM:
*1.* Some of the core artifacts which we need: infinispan and resteasy to name a few, have
almost all (if not all) of their mandatory transitive dependencies excluded from the BOM.
For example, in the case of _infinispan-core_, the _jboss-marhshalling_ and
_jboss-marshalling-river_ dependencies are required for some basic test cases/uses. We
don't use these directly in our API, but Infinispan uses them by default in many
cases. The only workaround is to redefine these dependencies (in order to avoid the
excludes) in our pom(s) which defeats the entire purpose of a BOM.
*2.* Since we're based on Infinispan, a lot of our modules use for testing
Infinispan's _test-jar_ artifact which isn't present in the BOM. Again, to work
around this we're basically having to define a local dependency with a version and the
_<type>test-jar<type>_
The jboss-as-parent-7.1.2 BOM excludes mandatory transitive
dependencies for artifacts and/or has missing artifact types
------------------------------------------------------------------------------------------------------------------------
Key: AS7-5941
URL:
https://issues.jboss.org/browse/AS7-5941
Project: Application Server 7
Issue Type: Bug
Components: Build System
Affects Versions: 7.1.2.Final (EAP)
Reporter: Horia Chiorean
Assignee: Paul Gier
Priority: Critical
In order for ModeShape 3.1 to be productized, we were asked to update our build system
and only use the _jboss-as-parent-7.1.2.Final_ BOM, importing it in our
_<dependencyManagement>_ section.
While trying to do so, we've identified a couple of blocker issues (from our
perspective) with the BOM:
*1.* Some of the core artifacts which we need: Infinispan and Resteasy to name a few,
have almost all (if not all) of their mandatory transitive dependencies excluded from the
BOM. For example, in the case of _infinispan-core_, the _jboss-marhshalling_ and
_jboss-marshalling-river_ dependencies are required for some basic test cases/uses. We
don't use these directly in our API, but Infinispan uses them by default in many
cases. The only workaround is to redefine these dependencies (in order to avoid the
excludes) in our pom(s) which defeats the entire purpose of a BOM.
*2.* Since we're based on Infinispan, a lot of our modules use for testing
Infinispan's _test-jar_ artifact which isn't present in the BOM. Again, to work
around this we're basically having to define a local dependency with a version and the
_<type>test-jar<type>_
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira