Hi Josh,
I'm starting migrating some projects to maven and personally I think
that maven is the way to go because of three things (the 3 selling
arguments I've used at work ;-) :
1. we can locate a project or a project module (an artifact in maven
terminology) in space and time, i.e. we spec
Nah, we can drop "ideology" in the bitbucket. It's a matter of using
the tool that best does the job.
Maven is really good at representing the structure of large, complex
projects simply, and pretty good at organizing the large-scale flow of
operations involved in realizing them. Ant is rather g
On Fri, Aug 22, 2008 at 4:07 AM, Josh Long <[EMAIL PROTECTED]> wrote:
> How do I make this case in the face of so hostile a mentality? Have you
> ever
> had to make the case? Any insight on how to move forward would be
> appreciated.
>
Well: you believe it'll solve some problems for you. Look at
Hi,
There is maven-ant-plugin which allows you to do everything which you
can do in ant.
However, you shouldn't use it too much because it is inconsistent with
maven ideology :).
Cheers,
Piotr Oktaba
On Fri, 2008-08-22 at 14:25 +0200, Paulo Pinto wrote:
> Hi,
>
> having survived an Ant->Maven
Hi,
having survived an Ant->Maven migration process, I would advise you to
really be sure that Maven supports out of the box all the things you are
already
doing with Ant.
Otherwise you might get some nasty surprises, that would fragile your
position.
Maven is a nice tool, but if it does not sup
Hi everyone,
I'm trying to make a case for Maven and I'm going to need to provide a
better reason than "it's better than a kick in the face!" to managment. I'm
at a bank, so everything is subject to heavy scrutiny. Essentially, our
project hardly compiles and is so untestable that upon check out n
