[
https://issues.jboss.org/browse/JBTM-893?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-893:
-------------------------------
Description:
We have a dependency in the arjuna module on jconsole.jar which is potentially not shipped
none-Sun JDK's for instance so our pom refers to JAVA_HOME/lib/jconsole.jar.
This needs reviewing, we could add a profile that only includes the dependency on a build
when the file exists and in other profiles does not build the classes that require this
Jar, but if the code is critical we need to think about a rewrite to not depend on the
(presumably) proprietary Jar.
was:
We have a dependency in the arjuna module on jconsole.jar which is not shipped in openjdk
for instance so our pom refers to JAVA_HOME/lib/jconsole.jar.
This needs reviewing, we could add a profile that only includes the dependency on a build
when the file exists and in other profiles does not build the classes that require this
Jar, but if the code is critical we need to think about a rewrite to not depend on the
(presumably) proprietary Jar.
Build is dependent upon Sun's JDK
---------------------------------
Key: JBTM-893
URL:
https://issues.jboss.org/browse/JBTM-893
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Tom Jenkinson
Assignee: Michael Musgrove
Fix For: 5.0.0.M2
We have a dependency in the arjuna module on jconsole.jar which is potentially not
shipped none-Sun JDK's for instance so our pom refers to JAVA_HOME/lib/jconsole.jar.
This needs reviewing, we could add a profile that only includes the dependency on a build
when the file exists and in other profiles does not build the classes that require this
Jar, but if the code is critical we need to think about a rewrite to not depend on the
(presumably) proprietary Jar.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira