On Dec 17, 2008, at 3:54 AM, Martin Höller wrote:
And BTW: Maven's primary goal is to help building and packaging
software,
not starting the developed piece of software, so IMHO the exec-
plugin is
not a good example here.
Well I have to disagree with you there. Testing is also not about
building and packaging software, yet Maven provides lots of support
for testing because it's such an integral part of the development
process. Launching a desktop application that's being developed is
part of testing too.
Also, I don't want to maintain separate scripts in a separate language
just to launch an application. How would I make sure that the source
code has been compiled? How would I locate all the dependent JARs?
These problems are handled by the exec plugin, so I see no reason not
to use it just because profiles are "bad".
I simply want to keep everything contained within Maven, like I was
able to do with Ant. For example, in Ant I was able to define targets
like "run-test1" and "run-test2" that had dependencies on "compile"
and "jar". That way, whenever I ran either test, Ant would make sure
that the JAR was up to date with the latest code. I don't know of any
way to duplicate this functionality without using profiles.
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
