I suggest talking to them about components, cohesion and various other buzzwords although it sounds like you might be fighting a losing battle if your team are too stubborn to run builds.
Separating your application into individual components with clearly defined responsibilities makes a lot of sense for all sorts of reasons which aren't really relevant to this list. Maintaining the source for these components in separate source trees, and treating each component as separate artifacts with it's own Maven project.xml with interdependencies and versioning managed via the very easy to use Maven dependency mechanism has worked very well for me and my team. If my understanding of your team's desire to "keeping parts of the app together" is to construct one monolithic source tree with no independent versioning of components then maybe your team isn't ready for Maven yet and you should focus on introducing some of the more basic principles of OOD. Matt. > -----Original Message----- > From: Brill Pappin [mailto:[EMAIL PROTECTED] > Sent: 29 June 2004 14:03 > To: Maven Users List > Subject: Re: RFE for the war plugin > > Actually I don't really have much of a problem with Eclipse, > other than I have to keep the parts of an app together... > remember I'm one of the group who is trying to get the old > fuddy-duddies around here to use Maven, so not everyone would > "get it" if the parts of an app where spread all over the repository. > > I'm having a hard enough time getting people to build with > maven (despite it being easier)... I've even got a couple of > guys that won't even *execute* it on our development box to > build an app, for no reason other than being stubbourn. > > BTW - A little off topic but following that last thought -- I > see Mavens value, but if you want to gain more support and > remove some of the roadblocks (for me at least) you have to > target the agile folks; we are an agile shop but its they are > who are the ones bulking even though Maven fits right into > agile practice. > > - Brill Pappin > > Matt Read wrote: > > >What problems do you have with Eclipse? I do exactly this across a > >project with many components which are re-used in various > combinations > >of .ear and .war files using the Maven dependency mechanism > and have no > >problems at all using Eclipse as my IDE. > > > >Matt. > > > > > > > >>-----Original Message----- > >>From: Brill Pappin [mailto:[EMAIL PROTECTED] > >>Sent: 29 June 2004 13:38 > >>To: Maven Users List > >>Subject: Re: RFE for the war plugin > >> > >>Yes, I thought of doing that very thing :) however I then have > >>problems with Eclipse as it doesn't understand > multi-project builds, > >>and you really want all the parts of an application in the > same place. > >> > >>Still doable, but less than optimum. > >> > >>- Brill > >> > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
