Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of carlossg@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=nAN1yGvaBXxCsvmwdxVjEsd/TRE6IwNyPwSzRetV1Zv+yG9MXc4r9Nbq+o7AZFsNvyZATr/LpOBqcDrjmYVjh3667mp62D5v+Yt7QXS90cT4xIeiUx1c4v7SFjEYujEgg0QIYlSsoAbGMdOt/Ws7s5yn4zpadqFphR4jEor6nj4=
Message-ID: <1a5b6c410607050319y6135ea78n1e660462ef84ef93@mail.gmail.com>
Date: Wed, 5 Jul 2006 12:19:56 +0200
From: "Carlos Sanchez" <carlos@apache.org>
Sender: carlossg@gmail.com
To: "Maven Developers List" <dev@maven.apache.org>
Subject: Re: [RANT] This Maven thing is killing us....
In-Reply-To: <23DDF46D-900A-4757-B884-A8F67EFE1360@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <FDD5D99066749040AF9098A720E9897701CA1830@CIWMEXZSA0E.ex.ordersx.org>
	 <98e4f1cd0607040434k1c0f7ddeo8e9ddf0899c15b7e@mail.gmail.com>
	 <1a5b6c410607040553r6c20b441j81ec638465d9f10d@mail.gmail.com>
	 <44AA6F0E.8040908@apache.org>
	 <572953DF-61AA-4732-93A9-54BAAF4CCD15@maven.org>
	 <b20ce4ed0607041556m3baec6cej4a181e5587946274@mail.gmail.com>
	 <1a5b6c410607041716j46dfbaefx223ba79854593292@mail.gmail.com>
	 <3804BE82-1FA8-4309-BAFD-D32C7CB6FE97@yahoo.com>
	 <44AB1703.3050507@apache.org>
	 <23DDF46D-900A-4757-B884-A8F67EFE1360@yahoo.com>

On 7/5/06, David Jencks <david_jencks@yahoo.com> wrote:
>
> On Jul 4, 2006, at 6:33 PM, Brett Porter wrote:
>
> > On 5/07/2006 10:54 AM, David Jencks wrote:
> >> I think the process is somewhat broken and that the maven team is
> >> being far too strict about changing broken poms that were in fact
> >> installed by the maven team, not supplied by the project.
> >> (xmlbeans is the case in point for me).  I also think that
> >> traceability of where poms came from and under what auspices they
> >> are added to either the repository svn tree or ibiblio is sorely
> >> lacking.  (again xmlbeans being my sore spot).  We are in the
> >> situation where a pom appeared from an unknown source, is wrong,
> >> did not come from the project, and can't be updated.  Much as I
> >> like maven it's hard for me to see how this is going to lead to
> >> success.
> >
> > David,
> >
> > I thought we'd agreed to fix that up? I can't find the issue on it
> > other than http://jira.codehaus.org/browse/MEV-406 which is not the
> > one I recall (that one is about stax which is a whole other problem
> > beyond the scope of Maven too).
>
> that's the one.  The xmlbeans pom does not have the required stax-api
> dependency listed in it.  As that issue notes, Carlos declined to
> change the existing pom.  IIUC Carlos said I needed to get xmlbeans
> to produce the pom, which I am currently working on, see http://
> issues.apache.org/jira/browse/XMLBEANS-277

The problem is that people want a stable repo, you just have to check
this thread. If I could go back in time I wouldn't do the
autogeneration of poms.

Another issue I've already seen several times is patches to fix poms
that at the end where not the *right* fix. For instance people saying
that dependency A is missing, so it's added. Then somebody else uses
it differently and then dependency B is missing. I don't want that to
happen again.

>
> The xmlbeans team have agreed in principle to cooperate but have not
> in fact yet reviewed my first draft for things like correct urls.  I
> originally planned to produce a complete set of poms for their 3 jars
> and 3 releases but am not sure how to test one of them.    To me it
> seems like its turned into an enormous amount of work to fix a really
> obvious problem.  One of the most frustrating things for me is that
> there is no way to find out where the existing wrong poms came from.

Brett has a good suggestion about adding traceability to uploaded
poms. But I can tell you that if the pom only has group, artifact and
version is coming from the early times of the repo autogenerated it
from a missing pom in the m1 repo.
Things from Apache, Codehaus, Objectweb,... come synced from their repos.

> Second most frustrating was that the MEV instructions turned out to
> be 100% inaccurate, so following them to the letter was a complete
> waste of time.

Sorry about that, now they are changed, not sure if they have been deployed yet.

>
> There was another problem with the maven xmlbeans plugin that Kris
> Bravo fixed immediately.
>
> thanks
> david jencks
>
> >
> > - Brett
> >
> > --
> > Brett Porter <brett@apache.org>
> > Apache Maven - http://maven.apache.org/
> > Better Builds with Maven - http://library.mergere.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org