[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [rt-pmc] Re: [jetty-dev] jetty dependency's and 'releasing' within eclipse
|
On 18-Jul-09, at 10:07 AM, Jesse McConnell wrote:
Whatever scheme is selected to put things in Maven should work for
all
Eclipse things (not just special cases) and likely cannot expect that
thousands of bundles be renamed (either their BSN or their file
name).
That is the challenge here.
fwiw, I know that sonatype has worked on this issue in the past with
nexus, I believe working out a mechanic whereby a typical p2
repository can be referenced via maven convention without the forcing
of 1000's of bundle renames.
imo, once artifacts leave their maven central repository location what
they get named for their respective consumer is up to that consumer,
if they want to be named org.eclipse.foo_ver that is fine, or they
could be renamed to simply start.jar...the onus is on the comsumer to
make sure they know what is going on with things. If something like
nexus where you allow you to automatically download it in such a way
that it is named in the eclipse sanctioned way automatically, great!
I understand where you're coming from. We have worked from a slightly
different perspective where producers create self-describing modules
that people then build upon to create systems (rather than
internalizing to create the system). These modules are shared within
one system and have other constraints/expectations on them (e.g., disk
cohabitation) so should not generally be folded, perforated or
stapled. Relying on consumers to rename or otherwise modify the
components would lead to a proliferation of different "copies" and
potential challenges in understanding and managing systems that are
amalgams of components. This is why we have opted for burdening the
producer with these challenges.
Stepping back from the details and reasoning here, we have lots of
people producing bundles with Eclipse-convention BSN and file naming.
We need a model for putting these bundles into a Maven repo. AFAICT
that means figuring out what the group and artifact ids should be.
Perhaps someone has already figured this out?
the most important thing here to me is that we have eclipse bundles
available in the maven central repo with good transitive dependency
metadata in place in such a way that we can use standard build tooling
like maven or ant+ivy or buildr or whatever to access them.
preferably within the month :)
Honestly I think that that is a pretty tall order given it is summer
and that this approach has far-reaching consequences and should be
addressed by the broader community (e.g., Architecture Council). The
topic of Maven repos has been raised in the Architecture council
recently but nothing particular was decided AFAIK. We should look for
ways to enable your progress in the near-term without inadvertently
setting a precedent for the long term.
Jeff