[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-360) Create "Library Dependency" module

[Andrew Rubinger (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKWRAP-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Rubinger updated SHRINKWRAP-360:
---------------------------------------

    Description: 
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.

  was:
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 two places: one as a standard dependency, and once as "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.


    
> Create "Library Dependency" module
> ----------------------------------
>
>                 Key: SHRINKWRAP-360
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-360
>             Project: ShrinkWrap
>          Issue Type: Feature Request
>          Components: ext-resolver
>            Reporter: Andrew Rubinger
>
> 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