[
https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522438#comment-17522438
]
Rob Leland commented on WSS-687:
--------------------------------
[~coheigea]
The short answer is I haven't found a way to custom taylor what artifacts from
from what repos, but I do have a suggestion.
I have asked that same question when working with multiple repos with older
artifacts. In the early days circa ~ 2002-2007 Maven central allowed
republishing release artifacts, for the same release on one day the release
would be built using a Solaris JDK then a few days later it would be built
using an Apple JDK and it drove me crazy! I have also worked with multiple
internal repos that were originally clones of a parent repo but have sense
diverged and this also resulted in nasty scenarios.
*What I have done*
Groom the effective POM so the repositories id's are in alpa order and that
will be the order that maven will resolve artifacts.
As long as Maven central is always available , i.e. a DDoS is not taking
place then it will meet your needs.
{noformat}
<repositories>
<repository>
<id>A_MavenCentral</id>
<name>Maven Central</name>
...
</repository>
<repository>
<id>B_OpenSaml</id>
<name>Maven Central</name>
...
</repository>
</repositories>
{noformat}
I prepend 'A', 'B', 'C' to the 'id' to ensure that maintaining repo order is a
no brainer.
I don't see a settings file in wss4j and suggest adding one as opposed to hard
coding the repositories in the parent pom.xml but that is up to you.
run
{noformat}
mvn help:effective-pom
{noformat}
To verify the change.
> Upgrade OpenSAML to v4.1.x
> --------------------------
>
> Key: WSS-687
> URL: https://issues.apache.org/jira/browse/WSS-687
> Project: WSS4J
> Issue Type: Task
> Components: WSS4J Core
> Affects Versions: 3.0.0
> Reporter: Misagh Moayyed
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> wss4j 2.5.0.SNAPSHOT currently uses OpenSAML v4.0.x. Current release of
> OpenSAML is 4.1.1 and wss4j should upgrade to this version. No breaking
> changes are expected.
> I can assist with a patch or pull request.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
