Community
Participate
Working Groups
If I have a server having multiple applications published to it and I enable automatic publish, then any change to any project will result in republishing all modules. This is not necessary and slow. Could you track the changes and evaluate that which modules are needed to be republished?
The server framework provides delta information to the server adapter down to the file level, so only the changed files need to be published. Tomcat works this way, so the publishing is incremental and fast. Which adapter are you using that doesn't support this, since this appears to be a server adapter specific bug?
I used Glassfish plugin for Glassfish 2.1. Plugin version 1.0.24.
Ok, then please open a bug directly against the Glassfish server adapter. It may turn out that they in turn open a bug against the generic server framework in WTP or some such, but since this is working in most other server adapters it is not a general problem and they will need to do the initial investigation.
I reported the bug to glassfish plugin developers, and as far as I understand the comment (https://glassfishplugins.dev.java.net/issues/show_bug.cgi?id=167) it is because of the generic server adapter. So the bug is in the eclipse. Am I right?
Gorkem - Does the generic server framework make this restriction, or is it missing implementation on the glassfish side?
This is probably fixed when the bug# 148269 was fixed before this fix the publishers were determining the delta incorrectly. I will confirm that it is actually fixed and resolve it.
There was still some issue. I have released a fix.
New Gerrit change created: https://git.eclipse.org/r/108786