Community
Participate
Working Groups
2 days ago a project at eclipse published a new artifact org.eclipse.core:runtime:jar:3.9.100-v20131218-1515 in Maven central http://central.maven.org/maven2/org/eclipse/core/runtime/3.9.100-v20131218-1515/runtime-3.9.100-v20131218-1515.pom Unlike its previous version (http://central.maven.org/maven2/org/eclipse/core/runtime/3.9.0-v20130326-1255/runtime-3.9.0-v20130326-1255.pom) it isn't using a range for its dependency (org.eclipse.equinox:app) but a fixed version (1.0.0) not available in central. <dependency> <groupId>org.eclipse.equinox</groupId> <artifactId>app</artifactId> - <version>[1.0.0,2.0.0)</version> + <version>1.0.0</version> <optional>false</optional> </dependency> Due to this change many builds are broken all over the world (I found several people complaining on twitter too). Please help us to have quickly a fix in Maven central.
Is there a way to tell who / how this project got there? http://repo.eclipse.org does not contain anything by that name.
I don't see how to find it ourselves. We need to ask to sonatype if its not coming from your foundation. I will open an issue in https://issues.sonatype.org/browse/MVNCENTRAL to ask them to tell us where it is coming from
Reported here : https://issues.sonatype.org/browse/MVNCENTRAL-431 Let see what they say ...
Moving to platform->runtime where org.eclipse.core.runtime is, but I have the same questions as Pascal.
Guys, Joel from Sonatype replied to me : https://issues.sonatype.org/browse/MVNCENTRAL-431?focusedCommentId=213261&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-213261 It seems to be a third party upload from Pieter Martin as the uploader <pieter.martin@gmail.com>. Perhaps you know him in the eclipse community ? Could you contact him to understand his need and find a solution ? I can do it if you prefer but I really don't know these artifacts and won't be able to debate a lot about why he needed to do it (and why he shouldn't have done this). Arnaud
I'll reach out to Pieter to see what are his needs. However even knowing what his needs are (which are probably "I just want artifacts to be central"), the same old discussion of who is going to do the work to put the artifacts in central on a regular basis is going to come back and haunt us.
Hi, I have uploaded the runtime.jar with the dependency changed as indicated. It is waiting for sonatype 3rd party upload approval. I generated the original jars by running mvn eclipse:to-maven on a eclipse kepler sr2 installation. It is from there that the pom's dependency versions come. Indeed "I just want artifacts to be central", and am not involved with eclipse foundation nor with the projects whos artifacts I upload. My own requirements are for the eclipse uml and ocl projects. Thanks Pieter
It is in maven central. http://search.maven.org/#artifactdetails|org.eclipse.core|runtime|3.9.100-v20131218-1515|jar
Sonatype just updated the POM ? :( Nobody will see the update due to maven behavior to never update released artifacts. In my case I know it thus I'll do the necessary cleanup but for others ...
Pieter, thanks for the quick turnaround on this issue. > Indeed "I just want artifacts to be central", and am not involved with > eclipse foundation nor with the projects whos artifacts I upload. Would you be interested in doing the same work but from the Eclipse Foundation infrastructure? This would not be any different than what you are doing now but it would be done from the Eclipse Foundation machines so we would have official Foundation artifacts in Central.
(In reply to Arnaud Heritier from comment #9) > Sonatype just updated the POM ? :( > Nobody will see the update due to maven behavior to never update released > artifacts. > In my case I know it thus I'll do the necessary cleanup but for others ... Bah that's weird... :(
closing
In maven central. PW
