Hi Ray, I would really appreciate the assistance on addressing this concern. One complication in the past for publishing eclipse things to mavin central was how to handle 3rd party dependencies we get from orbit. But with Equinox pretty low on the stack I think many of our bundles will not run into this issue. For example the framework and our osgi specification implementations.
Tom From: Raymond Auge <[email protected]> To: Equinox development mailing list <[email protected]> Date: 08/29/2014 12:03 AM Subject: Re: [equinox-dev] milestones in a maven repo Sent by: [email protected] With some help from @mcculls I've learned that anyone (third parties) can request any artifact to be publishing into a Maven Central group provided that the artifact can plainly be linked back to the project/domain owner, the artifact is open source, the project owners have not claimed the group (not the official wording). The process is defined here: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository Specifically in this case, anyone can ask to have artifacts published which were generated by the eclipse release process into the org.eclipse group and subgroups. Until a representative of equinox steps forward to claim org.eclipse.osgi (and associated) group(s) this chaos will continue. Here's the process: https://issues.sonatype.org/secure/CreateIssue.jspa?issuetype=21&pid=10134 So, will equinox take on this challenge? I'm willing to donate some time to this effort. I believe there are no technical barriers to doing this. However, I'm willing to help work through those that exist. Lastly, I've been pointed to and will comment on this issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=365798 Sincerely, - Ray On Fri, Aug 22, 2014 at 11:19 AM, Raymond Auge <[email protected]> wrote: Someone is at least publishing the framework to MC even though it seems to be very delayed. 3.10.0-v20140606-1445 was published just on Aug 1. http://search.maven.org/#browse%7C-552727178 Can whomever is doing that please update this artifact to the lastest SR1? (3.10.1.v20140807-1950) I'd really appreciate it. - Ray On Fri, Aug 22, 2014 at 10:59 AM, Pascal Rapicault <[email protected]> wrote: The barrier are ease of implementation, desire and time from the current committers. These could be overcome with contributions. On 22/08/2014 1:26 PM, Raymond Auge wrote: Hey All, I'd like to ask again what is the barrier to getting milestone builds into a maven repo? I mean https://repo.eclipse.org/content/repositories/eclipse/ exists. Why not extend it's use for publishing milestones? Wouldn't it quite literally be a single extra command invoked during the release process? -- Raymond Augé (@rotty3000) Senior Software Architect Liferay, Inc. (@Liferay) _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev -- Raymond Augé (@rotty3000) Senior Software Architect Liferay, Inc. (@Liferay) -- Raymond Augé (@rotty3000) Senior Software Architect Liferay, Inc. (@Liferay) _______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
