Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
6.2.10 EE GA1, 6.2.X EE
-
6.2.x
-
Committed
-
1.5
-
3
-
JBoss App Server 7.1, JBoss EAP 5.1, JBoss EAP 5.2
Description
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:
- Deploy Liferay 6.2.x (commit ef2ba02f325f688d96cb7c0715b9ba55674015a9) to JBoss EAP 5.2 (I had to use JBoss 5.1)
- Add the below property to your portal-ext.properties
auto.deploy.jboss.dest.dir[5]=${jboss.server.home.dir}/deploy
- Start up the portal
- 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
Attachments
Issue Links
- is related to
-
LPE-15625 JBoss 5 custom deployment folder is ignored
-
- Closed
-