I was using the word "artefact" in a generic sense. That spelling of
the word is correct English.
I am in no way suggesting that any Maven artifact published to Maven
central should reference Maven artifacts in an Eclipse repository. I
don't know what the exact impact on this is, but I assume that pom
files that reference Eclipse Foundation Maven server artifacts would
have to be changed before being pushed to Maven Central.
We can push original artifacts into the Eclipse Maven repository.
There's no specific requirement that says only OSGi-ified bundles
can go there. In fact, I've suggested that we use the Eclipse-based
Maven repository as a place to put "raw" JAR files for consumption
by Orbit. At some point in the future, we need to put some energy
into changing how Orbit works, and having it work from and push to
an Eclipse Foundation-run Maven repository seems to make sense.
We do want to play well with the rest of the world. Again, I look to
the RT PMC for guidance; how can we be confident that the artifacts
pulled from Maven Central exactly match the JAR files that have been
approved by the IP Team?
Wayne
On 03/12/2014 12:49 PM, Joakim Erdfelt
wrote:
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|