Hi all,
I'm an experienced Ant user but new to Maven, and I'm a little shocked
at how verbose Maven is, even compared to Ant, which is notorious for
its verbosity. For example, if I want to launch a Java application in
Ant, I do this:
target name=run
java classname=foo.Bar
Maven does make the development process simpler in many ways, but it's a
mistake to think that every possible activity in that process will be
simpler. Obviously, the power Maven brings in terms of dependency
handling, standardized lifecycles and lifecycle vocabulary, etc. will be
completely
BTW, unless I'm misataken, the following invocation should also work:
mvn exec:java
-j
Trevor Harmon wrote:
Hi all,
I'm an experienced Ant user but new to Maven, and I'm a little shocked
at how verbose Maven is, even compared to Ant, which is notorious for
its verbosity. For example, if I
On Aug 18, 2008, at 2:51 PM, John Casey wrote:
Maven does make the development process simpler in many ways, but
it's a mistake to think that every possible activity in that process
will be simpler. Obviously, the power Maven brings in terms of
dependency handling, standardized lifecycles
2008/8/19 Trevor Harmon [EMAIL PROTECTED]:
But isn't this a pretty common use case? I mean, launching a Java
application happens pretty often in most Java development life cycles. You
can only go so far with unit tests; eventually you need to run the thing and
see how it looks.
Not generally
