I have been reading up on Maven2 for a project at work. It pretty much handles everything about a project (managing dependecies, documentation, tests etc.).
I wonder if something similar would benefit the Perl community or is there something out there that I don't know about or even "it is a bad idea".
Maven == CPAN? (Score:1)
I don't know much about Maven specifically, but your description sounds like a CPAN modules.
Re: (Score:1)
Re: (Score:1)
In the case of CPAN it does these things in very, very d
Beware (Score:1)
Maven: Broken By Design [pastiche.org].
Re: (Score:1)
Re: (Score:2)
1) It imposes its own worldview on How Things Should Work (e.g., only one source tree per 'module') that require you to develop, package or deploy differently.
2) Hand in hand with that, it's a "drink the kool-aid" project -- you need to know how things work to figure out how they should work. For instance, Ant has a simple way to ask "What targets can I run with this buildfile?" Maven has no useful implementation of such a thing (the list
Re: (Score:1)
Re: (Score:2)
And, of course, all this just applies to the one implementation; there's nothing that says a copy needs to copy all the warts
Re: (Score:1)
That is what I was thinking as well.
Re: (Score:2)
I've just witnessed several experienced developers at work have their projects delayed by weeks, as they are converting to Maven. Not in one big go. Just the continual rounds of “why is the build broken now?” adding up. To me, the benefits don't seem to outweigh the flaws.
Re: (Score:1)
Re: (Score:2)