[ http://issues.apache.org/jira/browse/DIR-196?page=all ]
Emmanuel Lecharny updated DIR-196:
----------------------------------
Attachment: build-failure.txt
A beautifull sample of maven "helping" logs ...
> Cannot build Trunks
> -------------------
>
> Key: DIR-196
> URL: http://issues.apache.org/jira/browse/DIR-196
> Project: Directory
> Issue Type: Bug
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Attachments: build-failure.txt
>
>
> Again, and I'm pretty sure this is not the last time, the trunks cannot be
> built...
> At this point, I really think we should *SERIOUSLY* consider switching from a
> so called "build system" (Maven 2) to something that may be not genious, but
> which _simply_ work.
> It's not the first time the build is broken, and I agree that somebody may
> have made an error while committing a pom.xml, but it's obviously insane that
> a simple error cannot be fixed because we can't figure out what is the origin
> of the error without checking every commits for the last modification which
> has caused the build to fail - if an only if a commmit is the culprit,
> because maven is really used to s***t its own pant by downloading new version
> of (broken) plugins -.
> I'm really fed up of maven. It's supposed to *help*, noy to make you loosing
> your time. And even if the hypothesis of me being a complete idiot - an
> option which cannot be discarded -, then maven whould be designed for idiots
> like me. This is not the case.
> Maven concepts looks like the current build of apache DS : totally broken.
> Let's ditch this piece of shi^h^hoftware out of our path. No more hurdles.
> Let's use make, ./configure, or simply ant. Somtheing that works. Thanks.
> NB : I'm more than pissed off.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
