not sure why geronimo isn't representitive of what maven can do. they have an extremely modular codebase, and are building a J2EE server, so it seems perfectly logical that J2EE applications could follow the same model.
project.properties are inherited. I'm doing a very similar thing with my project. want a "real world" example? see https://shard.dev.java.net/source/browse/shard/ for my open source project. I'll gladly talk with you more about how I got around the problems you describe. -----Original Message----- From: jerome lacoste [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 10:16 AM To: Maven Users List Subject: Re: Why I hate Maven :-) On 6/15/05, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > take a look at geronimo for a LARGE project using maven. I haven't looked at geronimo's code, but sometimes large may not mean representative. For example I have a client who has a typical J2EE webapp + some webstart thick clients. One of these thick clients has two configurations. It's packaged as the same jar, but depending on the parameters in the JNLP file, it will trigger a different internal module. Following maven's rule of one artifact per project, I've created 3 projects, one for the jar file, one for each of the 2 JNLP. The JNLP plugin makes us put the properties in the project.properties which cannot be inherited. So I end up with 2 very similar projects, with the same dependencies, and almost the same project.properties. Then I've got to merge these resulting artifacts inside the same directory for deployment. In that particular case, I find that maven (or the JNLP plugin) gets in my way. It was much cleaner with Ant. Sometimes "best practise" and productivity don't go hand in hand. Cheers, Jerome PS: if someone knows a clean solution to my issue... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
