Well this may be possible in the future with the eclipse maven plugin. Anyway, packaging a web app is not something you do regularly. I think you are being a bit idealistic here. It's not optimal but in the mean time it works correctly. Never seen any performance issue and I don't agree with what you have defined as problems.
On 6/7/06, kvpetrov <[EMAIL PROTECTED]> wrote:
I don't think turning off autobuild feature of Eclipse is a good idea. I like Eclipse compiling my java classes on fly. There two problems with the current behavior: 1) I don't want to waste my CPU on copying files back and forward taking into account that the resulting application is not usable anyway because Eclipse just can't build it right. Instead of trying to build it on its own when you publish the app Eclipse should call appropriate maven goals when a resource is touched. Basically, this is more of a problem for the Eclipse maven plugin that can't get triggered when a particular resource is changed within Eclipse project. 2) Because the resulted app is invalid I can not associate the project with a server and start it within Eclipse. Of course, I found ways around this problem but I still think that what WTP+Maven do now is completely wrong. Eclipse can still compile java classes on fly it does not prevent maven from correctly assembling the app and providing it to WTP for deployment. -- View this message in context: http://www.nabble.com/eclipse%2C-wtp%2C-maven-and-web-apps-t1725424.html#a4763221 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- 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]
