JBoss 5 custom deployment folder is ignored

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.10 EE GA1, 6.2.X EE
• Fix Version/s: 6.2.X EE
• Component/s: Environments, Environments > App Servers
• Labels:
  • QA-NF
  • ee-ts
  • liferay-fixpack-portal-162-6210
• Branch Version/s:
  6.2.x
• Backported to Branch:
  Committed
• Story Points: 1.5
• Fix Priority: 3
• Application Servers:
  JBoss App Server 7.1, JBoss EAP 5.1, JBoss EAP 5.2
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal-ee/pull/18205

On 7.0.x/master there is no such wide range of supported JBoss app servers, therefore those are not affected, but the new method we added to ServerDetector as part of the fix will be committed to 70x and master also.

---

Reproduction steps:

1. Deploy Liferay 6.2.x (commit ef2ba02f325f688d96cb7c0715b9ba55674015a9) to JBoss EAP 5.2 (I had to use JBoss 5.1)
2. Add the below property to your portal-ext.properties

   auto.deploy.jboss.dest.dir[5]=${jboss.server.home.dir}/deploy

3. Start up the portal
4. Deploy a plugin

Experienced behavior: The war file was copied to the $JBoss_Home/webapps folder

Expected behavior: The war file should have been copied to the specified deploy folder