February 2013 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-109) Maven resolver: can't resolve POM artifact which is part of the Reactor but not installed in Repository

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-109?page=com.atlassian.jira.plu... ] Lukáš Fryč updated SHRINKRES-109: --------------------------------- Summary: Maven resolver: can't resolve POM artifact which is part of the Reactor but not installed in Repository (was: Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository) > Maven resolver: can't resolve POM artifact which is part of the Reactor but not installed in Repository > ------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-109 > URL: https://issues.jboss.org/browse/SHRINKRES-109 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Lukáš Fryč > Assignee: Andrew Rubinger > > Scenario where you have multi-module repository, e.g.: > {code} > richfaces-bom > richfaces-framework > ... > {code} > where {{richfaces-framework}} depends on {{richfaces-bom}}, > having tests in the {{richfaces-framework}}. > --- > When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. > You need to run {{mvn install}}. > --- > Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... > Issue: > {{richfaces5/> $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true}} > {code} > ... > Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: > org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) > {code} -- 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-109) Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-109?page=com.atlassian.jira.plu... ] Lukáš Fryč updated SHRINKRES-109: --------------------------------- Description: Scenario where you have multi-module repository, e.g.: {code} richfaces-bom richfaces-framework ... {code} where {{richfaces-framework}} depends on {{richfaces-bom}}, having tests in the {{richfaces-framework}}. --- When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. You need to run {{mvn install}}. --- Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... Issue: {{richfaces5/> $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true}} {code} ... Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) {code} was: Scenario where you have multi-module repository, e.g.: {code} richfaces-bom richfaces-framework ... {code} where {{richfaces-framework}} depends on {{richfaces-bom}}, having tests in the {{richfaces-framework}}. --- When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. You need to run {{mvn install}}. --- Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... Issue: {code} $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true ... Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) {code} > Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-109 > URL: https://issues.jboss.org/browse/SHRINKRES-109 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Lukáš Fryč > Assignee: Andrew Rubinger > > Scenario where you have multi-module repository, e.g.: > {code} > richfaces-bom > richfaces-framework > ... > {code} > where {{richfaces-framework}} depends on {{richfaces-bom}}, > having tests in the {{richfaces-framework}}. > --- > When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. > You need to run {{mvn install}}. > --- > Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... > Issue: > {{richfaces5/> $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true}} > {code} > ... > Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: > org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) > {code} -- 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-109) Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-109?page=com.atlassian.jira.plu... ] Lukáš Fryč updated SHRINKRES-109: --------------------------------- Description: Scenario where you have multi-module repository, e.g.: {code} richfaces-bom richfaces-framework ... {code} where {{richfaces-framework}} depends on {{richfaces-bom}}, having tests in the {{richfaces-framework}}. --- When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. You need to run {{mvn install}}. --- Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... Issue: {code} $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true ... Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) {code} was: Scenario where you have multi-module repository, e.g.: {code} richfaces-bom richfaces-framework ... {code} where {{richfaces-framework}} depends on {{richfaces-bom}}, having tests in the {{richfaces-framework}}. --- When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. You need to run {{mvn install}}. > Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-109 > URL: https://issues.jboss.org/browse/SHRINKRES-109 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Lukáš Fryč > Assignee: Andrew Rubinger > > Scenario where you have multi-module repository, e.g.: > {code} > richfaces-bom > richfaces-framework > ... > {code} > where {{richfaces-framework}} depends on {{richfaces-bom}}, > having tests in the {{richfaces-framework}}. > --- > When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. > You need to run {{mvn install}}. > --- > Sample: https://github.com/richfaces/richfaces5/blob/462d5377cb4301e287ada576b906... > Issue: > {code} > $ mvn verify -Pbrowser-firefox -Dintegration=jbossas -DskipTests=true > ... > Feb 12, 2013 12:27:09 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener transferFailed > WARNING: Failed downloading org/richfaces/richfaces-bom/5.0.0-SNAPSHOT/richfaces-bom-5.0.0-SNAPSHOT.pom from https://repository.jboss.org/nexus/content/groups/public/. Reason: > org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.richfaces:richfaces-bom:pom:5.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) > {code} -- 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-109) Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository

by Lukáš Fryč (JIRA)

Lukáš Fryč created SHRINKRES-109: ------------------------------------ Summary: Maven resolver: can't resolve Artifact which is part of the Reactor but not installed in Repository Key: SHRINKRES-109 URL: https://issues.jboss.org/browse/SHRINKRES-109 Project: ShrinkWrap Resolvers Issue Type: Component Upgrade Components: impl-maven Affects Versions: 2.0.0-beta-2 Reporter: Lukáš Fryč Assignee: Andrew Rubinger Scenario where you have multi-module repository, e.g.: {code} richfaces-bom richfaces-framework ... {code} where {{richfaces-framework}} depends on {{richfaces-bom}}, having tests in the {{richfaces-framework}}. --- When using {{Maven}} resolver, running {{mvn verify}} will fail to resolve {{richfaces-bom}} since it is not installed in local repository. You need to run {{mvn install}}. -- 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 José Freitas (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-101?page=com.atlassian.jira.plu... ] José Freitas commented on SHRINKRES-101: ---------------------------------------- My bad. I had an alpha-7 snapshot on that moment. > 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-56) Performance Audit

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-56?page=com.atlassian.jira.plug... ] Andrew Rubinger updated SHRINKRES-56: ------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.0.0-beta-2 Resolution: Done Upstream: https://github.com/shrinkwrap/resolver/commit/7c756492c750f00dedea65b478d... > 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 > Fix For: 2.0.0-beta-2 > > > 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-108) ClasspathWorkspaceReader Ignores Requested Version During Resolution

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-108?page=com.atlassian.jira.plu... ] Andrew Rubinger updated SHRINKRES-108: -------------------------------------- Fix Version/s: 2.0.0-beta-2 > ClasspathWorkspaceReader Ignores Requested Version During Resolution > -------------------------------------------------------------------- > > Key: SHRINKRES-108 > URL: https://issues.jboss.org/browse/SHRINKRES-108 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > Fix For: 2.0.0-beta-2 > > > When resolving an artifact that may be resolved by the ClasspathWorkspaceReader, the requested version is ignored and incorrect version may be returned. -- 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-108) ClasspathWorkspaceReader Ignores Requested Version During Resolution

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-108?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-108. --------------------------------------- Resolution: Done Upstream: https://github.com/shrinkwrap/resolver/commit/29e1564048ffc446937e35b0790... > ClasspathWorkspaceReader Ignores Requested Version During Resolution > -------------------------------------------------------------------- > > Key: SHRINKRES-108 > URL: https://issues.jboss.org/browse/SHRINKRES-108 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > > When resolving an artifact that may be resolved by the ClasspathWorkspaceReader, the requested version is ignored and incorrect version may be returned. -- 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-108) ClasspathWorkspaceReader Ignores Requested Version During Resolution

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-108: ----------------------------------------- Summary: ClasspathWorkspaceReader Ignores Requested Version During Resolution Key: SHRINKRES-108 URL: https://issues.jboss.org/browse/SHRINKRES-108 Project: ShrinkWrap Resolvers Issue Type: Bug Reporter: Andrew Rubinger Assignee: Andrew Rubinger When resolving an artifact that may be resolved by the ClasspathWorkspaceReader, the requested version is ignored and incorrect version may be returned. -- 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 updated SHRINKRES-56: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/35 > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues February 2013