July 2015 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-221) The same artifact is downloaded multiple times from different repositories.

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-221?page=com.atlassian.jira.plu... ] Matous Jobanek closed SHRINKRES-221. ------------------------------------ Fix Version/s: 2.2.0-beta-2 Resolution: Duplicate Issue I'm closing this issue as duplicate as it was already fixed in 2.2.0-beta-2 > The same artifact is downloaded multiple times from different repositories. > --------------------------------------------------------------------------- > > Key: SHRINKRES-221 > URL: https://issues.jboss.org/browse/SHRINKRES-221 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.1.1 > Environment: Shrinkwrap Resolver 2.1.1 > Reporter: Christopher Hobbs > Fix For: 2.2.0-beta-2 > > > When downloading dependencies using multiple repositories, the artifact is downloaded multiple times: once from each repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-221) The same artifact is downloaded multiple times from different repositories.

by Christopher Hobbs (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-221?page=com.atlassian.jira.plu... ] Christopher Hobbs commented on SHRINKRES-221: --------------------------------------------- Thanks for the heads up. I'm fine with you closing this. > The same artifact is downloaded multiple times from different repositories. > --------------------------------------------------------------------------- > > Key: SHRINKRES-221 > URL: https://issues.jboss.org/browse/SHRINKRES-221 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.1.1 > Environment: Shrinkwrap Resolver 2.1.1 > Reporter: Christopher Hobbs > > When downloading dependencies using multiple repositories, the artifact is downloaded multiple times: once from each repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-221) The same artifact is downloaded multiple times from different repositories.

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-221?page=com.atlassian.jira.plu... ] Matous Jobanek commented on SHRINKRES-221: ------------------------------------------ Hi Christopher, thanks for reporting. The behavior you are describing is performed by Eclipse Aether itself. Aether is a library for working with maven artifact repositories and this library is used in ShrinkWrap Resolver. You can be confused why the log is created by the classes of ShrinkWrap Resolver: {{org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener}} {{org.jboss.shrinkwrap.resolver.impl.maven.logging.LogRepositoryListener}} The classes are only log listeners - they observe events fired by the Aether and log the activities appropriately. This issue has been already reported: [MNG-5723|https://issues.apache.org/jira/browse/MNG-5723] and also fixed in the Maven 3.2.5. This new Maven is included in [ShrinkWrap Resolver 2.2.0-beta-2|http://arquillian.org/blog/2015/04/11/resolver-2-2-0-beta-2/] - so, if you update to the newest version of Resolver you shouldn't observe this behavior any more. I'll close this issue as "duplicate issue" if you agree. > The same artifact is downloaded multiple times from different repositories. > --------------------------------------------------------------------------- > > Key: SHRINKRES-221 > URL: https://issues.jboss.org/browse/SHRINKRES-221 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.1.1 > Environment: Shrinkwrap Resolver 2.1.1 > Reporter: Christopher Hobbs > > When downloading dependencies using multiple repositories, the artifact is downloaded multiple times: once from each repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-223) ClasspathWorkspaceReader does not resolve version variables

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-223?page=com.atlassian.jira.plu... ] Matous Jobanek commented on SHRINKRES-223: ------------------------------------------ Hi Thorsten, thanks for the reproducer. >From the files included in the zip file I assume that you get this problem when running the code inside Eclipse (or similar IDE). I hadn't expected that - I thought that you have problem with running the code on command line with standard maven commands - hence, I wasn't able to reproduce it. If so - if you get the Error in Eclipse - then I'm afraid that this issue is more likely for M2Eclipse then for ShrinkWrap Resolver - Resolver parses the pom file and replaces the properties correctly. However, when it tries to resolve all the dependencies, maven looks for the artifacts into your local repository or tries to download from online repositories (when running online). I assume that in the case of M2Eclipse it also uses the generated /target directories. There you can see the generated pom file {{projectA/target/classes/META-INF/maven/com.knime/projectA/pom.xml}} where the version variable isn't replaced. This is why the artifact cannot be resolved inside the IDE. I've created a new jira for JBoss Tools: JBIDE-20215 There is a workaround: you can install with the command {{mvn clean install}} both the parent project and the projectA into your maven local repository, then all the artifacts will be resolved correctly. > ClasspathWorkspaceReader does not resolve version variables > ----------------------------------------------------------- > > Key: SHRINKRES-223 > URL: https://issues.jboss.org/browse/SHRINKRES-223 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-2 > Reporter: Thorsten Meinl > Attachments: resolver-bug.zip > > > The ClasspathWorkspaceReader does not resolve variables in artifact versions. We have an artifact whose version is a variable that is defined in its parent pom. "ClasspathWorkspaceReader.createFoundArtifact" reads the variable as-is and does not resolve it to the real version. However, when resolving the dependencies for the "root" artifacts (the one whose pom has been loaded by the resolver via "loadPomFromFile") version variables *are* resolved and therefore there will always be a mismatch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-225) Upgrade Aether and remove dependency on aether-connector-wagon

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-225?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-225. --------------------------------- Fix Version/s: 2.2.0-beta-2 Resolution: Duplicate Issue Hello [~mbarkley], I'm closing this issue as duplicate as it was already fixed in 2.2.0-beta-2. Please let me know if that does not fix the problem for you. Details: http://arquillian.org/blog/2015/04/11/resolver-2-2-0-beta-2/ Thanks, Karel > Upgrade Aether and remove dependency on aether-connector-wagon > -------------------------------------------------------------- > > Key: SHRINKRES-225 > URL: https://issues.jboss.org/browse/SHRINKRES-225 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Affects Versions: 2.1.1 > Reporter: Max Barkley > Fix For: 2.2.0-beta-2 > > > It is currently not possible to use Shrinkwrap as part of a project that depends on a version of Aether more recent than 0.9.M2. This is because Shrinkwrap depends on the artifact aether-connector-wagon which seems to have been replaced in newer versions of Aether by aether-connector-basic and aether-transport-wagon. > Upgrading this dependency would allow users depending on newer versions of Aether to use Shrinkwrap. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-225) Upgrade Aether and remove dependency on aether-connector-wagon

by Max Barkley (JIRA)

Max Barkley created SHRINKRES-225: ------------------------------------- Summary: Upgrade Aether and remove dependency on aether-connector-wagon Key: SHRINKRES-225 URL: https://issues.jboss.org/browse/SHRINKRES-225 Project: ShrinkWrap Resolvers Issue Type: Component Upgrade Affects Versions: 2.1.1 Reporter: Max Barkley It is currently not possible to use Shrinkwrap as part of a project that depends on a version of Aether more recent than 0.9.M2. This is because Shrinkwrap depends on the artifact aether-connector-wagon which seems to have been replaced in newer versions of Aether by aether-connector-basic and aether-transport-wagon. Upgrading this dependency would allow users depending on newer versions of Aether to use Shrinkwrap. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues July 2015