Thanks you for the advices.
By quickly scanning thru Eclipse and Maven's eclipse plugin.
I do understand that Maven can generate Eclipse projects. What about
eclipse plugin , can maven generate plugin related files??.
Sorry at this moment, I dont know eclipse too much to figure it out
my self.
-Dan
On Thu, 23 Dec 2004 10:21:43 +0100, Laurent PETIT <[EMAIL PROTECTED]> wrote:
> With maven, it seems to me easier to manage platform dependent code, such as
> replacing "on the fly" tokens for your platform in some files, or entire
> resources directories.
>
> Example : My maven directory layout includes src/conf/all, src/conf/dev,
> src/conf/preprod, src/conf/prod, src/conf/test as resources directories.
>
> In my project.xml, I declare as resource directories :
> ${basedir}/src/conf/all, and ${basedir}/src/conf/${currentResourcesChoice}
> pointing to the good directory.
>
> In my build.xml, I set the current target platform for compilation :
> currentResourcesChoice=dev (for example).
>
> Another interesting thing is for unit testing : you generally need to
> include different resources for the unit tests (ie from the src/conf/test
> directory).
> But in Eclipse you can not easily exclude the src/conf/dev resource
> directory, replacing it with src/conf/test.
> You have to go to the project properties and change the java source
> directories .... not very pratical !
>
> With maven, you just open a "maven console" in a dos shell, type in
> test:test once for the entire day, and "alt+tab" + "Enter" the other times,
> not so bad for a more supple project management process.
>
> My 0.02 euros,
>
> --
> Laurent
>
> -----Message d'origine-----
> De : Milos Kleint [mailto:[EMAIL PROTECTED]
> Envoy� : jeudi 23 d�cembre 2004 10:12
> � : Maven Users List; dan tran
> Objet : Re: Maven vs Eclipse build
>
>
> advantages, in no particular order
> 1. generating the web site with all the reports and docs
> 2. automated builds - nightly, after every commit (not sure if that
> can be achieved with eclipse build but assume not)
> 3. no eclipse lock-in, can use other IDEs as well (netbeans,
> jbuilder)..maybe not relevant to you
> 4. variety of maven plugins for different technologies, no need to
> install the relevant plugin to eclipse in order to build. (not sure
> about this one - I always base my builds on ant or maven)
>
> Regards
>
> Milos Kleint
>
> On Wed, 22 Dec 2004 19:33:30 -0800, dan tran <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I am trying to convince our team to use maven for a new application
> > using eclipse.
> >
> > Can someone give me some advices what advantages and disadvantages
> > maven together with maven-eclipse-plugin and mevenide and
> > maven-eclipse-plugin-plugin has over the eclipse build.
> >
> > advices are greatly appreciated.
> >
> > -Dan
> >
> > ---------------------------------------------------------------------
> > 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]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
