[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-329) jboss-as-5 plugin: reliance on hard-coded app server library paths

jboss-as-5 plugin: reliance on hard-coded app server library paths ------------------------------------------------------------------ Key: EMBJOPR-329 URL: https://jira.jboss.org/browse/EMBJOPR-329 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.3.3 Reporter: Thomas Hauser Assignee: Ian Springer Priority: Critical This is related to https://jira.jboss.org/browse/JBPAPP-4886 From JBPAPP-4886: If the JBoss library locations are altered and the JBoss variables for the libraries (jboss.lib.url,jboss.common.lib.url and jboss.server.lib.url) are made consistent with the library locations the JBoss Admin Console cannot be opened. Investigations shows This is because the ApplicationServerDiscoveryComponent class don't use JBoss variables and instead hard coded the path to jar files: See at the end of ApplicationServerDiscoveryComponent: CLIENT_JARS = Arrays.asList(new String[] { "client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar", "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-dependency.jar" }); AS6_CLIENT_JARS = new ArrayList(CLIENT_JARS); AS6_CLIENT_JARS.add("lib/jboss-classpool.jar"); AS6_CLIENT_JARS.add("lib/jboss-classpool-scoped.jar"); And it seems still the case in the trunk: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/j... Customers timescale is that they need a patch in October as their first production of a JBoss application is expected in November. Please note that this is a time sensitive issue! Thanks