Quick question - I'm still rather new to Maven, but am an eclipse user and feel I can provide some input here.
I don't see the problem with the target/classes as a default directory. However, I understand if you would like to separate the build from eclipse auto-compile. +1 to allowing configuration. In my opinion providing configuration hooks to modify behavior is a good thing. One thing thought that I have a question on, is the scenario with a reactor and multiple "sub-projects. Newer version of Eclipse allow for multiple output directories (each source directory can have its own output directory). This is extremely useful, and it fits nicely with maven's target/classes. My only concern about the additional configuration is that it takes this into account (I'm not sure if the eclipse-plugin handles this yet or not, but it should if it doesn't) - Mike > -----Original Message----- > From: James Strachan [mailto:[EMAIL PROTECTED] > Sent: Friday, February 28, 2003 8:46 AM > To: Turbine Maven Developers List > Subject: Re: [eclipse plugin] setting the output directory > > This is a great idea. Lets leave the default to be target/classes and let > folks like me change the detault. > > James > ------- > http://radio.weblogs.com/0112098/ > ----- Original Message ----- > From: "Martin van den Bemt" <[EMAIL PROTECTED]> > To: "Turbine Maven Developers List" <[EMAIL PROTECTED]> > Sent: Wednesday, February 26, 2003 5:35 PM > Subject: Re: [eclipse plugin] setting the output directory > > > > I always have them the same (target/classes). > > If you can make it settable (eg in project.properties) and use the one > > you prefer as default, I don't mind ;) > > > > Mvgr, > > Martin > > > > On Wed, 2003-02-26 at 17:50, James Strachan wrote: > > > The eclipse plugin currently sets the target directory for eclipse's > build > > > to target/classes. I just wanted to get feedback from other Eclipse > users > > > about this. I'd prefer Eclipse to have its own output directory; > preferably > > > in something different like bin. > > > > > > Basically I like to do lots of > > > > > > maven clean test > > > > > > from time to time. Any 'maven clean' will force a rebuild to be > required > in > > > eclipse. So I don't see much value in Eclipse's binary compilation of > the > > > code to be in the same place as where Maven builds. I'd prefer to keep > them > > > separate. > > > > > > IDEs are notoriously subjective - would this approach suite others use > of > > > Eclipse? If so I'll go ahead and patch the eclipse plugin to not use > the > > > same location as Maven for its build files. > > > > > > James > > > ------- > > > http://radio.weblogs.com/0112098/ > > > > > > __________________________________________________ > > > Do You Yahoo!? > > > Everything you'll ever need on one web page > > > from News and Sport to Email and Music Charts > > > http://uk.my.yahoo.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: turbine-maven-dev- > [EMAIL PROTECTED] > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: turbine-maven-dev- > [EMAIL PROTECTED] > > > > __________________________________________________ > Do You Yahoo!? > Everything you'll ever need on one web page > from News and Sport to Email and Music Charts > http://uk.my.yahoo.com > > --------------------------------------------------------------------- > 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]
