[
https://jira.jboss.org/jira/browse/EMBJOPR-119?page=com.atlassian.jira.pl...
]
Charles Crouch commented on EMBJOPR-119:
----------------------------------------
So the /server/${config}/tmp/embjopr value coming from the console is fine. The deployment
manager wasnt putting the file in the right place because we were telling it to not copy
the deployment to /deploy, telling it to do the copy and everything works great.
Ian fixed this in JOPR r323.
Applications are deployed to server/default/tmp/embjopr directory
instead of expected server/default/deploy
-----------------------------------------------------------------------------------------------------------
Key: EMBJOPR-119
URL:
https://jira.jboss.org/jira/browse/EMBJOPR-119
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Environment: JBoss AS r 86263, EMBJOPR r 253
Reporter: Shelly McGowan
Assignee: Charles Crouch
Fix For: 1.2
Applications are typically deployed to JBoss AS in the server/${config}/deploy directory.
Using the versions of JBossAS/EMBJOPR shown in the Environment field, the applications
deployed via EMBJOPR get deployed to:
$JBOSS_HOME/server/${config}/tmp/embjopr directory. It is not clear why this change
occurred but is affecting tests verifying successful deployment of applications including
the view from the JMX console.
Tests failuring due to above:
testBasicEarDeployment
testEarSummaryTab
testDeployUnpackedEar
testWarSummaryTab
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira