February 2013 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-56) Performance Audit

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-56?page=com.atlassian.jira.plug... ] Michal Matloka updated SHRINKRES-56: ------------------------------------ Description: Alongside the tasks listed in the linked forum Thread... When there are a lot of artifacts to resolve, the ClasspathWorkspaceReader takes an unreasonable about of time. Consider: {code}final File[] files = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeAndTestDependencies().as(File.class);{code} Determine the source of the bottleneck. Also review if we should continue with this enabled by default, or if should be switched on by the user when needed. was: Alongside the tasks listed in the linked forum Thread... When there are a lot of artifacts to resolve, the ClassPathWorkSpaceReader takes an unreasonable about of time. Consider: {code}final File[] files = Maven.resolver().configureFromPom("pom.xml").importRuntimeAndTestDependencies().as(File.class);{code} Determine the source of the bottleneck. Also review if we should continue with this enabled by default, or if should be switched on by the user when needed. > Performance Audit > ----------------- > > Key: SHRINKRES-56 > URL: https://issues.jboss.org/browse/SHRINKRES-56 > Project: ShrinkWrap Resolvers > Issue Type: Task > Affects Versions: 2.0.0-alpha-2 > Reporter: Andrew Rubinger > Assignee: Michal Matloka > > Alongside the tasks listed in the linked forum Thread... > When there are a lot of artifacts to resolve, the ClasspathWorkspaceReader takes an unreasonable about of time. Consider: > {code}final File[] files = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeAndTestDependencies().as(File.class);{code} > Determine the source of the bottleneck. Also review if we should continue with this enabled by default, or if should be switched on by the user when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-56) Performance Audit

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-56?page=com.atlassian.jira.plug... ] Michal Matloka reassigned SHRINKRES-56: --------------------------------------- Assignee: Michal Matloka (was: Andrew Rubinger) > Performance Audit > ----------------- > > Key: SHRINKRES-56 > URL: https://issues.jboss.org/browse/SHRINKRES-56 > Project: ShrinkWrap Resolvers > Issue Type: Task > Affects Versions: 2.0.0-alpha-2 > Reporter: Andrew Rubinger > Assignee: Michal Matloka > > Alongside the tasks listed in the linked forum Thread... > When there are a lot of artifacts to resolve, the ClassPathWorkSpaceReader takes an unreasonable about of time. Consider: > {code}final File[] files = Maven.resolver().configureFromPom("pom.xml").importRuntimeAndTestDependencies().as(File.class);{code} > Determine the source of the bottleneck. Also review if we should continue with this enabled by default, or if should be switched on by the user when needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-101) Problem to resolving maven dependencies in shrinkres alpha-6 when dependency is defined in the parent project.

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-101. --------------------------------- Resolution: Done Closed. > Problem to resolving maven dependencies in shrinkres alpha-6 when dependency is defined in the parent project. > -------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-101 > URL: https://issues.jboss.org/browse/SHRINKRES-101 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Environment: maven 3.0.4 > Reporter: José Freitas > Assignee: Karel Piwko > Labels: maven > Fix For: 2.0.0-alpha-7 > > > It seems that "Maven.resolver().loadPomFromFile("pom.xml").resolve(...)" is not resolving dependencies from effectivepom, cause it cannot find dependencies defined at the parent. > Please take a look at the gist below to understand the issue better: > https://gist.github.com/4451555 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-101) Problem to resolving maven dependencies in shrinkres alpha-6 when dependency is defined in the parent project.

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-101: ---------------------------------- Summary: Problem to resolving maven dependencies in shrinkres alpha-6 when dependency is defined in the parent project. (was: Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project.) > Problem to resolving maven dependencies in shrinkres alpha-6 when dependency is defined in the parent project. > -------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-101 > URL: https://issues.jboss.org/browse/SHRINKRES-101 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Environment: maven 3.0.4 > Reporter: José Freitas > Assignee: Karel Piwko > Labels: maven > Fix For: 2.0.0-alpha-7 > > > It seems that "Maven.resolver().loadPomFromFile("pom.xml").resolve(...)" is not resolving dependencies from effectivepom, cause it cannot find dependencies defined at the parent. > Please take a look at the gist below to understand the issue better: > https://gist.github.com/4451555 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-101) Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project.

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Karel Piwko reopened SHRINKRES-101: ----------------------------------- Reopening to change the description > Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project. > -------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-101 > URL: https://issues.jboss.org/browse/SHRINKRES-101 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Environment: maven 3.0.4 > Reporter: José Freitas > Assignee: Karel Piwko > Labels: maven > Fix For: 2.0.0-alpha-7 > > > It seems that "Maven.resolver().loadPomFromFile("pom.xml").resolve(...)" is not resolving dependencies from effectivepom, cause it cannot find dependencies defined at the parent. > Please take a look at the gist below to understand the issue better: > https://gist.github.com/4451555 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-101) Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project.

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-101: --------------------------------------- Definitely alpha-6. Alpha-7 did not exist at this was filled. > Problem to resolving maven dependencies in shrinkres alpha-7 when dependency is defined in the parent project. > -------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-101 > URL: https://issues.jboss.org/browse/SHRINKRES-101 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-alpha-6 > Environment: maven 3.0.4 > Reporter: José Freitas > Assignee: Karel Piwko > Labels: maven > Fix For: 2.0.0-alpha-7 > > > It seems that "Maven.resolver().loadPomFromFile("pom.xml").resolve(...)" is not resolving dependencies from effectivepom, cause it cannot find dependencies defined at the parent. > Please take a look at the gist below to understand the issue better: > https://gist.github.com/4451555 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-440) Create a CDI Archive

by George Gastaldi (JIRA)

George Gastaldi created SHRINKWRAP-440: ------------------------------------------ Summary: Create a CDI Archive Key: SHRINKWRAP-440 URL: https://issues.jboss.org/browse/SHRINKWRAP-440 Project: ShrinkWrap Issue Type: Feature Request Reporter: George Gastaldi A lot of projects do this to make the beans CDI enabled: {code} addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); {code} It would be nice to have a addBeansXml() method together with a CdiArchive (or maybe automatically add it as the default behavior). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-440) Create a CDI Archive

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-440?page=com.atlassian.jira.pl... ] George Gastaldi updated SHRINKWRAP-440: --------------------------------------- Description: A lot of projects do this to make an archive CDI-enabled: {code} addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); {code} It would be nice to have a addBeansXml() method together with a CdiArchive (or maybe automatically add it as the default behavior). was: A lot of projects do this to make the beans CDI enabled: {code} addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); {code} It would be nice to have a addBeansXml() method together with a CdiArchive (or maybe automatically add it as the default behavior). > Create a CDI Archive > --------------------- > > Key: SHRINKWRAP-440 > URL: https://issues.jboss.org/browse/SHRINKWRAP-440 > Project: ShrinkWrap > Issue Type: Feature Request > Reporter: George Gastaldi > > A lot of projects do this to make an archive CDI-enabled: > {code} > addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml")); > {code} > It would be nice to have a addBeansXml() method together with a CdiArchive (or maybe automatically add it as the default behavior). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-105) Support resolution of variables in Maven settings file

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-105?page=com.atlassian.jira.plu... ] Andrew Rubinger closed SHRINKRES-105. ------------------------------------- > Support resolution of variables in Maven settings file > ------------------------------------------------------ > > Key: SHRINKRES-105 > URL: https://issues.jboss.org/browse/SHRINKRES-105 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 1.0.0-beta-7 > Reporter: Thomas Segismont > Assignee: Thomas Segismont > Labels: maven, resolver > Fix For: 2.0.0-beta-1 > > > Variables in Maven settings file are not resolved. > For instance if you have this node in your settings : > {code:xml} > <localRepository>${user.home}/.m2/repository</localRepository> > {code} > then Shrinkwrap will create a _$\{user.home\}/.m2/repository_ in the project directory and use it as local repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-30) ShrinkWrap should be able to exclude its own and Arquillian's -impl archives

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-30?page=com.atlassian.jira.plug... ] Andrew Rubinger edited comment on SHRINKRES-30 at 2/4/13 9:51 AM: ------------------------------------------------------------------ Note to dev team: Create a test case for this using the 2.0.0-X API and ensure the global exclusions are working as expected. was (Author: alrubinger): Create a test case for this using the 2.0.0-X API and ensure the global exclusions are working as expected. > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues February 2013