[
https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640663#action_12640663
]
Fred Dushin commented on WSS-124:
---------------------------------
As opensaml is not a requirement for use of WSS4J (with the exception of a
blemish in 1.5.4, that is fixed for 1.5.5), we can work around this by making
the opensaml libraries provided scope in the wss4j POM.
FWIW, the opensaml authors are opposed to deploying opensaml 1.x into maven, as
it is no longer supported software. So yes, we should migrate to OpenSAML 2,
whose APIs are stable.
Dan, are you open to this strategy? (I suppose it means that any CXF users are
on their own to locate the SAML libs)
> Get maven dependencies pushed to central
> ----------------------------------------
>
> Key: WSS-124
> URL: https://issues.apache.org/jira/browse/WSS-124
> Project: WSS4J
> Issue Type: Task
> Components: WSS4J Core
> Affects Versions: 1.5.4
> Reporter: Daniel Kulp
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.5
>
>
> Having a pom for wss4j is great, but the repository entry really need to be
> removed and the dependencies that are in the ws repository need to be pushed
> to central (and also have poms for them). For things like opensaml, you
> can follow the guide at:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> For xmlsec, you will need to work with the xmlsec folks to get someone on
> that group to properly sign the artifacts and get them into the sync
> repository on people.apache.org.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
