[JIRA] Commented: (JOST-178) Host OpenSAML Maven repositories on Maven Central?

[gmazza@idp.protectnetwork.org (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/JOST-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763#comment-13763 ] 

gmazza at idp.protectnetwork.org commented on JOST-178:
----------------------------------------------------

OK.  I don't think that you should have to manually maintain and upload third-party dependencies that OpenSAML needs on Maven Central.  Rather, if OpenSAML indeed needs obscure/rare dependencies that can't be found on Maven Central, ideally, I think a better direction would be for OpenSAML to be rearchitected so it can easily run with just the vanilla dependencies already available on Maven Central.  Being able to host OpenSAML on Maven Central makes an excellent architectural statement that the product runs on common, simple, well-maintained dependencies that are already available on Maven Central.

> Host OpenSAML Maven repositories on Maven Central?
> --------------------------------------------------
>
>                 Key: JOST-178
>                 URL: https://issues.shibboleth.net/jira/browse/JOST-178
>             Project: OpenSAML 2 - Java
>          Issue Type: Improvement
>          Components: SAML 2
>    Affects Versions: 2.5.2, 2.5.3
>            Reporter: gmazza at idp.protectnetwork.org
>            Assignee: Chad La Joie
>            Priority: Minor
>
> Hi, my OpenSAML tutorial[1]--both the present one and the since-deleted 3.5 year old one that preceded it before 29 Dec. 2011--is being heavily read from my blog--with 238 reads since 1 December 2011, it ranks as my 13th most popular article.  I think that will increase even more given that all reads before 29 December 2011 were only to the largely out-of-date 3.5 year old article, and the newer one is being read quite a bit longer (5min 20sec vs 3min 40sec for the older article.)
> Anyway, it would be nice if OpenSAML went more mainstream--i.e., its artifacts pushed to Maven Central so it's no longer needed to bring in a custom Shibboleth repository while using it.  Availability on Maven Central increases usage both by making it simpler to incorporate and easier to advocate to others its incorporation into projects.  Sonatype of course encourages[2] it.  My Talend colleague Colm O Higeartaigh (Apache WSS4J and CXF teams) had started the process for version 2.5.1 but if this could one "officially" from the Shibboleth team for later versions that would be a great help.
> [1] http://www.jroller.com/gmazza/entry/opensaml_with_web_services
> [2] https://docs.sonatype.org/display/Repository/Central+Sync+Requirements

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira