As a Plugin Deployer I can redeploy blacklisted WAR files without restarting the JVM

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: 6.2.0 CE M4
• Fix Version/s: 6.2.0 CE M4
• Component/s: Tools, Tools > Plugins SDK > Web
• Labels:
  • QA-PORTAL
• Epic/Theme:
  • Platform
  • Quick_Win
• Similar Issues: Show 5 results ; ;

  LPS-16382	Ability to edit plugin blacklist
  LPS-14221	Ext Plugin Redeploy
  LPS-18171	Plugin should be blacklisted if the file cannot be read or write
  LPS-9618	Plugins need to be deployed twice after recompile / restart
  LPS-1753	Re-Deploy portlet war causes NPE

A plugin developer creates a WAR file which is invalid or can't be successfully deployed during portal's auto deploy process. When the plugin developer starts the process, portal unsuccessfully deploys the WAR file. To avoid repetitive deployment tries, the WAR file is put on a black list. The developer fix the deployment issue and try again to deploy the WAR file. Although the file is on the black list, portal can start again the auto deploy process with the new file, because the black list contains an identification of the previous version.

[David Truong]

What is the process to allow the war to be removed from the black list.

[Tomas Polesovsky]

Developer must redeploy the war or restart portal.