Support resolving Artifacts directly from Workspace
---------------------------------------------------
Key: SHRINKWRAP-366
URL: https://issues.jboss.org/browse/SHRINKWRAP-366
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Reporter: Aslak Knutsen
Assignee: Karel Piwko
MavenDependencyResolver should be able to resolve artifacts from the Workspace if they exist to avoid having to install to repo upfront. This is especially interesting when working from the IDE.
--
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
Introduce BOM for SWD
---------------------
Key: SHRINKWRAP-359
URL: https://issues.jboss.org/browse/SHRINKWRAP-359
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Reporter: Andrew Rubinger
Assignee: Karel Piwko
Create a BOM module and pom.xml to align the api, api-maven, impl-maven versions in dependencyManagement
--
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
Make SW BOM have no parent
--------------------------
Key: SHRINKWRAP-367
URL: https://issues.jboss.org/browse/SHRINKWRAP-367
Project: ShrinkWrap
Issue Type: Task
Reporter: Andrew Rubinger
Karel notes that in order to ease w/ production process (which mutates the jboss-parent POM and may add dependencies), we should remove the parent from the BOM POM and instead fork off the maven-release-plugin configuration under pluginManagement.
--
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
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 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#L128https://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.
--
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