Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
OpenID Authentication 1.0.2
-
None
-
None
Description
The org.apache.sling.auth.openid bundle includes the following repository definition in its pom.xml file
<repositories> <repository> <releases> <enabled>true</enabled> </releases> <id>dyuproject-repo</id> <name>dyuproject-repo</name> <url>http://dyuproject.googlecode.com/svn/repos/maven2</url> </repository> </repositories>
and the following dependencies
<dependency> <groupId>com.dyuproject</groupId> <artifactId>dyuproject-openid</artifactId> <version>1.1.7</version> </dependency> <dependency> <groupId>com.dyuproject</groupId> <artifactId>dyuproject-util</artifactId> <version>1.1.7</version> </dependency> <dependency> <groupId>com.dyuproject</groupId> <artifactId>dyuproject-json</artifactId> <version>1.1.7</version> </dependency>
Since we sync/upload these artifacts to maven central [1] we should consider following the recommendation of not adding repositories to POMs [2] . There is an open request in the dyuproject tracker [3] to upload the openid artifacts to Maven Central, but it's been there for almost two years, and the project hasn't seen much activity ( no commits since June 2011 ).
I see two ways around this issue:
- Use the sonatype service for uploading 3rd party bundles to Maven Central [4]
- Replace the com.dyuproject dependency with something different
Thoughts?
[1]: http://search.maven.org/#search|ga|1|org.apache.sling.auth.openid
[2]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement
[3]: http://code.google.com/p/dyuproject/issues/detail?id=32
[4]: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
Attachments
Issue Links
- relates to
-
SLING-5780 Remove org.apache.sling.auth.openid from build
-
- Closed
-
- mentioned in
-
Page Loading...