You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2008/06/04 15:29:45 UTC
[jira] Created: (WSS-124) Get maven dependencies pushed to central
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: Ruchith Udayanga Fernando
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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Closed: (WSS-124) Get maven dependencies pushed to central
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-124.
-----------------------------------
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Assigned: (WSS-124) Get maven dependencies pushed to central
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh reassigned WSS-124:
---------------------------------------
Assignee: Colm O hEigeartaigh (was: Fred Dushin)
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-124) Get maven dependencies pushed to central
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-124.
-------------------------------------
Resolution: Fixed
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-124) Get maven dependencies pushed to
central
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-124) Get maven dependencies pushed to
central
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636038#action_12636038 ]
Colm O hEigeartaigh commented on WSS-124:
-----------------------------------------
We can remove the repository section of our pom once opensaml gets deployed into the central maven repo.
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-124) Get maven dependencies pushed to central
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Dushin updated WSS-124:
----------------------------
Fix Version/s: 1.5.5
Assignee: Fred Dushin (was: Ruchith Udayanga Fernando)
> 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: Fred Dushin
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-124) Get maven dependencies pushed to
central
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637577#action_12637577 ]
Glen Mazza commented on WSS-124:
--------------------------------
OpenSAML has its own repository though:
https://spaces.internet2.edu/display/OpenSAML/OSTwoUsrManJavaInstall (see bottom of page)
Can't you use this one? BTW, any problem with WSS4J upgrading to OpenSAML 2.0 (it can work with both SAML 1.x or 2.0 assertions) -- or is just a manpower/time-constraints issue?
Glen
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org