DEPLOY_TO_PREFIX broken

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.1.0 CE GA1, 6.1.10 EE GA1, 6.2.0 CE M2
• Fix Version/s: --Sprint 11/12, 6.2.0 CE M2
• Component/s: Administration, Administration > Server > Plugin Installer
• Labels:
  • QA-C
  • deployment
• Liferay Contributor's Agreement:
  Accept
• Similar Issues: Show 5 results ; ;

  LPS-13362	Chat-portlet is broken
  LPS-1657	WSRP Consumer : Resouce upload is broken
  LPS-28269	Dockbar is broken in Sybase
  LPS-36081	Dockbar broken on plugin themes
  LPS-9532	Asset publiser edit links in title list view are broken

I found that after switching from 6.0.6 to 6.1.0 ce i cannot use DEPLOY_TO__ prefix anymore to define a plugin's context root when deploying by copying a war into the deploy folder. This is related to Commit a697bb550826ea59070d71133c09a6f5a74940ec.

In BaseDeployer, line 775 sais:
if ((specifiedContext != null) && srcFile.getName().startsWith(DEPLOY_TO_PREFIX)) {

specifiedContext is not given in some cases, especially not when deploying plugins by copying them to the deploy folder. In that case, I think, the DEPLOY_TO_PREFIX should be evaluated which is somewhat the opposite what the current code does.

[Philipp Kunz]

i think this was just a kind of typo. See commit comment and LPS-26025.

[Michael Saechang]

Committed on:
Portal 6.2.x GIT ID: 96e02ca874297893537393f6395a6956de4f878f.