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

Chad La Joie (JIRA) noreply at shibboleth.net
Thu Jan 5 13:49:25 GMT 2012


     [ https://issues.shibboleth.net/jira/browse/JOST-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie closed JOST-178.
-----------------------------

    Resolution: Won't Fix

This has been discussed before by the developers, the short answer is it's not going to happen.  The main roadblock is that we rely on libraries that are not themselves published to maven central and we are not going to take on the responsibility of making sure their releases do get published there.

If all our dependencies ever make it in to maven central and are regularly maintained then we'll re-examine this.  But for now people are just going to have to live with the hardship of adding a the 4 lines to their POM necessary to use the Shib repo.

> 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


More information about the commits mailing list