You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by James Strachan <ja...@yahoo.co.uk> on 2003/03/06 14:15:59 UTC

Re: [eclipse plugin] setting the output directory

I've patched the eclipse plugin so that the output directory of the
generated eclipse project can be configured. e.g. I now set the following
variable in my ~/build.properties file

    maven.eclipse.output.dir = bin

which then uses a local bin directory, to keep Eclipse and Maven generated
files separate. I've left the default behaviour the same, so this is an
optional feature for those that need it.

James
-------
http://radio.weblogs.com/0112098/
----- Original Message -----
From: "James Strachan" <ja...@yahoo.co.uk>
To: "Turbine Maven Developers List" <tu...@jakarta.apache.org>
Sent: Friday, February 28, 2003 1:46 PM
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" <ml...@mvdb.net>
> To: "Turbine Maven Developers List" <tu...@jakarta.apache.org>
> 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-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> turbine-maven-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
turbine-maven-dev-help@jakarta.apache.org
> >
>
> __________________________________________________
> 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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
>

__________________________________________________
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