[JBoss JIRA] (SHRINKWRAP-395) ShrinkWrap should be able to exclude its own and Arquillian's -impl archives
10:40 p.m.
Craig Ringer created SHRINKWRAP-395:
---------------------------------------
Summary: ShrinkWrap should be able to exclude its own and Arquillian's
-impl archives
Key: SHRINKWRAP-395
URL: https://issues.jboss.org/browse/SHRINKWRAP-395
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Environment: Linux wallace 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21
22:07:10 UTC 2011 i686 i686 i386 GNU/Linux
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
JBoss AS 7.1.1.Final
Arquillian 1.0.0.Final
Reporter: Craig Ringer
I'm using ShrinkWrap via Arquillian 1.0.0.Final.
When the Maven Dependency Resolver extension is used to load dependencies from a project
pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced
ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to
leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of
Arquilian and ShrinkWrap archives
and dependencies. Some of the transitive dependencies could cause conflicts with app
server libraries, too.
What I'd like to see is a very quick and easy way to tell the Maven resolver to
exclude
anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg:
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml");
.excludeShrinkWrap().excludeArquillian(); // Imaginary for now
Currently one should be able to do something like:
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee",
"org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven",
"org.jboss.arquillian.junit:arquillian-junit-container",
"org.jboss.as:jboss-as-arquillian-container-remote");
... but in my quick tests it appeared to have no effect.
--
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
7:21 a.m.
[
https://issues.jboss.org/browse/SHRINKWRAP-395?page=com.atlassian.jira.pl...
]
Craig Ringer updated SHRINKWRAP-395:
------------------------------------
Description:
I'm using ShrinkWrap via Arquillian 1.0.0.Final.
When the Maven Dependency Resolver extension is used to load dependencies from a project
pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced
ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to
leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of
Arquilian and ShrinkWrap archives
and dependencies. Some of the transitive dependencies could cause conflicts with app
server libraries, too.
What I'd like to see is a very quick and easy way to tell the Maven resolver to
exclude
anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml");
.excludeShrinkWrap().excludeArquillian(); // Imaginary for now
{code}
Currently one should be able to do something like:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee",
"org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven",
"org.jboss.arquillian.junit:arquillian-junit-container",
"org.jboss.as:jboss-as-arquillian-container-remote");
{code}
... but in my quick tests these exclusions appeared to have no effect.
was:
I'm using ShrinkWrap via Arquillian 1.0.0.Final.
When the Maven Dependency Resolver extension is used to load dependencies from a project
pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced
ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to
leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of
Arquilian and ShrinkWrap archives
and dependencies. Some of the transitive dependencies could cause conflicts with app
server libraries, too.
What I'd like to see is a very quick and easy way to tell the Maven resolver to
exclude
anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg:
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml");
.excludeShrinkWrap().excludeArquillian(); // Imaginary for now
Currently one should be able to do something like:
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee",
"org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven",
"org.jboss.arquillian.junit:arquillian-junit-container",
"org.jboss.as:jboss-as-arquillian-container-remote");
... but in my quick tests it appeared to have no effect.
Forum Reference: https://community.jboss.org/message/729492 (was:
https://community.jboss.org/message/729492)
ShrinkWrap should be able to exclude its own and Arquillian's
-impl archives
----------------------------------------------------------------------------
Key: SHRINKWRAP-395
URL: https://issues.jboss.org/browse/SHRINKWRAP-395
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Environment: Linux wallace 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21
22:07:10 UTC 2011 i686 i686 i386 GNU/Linux
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
JBoss AS 7.1.1.Final
Arquillian 1.0.0.Final
Reporter: Craig Ringer
Labels: arquillian, dependency, maven, resolver, shrinkwrap
I'm using ShrinkWrap via Arquillian 1.0.0.Final.
When the Maven Dependency Resolver extension is used to load dependencies from a project
pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced
ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to
leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of
Arquilian and ShrinkWrap archives
and dependencies. Some of the transitive dependencies could cause conflicts with app
server libraries, too.
What I'd like to see is a very quick and easy way to tell the Maven resolver to
exclude
anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml");
.excludeShrinkWrap().excludeArquillian(); // Imaginary for now
{code}
Currently one should be able to do something like:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee",
"org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven",
"org.jboss.arquillian.junit:arquillian-junit-container",
"org.jboss.as:jboss-as-arquillian-container-remote");
{code}
... but in my quick tests these exclusions appeared to have no effect.
--
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
2:18 a.m.
New subject: [JBoss JIRA] (SHRINKRES-30) ShrinkWrap should be able to exclude its own and Arquillian's -impl archives
[
https://issues.jboss.org/browse/SHRINKRES-30?page=com.atlassian.jira.plug...
]
Andrew Rubinger commented on SHRINKRES-30:
------------------------------------------
Craig, does a filter-based approach fit this need for you, or are you suggesting that the
API needs to be altered to accommodate this use case in a different fashion?
ShrinkWrap should be able to exclude its own and Arquillian's
-impl archives
----------------------------------------------------------------------------
Key: SHRINKRES-30
URL: https://issues.jboss.org/browse/SHRINKRES-30
Project: ShrinkWrap Resolvers
Issue Type: Feature Request
Environment: Linux wallace 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21
22:07:10 UTC 2011 i686 i686 i386 GNU/Linux
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
JBoss AS 7.1.1.Final
Arquillian 1.0.0.Final
Reporter: Craig Ringer
Labels: arquillian, dependency, maven, resolver, shrinkwrap
I'm using ShrinkWrap via Arquillian 1.0.0.Final.
When the Maven Dependency Resolver extension is used to load dependencies from a project
pom, the ShrinkWrap and Arquillian dependencies are automatically included in produced
ShrinkWrap archives. There doesn't appear to be any easy way to tell ShrinkWrap to
leave its own -impl archives out, so a trivial test archive bloats to 31MB or more of
Arquilian and ShrinkWrap archives
and dependencies. Some of the transitive dependencies could cause conflicts with app
server libraries, too.
What I'd like to see is a very quick and easy way to tell the Maven resolver to
exclude
anything from ShrinkWrap or Arquillian when loading dependencies from a pom.xml, eg:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml");
.excludeShrinkWrap().excludeArquillian(); // Imaginary for now
{code}
Currently one should be able to do something like:
{code}
MavenDependencyResolver resolver =
DependencyResolvers.use(MavenDependencyResolver.class)
.includeDependenciesFromPom("pom.xml")
.exclusions("org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee",
"org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven",
"org.jboss.arquillian.junit:arquillian-junit-container",
"org.jboss.as:jboss-as-arquillian-container-remote");
{code}
... but in my quick tests these exclusions appeared to have no effect.
--
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
5104
days inactive
5113
days old
shrinkwrap-issues@lists.jboss.org
2 comments
2 participants
participants (2)
-
Andrew Rubinger (JIRA) -
Craig Ringer (JIRA)