Community
Participate
Working Groups
The usecase here is a server which has no functional start / stop, but rather only implements these things out of necessity to fit the workflow of wtp. Servers only automatically publish if the server is "started". Since this example server has no need to "start", users never get the automatic / incremental deployment requests from the auto-deployer. So, I've implemented a rudimentary launch configuration which does nothing other than automatically set the server to started, and a stop function which, again, simply sets the server's state to stopped. Unfortunately, in the server editor there's this nice hyperlink to open the launch configuration. In this situation, obviously, there is no *real* launch configuration, and clearly no need for any tab group that looks like one. In fact, the user should not even be able to open the launch configuration. Is there any way to add some API, either a launch configuration attribute or an extension point or anything, that would just disable / hide the hyperlink?
If the specific server type does not even has start or stop function, you may not need to create a launch configuration on the server at all. Have you tried remove the launch configuration and set the correct server state on the server when your server is being initialized? Then, by the time that you auto publish is being called, your server is already "started" and then you don't need to the launch configuration.
