• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • ehcache
  • Reporter: sslavic
  • December 05, 2009
  • 0
  • Watchers: 2
  • August 09, 2012
  • October 12, 2010


[ehcache-1.7.1.pom http://repo2.maven.org/maven2/net/sf/ehcache/ehcache/1.7.1/ehcache-1.7.1.pom] contains reference to external (non maven central) repository, thus not adhering to the rules for deploying artifacts to maven central repository (see “FAQ and common mistakes” in official [“Guide to uploading artifacts to the Central Repository” http://maven.apache.org/guides/mini/guide-central-repository-upload.html]).


gluck 2009-12-06

The repositories mentioned are only used for building snapshots, because central does not provide a snapshot repository feature.

It is not required for normal building or use.

We could strip those out before publishing to central, as a release step.

Fiona OShea 2009-12-16

please do this as part of release can we automate

gluck 2010-10-12

No current complaints

Brian Demers 2012-08-09

Please reopen, this is still a problem. http://repo1.maven.org/maven2/net/sf/ehcache/ehcache/2.6.0/ehcache-2.6.0.pom

[CentralSyncRequirement - Sonatype OSSRH https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement]

Greg, your first comment was a while ago, but for future googlers: You should not strip out the repository tag as a release step (if done wrong would violate your checksum). The element should be removed. All that is needed is the distributionManagement element.