Packages not available on Maven Central while p2 metadata saying so

[jochenberger]

The p2 metadata indicate that the artifacts are available on Maven Central, but they are not. That causes issues for third party apps that try to consume them, in this case the Spotless source code formatter (diffplug/spotless#2458 (comment)).
Would it be possible to publish the artifacts on Maven Central or, if that's not possible, remove those metadata entries?

[eric-milles]

Where does the metadata indicate this?

[jochenberger]

These are the relevant properties in the content.xml file:

It should be possible to disable that: #1618

[eric-milles]

I don't think that indicates Maven Central availability. The projects use Maven to build and so they have a groupId, artifactId, version and packaging type.

groovy-eclipse/base/org.eclipse.jdt.groovy.core/pom.xml

Line 9 in 1eaa31c

<groupId>org.codehaus.groovy.eclipse</groupId>

[jochenberger]

I'm afraid I don't know much about p2. @nedtwigg, could you please provide some insight?

[nedtwigg]

Across the p2 ecosystem, most artifacts don't specify maven coordinates. Of those that do specify maven coordinates, all of them that I have encountered have been available on maven central (speaking for jdt, groovy-eclipse in the past, wtp, cdt, m2e, etc).

It isn't a hard standard, it's just a heuristic which has worked for us until now.

[jochenberger]

Okay, then this is apparently a misunderstanding on my side.
I'm closing the issue. Sorry for the noise.

[eric-milles]

I'd have to look through the Tycho docs to figure out if they can be removed. For the most part, we are using defaults for the update site repo.

[jochenberger]

Could you please try whether #1618 changes anything?