[
https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279344#comment-279344
]
Dustin Parker commented on MSHADE-103:
--------------------------------------
In one of our company's projects, shade tries to resolve using the repositories
defined in the module's parent:
{code:xml}
<repositories>
<repository>
<id>download.osgeo.org</id>
<url>http://download.osgeo.org/webdav/geotools</url>
</repository>
<repository>
<id>JBOSS</id>
<name>JBoss Repository</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</repository>
</repositories>
{code}
(Yep, the JBoss one is out of date.) It doesn't consult settings.xml, though.
Also, the parent POM it's trying to find is already in ~/.m2/repository. Our
workaround is to put our company repository in that section, which makes sense
anyway. Running it once with the workaround caused the parent POM to be
downloaded AGAIN. Subsequent times, the POM was NOT redownloaded. Also, if you
have a repository manager like Nexus configured on your machine as a mirror for
*, this avoids the problem. Oddly enough, the problem didn't happen on Jenkins
even though neither of these workarounds was present.
Actually, now that I think about it, is this by design? This is producing an
artifact, the dependency-reduced POM, and its contents should be predictable,
not dependent on what a particular developer has in her settings.xml...
> maven-shade-plugin does not resolve from user-defined repositories
> ------------------------------------------------------------------
>
> Key: MSHADE-103
> URL: https://jira.codehaus.org/browse/MSHADE-103
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.3.3, 1.4
> Environment: Maven 3.0.3 (works with 2.2.1)
> Reporter: Lukas Fryc
>
> maven-shade-plugin doesn't consult repositories defined in
> settings.xml when trying to resolve parents of given pom. It contacts
> only central repo:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:1.4:shade (default) on
> project richfaces-components-api: Error creating shaded jar: 1 problem
> was encountered while building the effective model for
> org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT
> [ERROR] [FATAL] Non-resolvable parent POM for
> org.richfaces:richfaces-bom:4.1.0-SNAPSHOT: Could not find artifact
> org.richfaces:richfaces-parent:pom:10 in central
> (http://repo1.maven.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ org.richfaces:richfaces-bom:4.1.0-SNAPSHOT,
> /home/lfryc/workspaces/richfaces/build/bom/pom.xml, line 24, column 10
> [ERROR] for project
> org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at
> /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml
>
> for project org.richfaces.ui:richfaces-components-api:4.1.0-SNAPSHOT at
> /home/lfryc/workspaces/richfaces/components/dist/richfaces-components-api/dependency-reduced-pom.xml
>
> [ERROR] -> [Help 1]
> There is affected project (it references version 1.3.3, but the behavior is
> same with 1.4) if you would like to try at own:
> https://github.com/richfaces/components/blob/develop/dist/richfaces-components-api/pom.xml
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
