Broken by design

[Jan Wedel <Ja...@ettex.de>]

Hi,

while I was searching for a Perl plugin for maven, I found this link in 
interesting discussion:

http://fishbowl.pastiche.org/2007/12/20/maven_broken_by_design/

Since this is quite old, I guess this was already discussed on this 
list. I am interested if there are solutions for the mentioned problems.

At first maven looks like an attractive girl. But I've got a little idea 
that this girls is gonna get real "bitchy" once put a ring on her finger 
and live together.

What I'm trying to say is, the idea behind maven is promising. But maybe 
you end up dealing with maven repository and resolution issues as well 
as plugin version issues instead of working on your project. I can 
remember other colleagues telling my "Damn, I spend the last day 
resolving a maven problem...".

I especially have concerns about the reliability and repeatability 
issues. Transitive resolving is a really helpful, but it would be nice 
if you could do it just once and then have everything on your internal 
repository, frozen within a version and not having maven touching it 
again... And if you need to reproduce an earlier version, you just need 
to check out that particular version and have everything together 
instead of maven starting to search for plugins again.

Any comment is appreciated!

Jan

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

RE: Broken by design

[Todd Thiessen <th...@nortel.com>]

 
> We have had some problems with build reproduciblity though. 
> But it was because of downloading artifacts.

Sorry... I meant so say here... It was NOT because of downloading
artifacts...

Bah. Friday morning... Brain is still not in gear ;-).

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

RE: Broken by design

[Todd Thiessen <th...@nortel.com>]

> I can remember other 
> colleagues telling my "Damn, I spend the last day resolving a 
> maven problem...".

Before Maven, I would spend just as much, if not more time, fighting
with builds.

As for the link you provided, I think there is some truth to it. But in
my view the pros far out way the cons. So ya sure Maven may need to
download artifacts a lot. But because everything is modular, very rarely
do you need to compile a lot of code. This greatly speeds up build
times. So overall, we have seen our build times actually decrease when
we went to Maven, not increase.

And having a local repo manager does solve most of the issues discussed
on that blog (in my view anyway). Contrary to what the author states.

We have had some problems with build reproduciblity though. But it was
because of downloading artifacts. I believe, although I have not
confirmed, is that a plugin is behaving differently on Windows than it
does on Linux.

But I wouldn't say this is a core Maven issue and conclude that Maven is
"broken by design".  I would say the design is very sound.

My 2 cents...

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