[
https://issues.jboss.org/browse/SHRINKDESC-100?page=com.atlassian.jira.pl...
]
Andrew Rubinger moved SHRINKWRAP-376 to SHRINKDESC-100:
-------------------------------------------------------
Project: ShrinkWrap Descriptors (was: ShrinkWrap)
Key: SHRINKDESC-100 (was: SHRINKWRAP-376)
Component/s: (was: ext-resolver)
Fix Version/s: 1.2.0-alpha-2
(was: resolver-2.0.0-alpha-1)
(was: resolver-1.1.0-alpha-2)
Create SWD "depchain" module
----------------------------
Key: SHRINKDESC-100
URL:
https://issues.jboss.org/browse/SHRINKDESC-100
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Fix For: 1.2.0-alpha-2
Also called a "A-BOM" in EAP, or "depchain" in AS, this POM
aggregates dependencies for a project, in the right scope, in one view:
For instance:
{code}foo-api
foo-impl
foo
dep:
foo-api (compile)
foo-impl (runtime){code}
In this case, "foo" would be the module we're looking to create. A user
then makes a dependency upon this POM in coordination with a dep on the BOM in
"import" scope in depMgt (in order to honor exclusions).
An example of this in use is:
https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L128
https://github.com/ALRubinger/jboss-as-test-example/blob/master/pom.xml#L156
In the example above we have the dep on the AS7 API in two places as required; in turn
the AS7 API POM exports out transitives as we need. In that case the AS7 API is both BOM
and Library POM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira