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: [email protected] For additional commands, e-mail: [email protected]
