eclipse - Can a multi-module m2eclipse/WTP project get utility modules deployed into WEB-INF/classes? -
We currently use MyEclipse with the built-in Maven4MyEclipse integration and its built-in J2EE server support, but want to convert it to Regularly being able to use their 64-bit installation on Eclipse (especially in Holeos) windows (MyEclipse does not yet support Windows 64-bit.)
So far I have got a work prototype of the eclipse of the Halius, Using lipus, our large web application is being installed on a tomcat. Deployment is a bit processor intensive, but it works and the app starts.
What is quite different here is how dependent projects are deployed. In our Myclipus environment, all dependent projects were exploded in the Web-INF / Works folder, and when the server was running, the change in the Java class in the IDE would only copy the affected files (files) to the web-NF / classes of the server and Hot and swap the class in JVM ... Boom - Live changes in server great for debugging.
In my Holeus conversion, however, all dependent projects are put in Jared and WEB-INF / lib. This is actually the benefit of seeing how our image of actual Maven-produced production looks, but the development environment is seriously deprived of this, in which the hot-swapping capacity is completely lost. Here, if I change the Java class in a dependent project, then M2 will re-package the Eclipse Jar, see that the deployed web application is out of synchronization, and republish the entire application. Not only is this a problem that the entire web application is for the cycle (some things clearly do not have its size and the massive initialization time well), it is also a deep delusion in eclipse, republish it (our It takes a minute or two for the application.)
So my question is: to change the files deployed without having to swap the jvm that runs inside the dependent projects A way should be republished worse punishment? I am assuming that this means that those class files have to be deployed in the web-INF / classes, but to ensure that it is possible (A) is possible or (B) in reality as part of this solution Is necessary in
What are the others to solve this? Is it worth solving?
Thanks in advance!
I think you are looking for the solution described in:
If you enable "service modules without publishing", then a special jar is added to the Tomcat server that allows tomac support in WTP to control "classpath" besides the "web application" Utility projects are not collected in the jar. Instead, the utility The Java output folder (web) of projects is included in the "classpath" of the web application, which directly service class files. If you disable auto-loading for reference, and run in debug mode, then You can hot-code-replace the changes made to the classes so that the references do not reload. I believe what this will work for you.
To do this For:
Comments
Post a Comment