|Re: [emf-dev] Publishing to Maven Central|
Stephan,I never publish anything to Maven. Sometimes other people do. It seems a bit of a free-for-all...
Sorry, Ed On 30.03.2017 17:45, Stephan Herrmann wrote:
Hi, It's that time again, now working on Neon.3 for Maven Central. During tests I came across an unmet dependency from SDK to EMF:org.eclipse.e4.ui.workbench depends on org.eclipse.emf.ecore.change [2.5.0,)where the latter is not to be found in any Maven repositories. Is that bundle intentionally excluded from Maven uploads, or could this easily be added (ideally for Neon.3 :) )? thanks, Stephan On 15.12.2016 21:41, Stephan Herrmann wrote:Hi EMF :) In https://bugs.eclipse.org/408760 I'm working on publishing all artifacts of the Eclipse Project to Maven Central. Initially, I naively thought, that this would comprise *everything* in the release repo of the Eclipse Project. Only later it dawned on me that artifacts from other projects are involved, too, notably: EMF :) Since we can only publish stuff where all dependencies already exist on Maven Central, and given that we are targeting to publish Neon.2 for which naturally no EMF artifacts are yet available on Maven Central here my questions: Does EMF routinely publish all artifacts to Central? When may we expect Neon.2 artifacts to be available? Is org.eclipse.emf the correct groupId for referring to EMF artifacts?Strangely, I see the latest EMF artifacts only in groupId org.eclipse.birt.runtime ?!?thanks, Stephan _______________________________________________ emf-dev mailing list emf-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit_______________________________________________ emf-dev mailing list emf-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top