Got a bit lost on this thread :)

I agree, Gump should parse Maven POMs (sorry Niclas, if that leaves
you on your own :)
However, I added the mapping to allow projects to fix themselves until
that time arrives. It seems we've gotten to the point where the
generated descriptor is correct (I just have to remove property as it
is a duplicate of what is already generated, and add an optional id
element). I'll release a new version of the gump plugin to use.

Anywhere were we have mismatched projects (so several maven projects
declaring a dependency differently), that's something that probably
needs to be fixed from the Maven end. We manage the central
repository, so we can push to doing that.

If we are able to do this, do the combination of these two solutions
solve our problems now, and going forward?

Let's start a list of JAR names that have conflicts. Please add them here:
http://jira.codehaus.org/browse/MAVEN-1534
or if they are those pesky sun ones we can't distribute:
http://jira.codehaus.org/browse/MAVEN-1472

I'll do what I can to resolve them.

- Brett

On Mon, 13 Dec 2004 10:48:58 -0500, Stefano Mazzocchi
<[EMAIL PROTECTED]> wrote:
> Niclas Hedhman wrote:
> > On Monday 13 December 2004 16:24, Stefan Bodewig wrote:
> >
> >
> >>I think at least Stefan(o) prefer Gump an approach where Gump can
> >>parse Maven POMs directly.
> >
> >
> > :o) Cool. But you are back to some of the problems listed for approach "1.",
> > e.g.  there are artifacts that are not inter-project consistent.
> > So, POM *alone* is not enough, but can remove the need for a "gump" goal in
> > Maven.
> 
> Yep. POM alone is not enough, we should start thinking about a "registry
> of project names" on where everybody can agree upon.
> 
> Brett, what's your opinion on this?
> 
> --
> Stefano.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to