search

me0wster / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

External repository referenced in the pom but unreachable #194

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ensure you don't have jrobin-1.5.9 in your local maven repository
2. set net.bull.javamelody:javamelody-core:1.34.0 as a dependency
3. mvn package

What is the expected output? What do you see instead?
transitive dependency jrobin:1.5.9 should be downloaded

What version of the product are you using?
net.bull.javamelody:javamelody-core:1.34.0

Please provide any additional information below.
I noticed a repository <id>m.g.o-public</id> 
<url>http://maven.glassfish.org/content/groups/public/</url> is defined in the 
javamelody pom.xml, but I can't reach 
http://maven.glassfish.org/content/groups/public. 
Is the repository still alive ? 
Setting a mirror fixed the issue but I think you shouldn't set a repository 
definition in the javamelody pom.xml file.

Original issue reported on code.google.com by huchet.j...@gmail.com on 7 Mar 2012 at 5:02

GoogleCodeExporter commented 9 years ago 
This repository is currently down for maintenance.
I suppose that this repository will probably be alive again soon given that it 
is used a lot, for example for some official JavaEE artefacts.

And what would really solve the issue would be that the JRobin maven dependency 
is published in maven central.
Please vote for it (sign up if needed):
http://issues.opennms.org/browse/JRB-20

Can we do this ourselves?

Original comment by evernat@free.fr on 7 Mar 2012 at 11:27

GoogleCodeExporter commented 9 years ago 
In their guide 
(https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usag
e+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement), 
Sonatype explain that pom shouldn't contain elements <repository/> nor 
<pluginRepository/>. This maintenance case may be one of the reasons. 

I just read in the guide that it's possible to upload third-party artifacts : 
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Th
e+Central+Repository.

Original comment by huchet.j...@gmail.com on 8 Mar 2012 at 10:23

GoogleCodeExporter commented 9 years ago 
Yes it's true that Sonatype says that pom shouldn't contain elements 
<repository/>.
But it is also Sonatype which has first published the javamelody's pom with the 
<repository/> element.

That said I will volunteer to publish jrobin artefacts. This will solve the 
issue.

Original comment by evernat@free.fr on 8 Mar 2012 at 6:41

GoogleCodeExporter commented 9 years ago

Original comment by evernat@free.fr on 18 Mar 2012 at 12:00

GoogleCodeExporter commented 9 years ago

Original comment by evernat@free.fr on 28 Mar 2012 at 8:46

GoogleCodeExporter commented 9 years ago

Original comment by evernat@free.fr on 28 Mar 2012 at 8:49

GoogleCodeExporter commented 9 years ago 
The jrobin dependency is now available in the Maven central repository as you 
can see here:
http://search.maven.org/#artifactdetails|org.jrobin|jrobin|1.5.9|jar

You Maven builds should find it automatically in Maven central since March, the 
23rd.

The external repository referenced in the javamelody-core pom.xml file is now 
useless and it has been removed (revision 2688).

Original comment by evernat@free.fr on 28 Mar 2012 at 8:57