Even better would be if maven could just read the required info from the manifest and build.properties. Then all the normal tooling just works.
Dear all, According to Jeff below, this means that Equinox in maven central is "rogue"... so if we want to push the idea through, we'd need someone to take this job (who? me? I was hoping someone else would, hehe...), and also get authorization to maven central since we presume getting permission from Eclipse community was the easy bit...
In case the pre-bureaucracy goes well, a technical improvement would be to add/modify POMs in Equinox projects so they can be 'mvn deploy'-ed easily by anyone having proper access to maven central. I assume this will be slightly more convoluted, but still possible, and probably good for the long run.
Any comments/suggestions? ---------- Forwarded message ---------- From: Jeff McAffer < jeff@xxxxxxxxx> Date: Fri, Jun 13, 2008 at 1:32 AM
Subject: RE: [orbit-dev] Orbit Maven repository To: Orbit Developer discussion < orbit-dev@xxxxxxxxxxx> Cc: General OPS4J < general@xxxxxxxxxxxxxxx>
Thanks for your interest in Orbit. As you may know, the current
Maven repo content was put together by someone (not sure who) completely
independent of the Eclipse team. We had no input on how it was structured or
what was put there.
To your specific question, there are currently no plans to
create or maintain a Maven repository at eclipse.org. We will be creating and
hosting a p2 repository however. My understanding is that Maven has an extensible
repository structure such that it could be extended to read other repository
layouts. Perhaps if there were a p2 repo plugin for Maven then Maven users
could point directly at the eclipse.org repositories.
In the mean time however, it seems like the best path is for the
Maven user community to agree on the format for bundles in Maven repos and then
populate the standard Maven repo with the upcoming Ganymede release.
Jeff
Dear Orbit developers,
I had this discussion with the OPS4J community.
We're having difficulty getting Equinox-related artifacts using Maven... which
now our current approach is to host them (Equinox artifacts) within OPS4J Maven
repository.
The current Equinox artifacts at maven central are outdated and also having
inconsistent JAR versioning/naming (versus the ones in eclipse.org/orbit).
We're looking forward to having "official" Equinox maven artifacts
hosted on Maven central or perhaps if Orbit also has a Maven repository. Even
better if Eclipse maven artifacts can also be there too. Thank you.
---------- Forwarded message ----------
From: Peter Neubauer <peter.neubauer@xxxxxxxxx>
Date: Thu, May 29, 2008 at 3:44 PM
Subject: Re: Equinox version format
To: General OPS4J <general@xxxxxxxxxxxxxxx>
Cc: Costin Leau <costin.leau@xxxxxxxxx>
Hi there,
On Thu, May 29, 2008 at 10:39 AM, Hendy Irawan <hendy@xxxxxxxxxxxxxxxxx> wrote:
> Wouldn't it be natural to suggest Orbit maintainers to use a Maven
> compatible repository structure?
> What do you guys think? I guess Orbit should be a
natural place to host
> Equinox itself and Equinox-related bundles right? (i.e.
pseudo-"certified
> for Equinox" stuff)
Yes, true,
who is taking contact? If you want to put some force behind this, go
ahead, it would be great to have a good repo to build against!
/peter
--
GTalk: neubauer.peter
Skype peter.neubauer
ICQ 18762544
GTalk neubauer.peter
Phone +46704 106975
LinkedIn http://www.linkedin.com/in/neubauer
http://www.neo4j.org - New
Energy for Data - the Graph Database.
--
Best regards,
Hendy Irawan
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
-- Best regards, Hendy Irawan
|