[
https://jira.jboss.org/jira/browse/JOPR-35?page=com.atlassian.jira.plugin...
]
John Mazzitelli resolved JOPR-35.
---------------------------------
Fix Version/s: 2.2
Resolution: Done
Assignee: John Mazzitelli
the plugin needs to look for the undeployed installer too (because we now uninstall the
installer after we start for the first time). So, if we see "rhq-installer.war"
OR "rhq-installer.war.rej" in the deploy directory, we assume its the RHQ
Server.
After upgrading to 2.1.2SP1, RHQ server appears as generic JBAS
server
----------------------------------------------------------------------
Key: JOPR-35
URL:
https://jira.jboss.org/jira/browse/JOPR-35
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Environment: postgres, linux
Reporter: Jeff Weiss
Assignee: John Mazzitelli
Fix For: 2.2
Upgraded from 2.1.2GA to 2.1.2SP1. Afterwards, I had 2 JBAS instances in inventory. One
was "JBoss Application Server" and the other "JBoss Application Server
hosting the RHQ Server".
The problem is that both of them should be detected as RHQ servers:
<mazz> so the install paths are different, hence differrent resource keys, hence
different resources
why its not labeled as RHQ Server is worrisome
CRAP!
File rhqInstallerWar = new File(deployDir, "rhq-installer.war");
boolean isRhqServer = rhqInstallerWar.exists();
dammit :) have to change the jboss-as plugin
...
<mazz> svn rev 119 fixed it
--
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