[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-29) Artifacts from dependencyManagement imported pom not resolved

Karel Piwko (JIRA) jira-events at lists.jboss.org
Thu Apr 19 11:32:18 EDT 2012


     [ https://issues.jboss.org/browse/SHRINKRES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karel Piwko updated SHRINKRES-29:
---------------------------------

        Fix Version/s: 2.0.0-alpha-1
                           (was: 2.0.0-alpha-2)
    Affects Version/s: 1.0.0-beta-7
                       1.1.0-alpha-3

    
> Artifacts from dependencyManagement imported pom not resolved
> -------------------------------------------------------------
>
>                 Key: SHRINKRES-29
>                 URL: https://issues.jboss.org/browse/SHRINKRES-29
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 1.1.0-alpha-3, 1.0.0-beta-7
>         Environment: JBoss AS 7.1.1.Final
> java version "1.7.0_01"
> Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)
> Linux ayaki.localdomain 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Craig Ringer
>            Assignee: Karel Piwko
>              Labels: dependency, maven, resolver
>             Fix For: 2.0.0-alpha-1
>
>         Attachments: ArquillianShrinkwrapImportPom.zip
>
>
> ShrinkWrap's Maven Dependency Resolver (version 1.0.0-beta-5, also tested with 1.0.0-beta-6) fails to resolve artifacts where the version is specified by an imported bom in the dependencyManagement section, or where the artifact isn't in central even if it's in a repo listed by the project's pom.xml.
> See the attached self contained test case. Examine DemoTest.java; you'll see two different artifact co-ordinates for Seam 3 Security, neither of which works. The project's pom finds seam 3 security fine via the imported seam 3 bom, but the shrinkwrap dependency resolver doesn't even after loading the project's pom.xml via configureFrom(...) .
> If I use the co-ordinates:
>   org.jboss.seam.security:seam-security
> ShrinkWrap fails with:
>   java.lang.IllegalArgumentException: Bad artifact coordinates, expected format is <groupId>:<artifactId>[:<extension>[:<classifier>]]:<version>
> if I specify a version explicitly (which shouldn't be necessary since it's in the seam 3 bom imported via dependencyManagement) it instead says it can't find the artifact in Central, even though the jboss repo is listed in pom.xml:
>   org.jboss.seam.security:seam-security:3.1.0.Final
> produces:
>   org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.jboss.seam.security:seam-security:jar:3.1.0.Final in central (http://repo1.maven.org/maven2)

--
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

        


More information about the shrinkwrap-issues mailing list