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
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
EmptyStackException when adding a exclusion before a artifact using MavenDependencyResolver
-------------------------------------------------------------------------------------------
Key: SHRINKWRAP-361
URL: https://issues.jboss.org/browse/SHRINKWRAP-361
Project: ShrinkWrap
Issue Type: Bug
Components: ext-resolver
Affects Versions: 1.0.0-beta-5
Reporter: Aslak Knutsen
{code}
DependencyResolvers.use(MavenDependencyResolver.class)
.exclusion("javax.transaction:jta")
.artifacts("org.hibernate:hibernate-core:3.6.8.Final")
.resolveAsFiles())
{code}
{code}
Caused by: java.util.EmptyStackException
at java.util.Stack.peek(Stack.java:102)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.exclusion(MavenBuilderImpl.java:264)
at ...
{code}
--
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
MavenResolver does not take settings.xml specified on command line into account when resolving repositories
-----------------------------------------------------------------------------------------------------------
Key: SHRINKWRAP-292
URL: https://issues.jboss.org/browse/SHRINKWRAP-292
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Affects Versions: 1.0.0-beta-3
Reporter: Aslak Knutsen
Running Maven using the following startup args does not work with the MavenResovler, the new defined settings.xml is not read
mvn install -s settings.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Do not override version of maven-release-plugin from jboss-parent
-----------------------------------------------------------------
Key: SHRINKWRAP-363
URL: https://issues.jboss.org/browse/SHRINKWRAP-363
Project: ShrinkWrap
Issue Type: Task
Components: build
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
Do not override the maven-release-plugin version as inherited from jboss-parent (2.9, and we have 2.0 set).
--
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
Separate Archive API from what's needed by the underlying storage mechanism
---------------------------------------------------------------------------
Key: SHRINKWRAP-362
URL: https://issues.jboss.org/browse/SHRINKWRAP-362
Project: ShrinkWrap
Issue Type: Task
Reporter: Andrew Rubinger
Currently "Archive" is implemented by both ArchiveBase and ContainerBase. In truth, "Archive" is for the end-user view, and ArchiveBase is really used to centralize functions specific to doing underlying data storage. Separate these out such that ArchiveBase/MemoryMapArchive/MemoryMapArchiveImpl have a sane structure which clearly is centered around the operations necessary for ShrinkWrap's VFS, and don't abuse the Archive (end-user view) contract for these aims.
--
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
Fix Remote Repository handling from settings.xml files, enable central
----------------------------------------------------------------------
Key: SHRINKWRAP-355
URL: https://issues.jboss.org/browse/SHRINKWRAP-355
Project: ShrinkWrap
Issue Type: Bug
Components: ext-resolver
Reporter: Karel Piwko
Assignee: Karel Piwko
Priority: Blocker
Fix For: resolver-2.0.0-alpha-1
During 2.0.0 internal changes, following errors were introduced:
* Maven Central is no longer default enabled
* Loading settings.xml from classpath was broken
As testsuite is not using any remote artifacts, the change was not apparent from the testsuite.
--
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