- This topic has 5 replies, 2 voices, and was last updated 17 years ago by
.
-
Posts
-
Thanks for helping Stephen.
Where do I put the mvn war:inplace ? I mean I know I can run it as a command line, but what I’m trying to get to is the ability to just deploy from within myeclipse to the internal myeclipse for development but still have my maven build set up to build in target/ to use for our typical deployment.
Is there a way to have both?
Also, I am using the m2eclipse plugin (I don’t think it’s been buggy for me although it is QUITE slow building the workspace due to all the projects and there dependencies). I used mvn eclipse:eclipse initially to add the maven stuff to my eclipse classpath but I guess I hadn’t thought of using it after each pom change (is that what you do instead of m2eclipse?).
Thanks for clarifying. I hope I’m not being too stupid. 😉
If you use the m2eclipse plugin (apparently, the dev version avoids some serious bugs which caused me to give up on the dang thing) then you can attach a maven builder to your project.
Personally, I’ve just been using mvn jetty:run to start a web server – it really rocks not having a deploy step at all. And you can easily debug from eclipse – http://docs.codehaus.org/display/JETTY/Debugging+with+the+Maven+Jetty+Plugin+inside+EclipseOh yeah – I didn’t answer all of your questions. Yes, I’m doing eclipse:eclipse after each pom dependency change.
Using the m2eclipse plugin and mvn eclipse:eclipse are mutually exclusive. The both accomplish the same thing, and last one wins. 🙂
My biggest gripe with the m2eclipse plugin is that pom changes would frequently lead to all dependencies being removed from the project, and getting them back was a pain in the butt. Like I say, this is apparently fixed, but now I have a workflow going with mvn eclipse:eclipse and mvn jetty:run, and I don’t really see a need to go back.
