[
https://issues.jboss.org/browse/SHRINKWRAP-243?page=com.atlassian.jira.pl...
]
jay shaughnessy commented on SHRINKWRAP-243:
--------------------------------------------
has the fix version been corrected? I have resolver 1.0.0-beta-7 in my M2 repo yet I seem
to be hit by this. Or is perhpas because we encounter the problem only on jenkins runs,
which has additional proxy situation described here:
http://stackoverflow.com/questions/6291146/arquillian-shrinkwrap-mavendep...
To get around this I was able to add resolver.goOffline() at the problem point, because at
that point I am assured of the dep being in the local repo. This seems to work.
Dependencies does not find remote repositories set in settings.xml
------------------------------------------------------------------
Key: SHRINKWRAP-243
URL:
https://issues.jboss.org/browse/SHRINKWRAP-243
Project: ShrinkWrap
Issue Type: Feature Request
Components: ext-resolver
Reporter: Aslak Knutsen
Assignee: Karel Piwko
Fix For: 1.0.0-alpha-12
Using activeDefault profiles in settings.xml does not seem to be included in the remote
repository resolution in Dependencies.
e.g.
.m2/settings.xml
<profiles>
<profile>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<
url>http://repository.jboss.org/nexus/content/groups/public/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<
url>http://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
--
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