D
Dustin Grau
Guest
These are meant to address the speed at which development can occur with an ABL Web App project, primarily, but could also be applied to Data Object project that also utilize the Publish action for moving code to a Tomcat server. Currently there is a delay in testing code after a publish due to sessions being trimmed after each Publish event, even when such an action is not needed (read: only non-ABL files were changed). -Disable the automatic publish option for all Tomcat-based servers (current default is enabled) -Don't trim PAS/MSAS sessions on Publish if ONLY static files (non-ABL) are changed -If files in a project are modified via the filesystem, when changes are discovered by Eclipse, mark those files for inclusion/removal in next publish action Related: -Add context menu option to trim PAS/MSAS sessions (for on-demand use, outside of a publish)
Continue reading...
Continue reading...