The standards aren't what is blocking progress, simply applying configuration via various profiles is. If you have one base one in pom.xml, one additional one in profiles.xml and a third in settings.xml, hands down, ant handles this kind of thing in a way more elegant way.
Additionally, passing these kinds of profiles along via CruiseControl (distributed CC at that) is either undocumented or unsupported. So I guess I'd add little/poor support by other widely used tools (continuum is not a solution for us at this point). -----Original Message----- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 4:18 PM To: Maven Users List Subject: Re: [POLL] Why switch to Maven? On 8/29/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > I second the horrible online documentation and add to that slow, > unreliable support via the mailing list. > > I feel like m2 is great for small opensource projects with little to no > configurability. I find this reason interesting since large, complex projects are precicely what Maven was created to manage. Does this feeling stems from Maven's insistance on following a standard? What specific aspects of your project make it too complex to work in Maven? Can they be solved by breaking a large project into seperate smaller projects? -----Original Message----- > From: Heck, Joe [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 29, 2006 2:10 PM > To: Maven Users List > Subject: RE: [POLL] Why switch to Maven? > > This might be under your category of "lack of good documentation": > the tool really doesn't help you determine what's happening. > > The error messages are obscure, and there is now easy way to determine > what is even easily available from the command line. To learn anything > about maven, you need to be dedicated to really wanting to use it and be > willing to dive into online documentation. > > The "Better Builds with Maven" online book was a huge benefit - we are > making the switch for some projects, and we never would have been able > to enable that without the online book. > > -joe > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Eric Redmond > Sent: Tuesday, August 29, 2006 10:55 AM > To: Maven Users List > Subject: [POLL] Why switch to Maven? > > Hi all Maven users! > > I'm beginning a study to outline the real reasons that people have for > avoiding Maven. My questions to you all are: > What were your anxieties about using Maven? If you use Maven: what > helped > you make the decision? If you don't: why did you avoid it? > > Here are some that I have heard in the past: > > * Lack of good documentation. > * Community unwilling to help me with my problems. > * Not "industry supported" or "mainstream" enough. > * I don't like conforming to the Maven project layout. > * My project is too complex to switch. > * There are not enough plugins available. > * We already have a large investement in tool X. > * I have to build native/non-Java code. > > Any more reasons? Care to expand these ideas? > Thanks for your help! > ____ > Eric Redmond > http://codehaus.org/~eredmond > > --------------------------------------------------------------------- > 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] > > -- Eric Redmond http://codehaus.org/~eredmond --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
