Hi, I have this bug report in m2e-wtp[1], where calling IServer.publish() [2] causes some adapter(s) (GlassFish at least) to start stopped server instances. I must say I find that behavior questionable, but I can't control how 3rd party server adapters work. Anyways, is there a recommended way to tell the stopped IServer instance it *should* publish, in a way it -most likely- wouldn't start the server?
And if you ask why I force server publication in that resource listener, it's to support dynamic war overlay [3] (changes in overlay project are automatically published in main web app) So if you have any pointers, please let me know. Thanks, Fred. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413987 [2] https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp.overlay/src/org/eclipse/m2e/wtp/overlay/internal/servers/OverlayResourceChangeListener.java#L83 [3] http://maven.apache.org/plugins/maven-war-plugin/overlays.html -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
