[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560394#action_12560394
]
Rick Hillegas commented on DERBY-1387:
--------------------------------------
Hi John,
After applying the patch and running "ant all", I see the following sequence of
ant targets being invoked:
engine
...
compile_iapi_error_jsr169:
compile_reference:
The error is coming from compile_reference which is a target in
trunk/java/engine/org/apache/derby/iapi/reference/build.xml. Looking at the
<javac> task in that target, I see that the classpath is set to be just
${compile.classpath}, which is the set of jars in the JDK, in this case JDK1.4.
So none of the jars in tools/java are being pulled in.
If you want to just hack this together, then you can do the following:
1) in tools/ant/extrapath.properties, add a new variable which points at the
jmxri.jar file you have added.
2) wire that variable into the classpath in the <javac> task in
compile_reference.
However, trying to force the JMX support to compile under jdk1.4 has some
pitfalls to it. It either involves:
a) asking people to download another (optional) jar file--this at a time when
we are trying to simplify the build and eliminate the optional jar files
b) find or construct a freeware version of the JMX jar file (perhaps by mining
the Harmony project?)
I would recommend compiling the JMX support under Java 5 instead, where you
will be guaranteed to have the JMX libraries. You can look at
trunk/java/testing/org/apache/derby/build.xml for an example of how to do this.
I think it would be ok to say that the JMX support has only been tested under
Java 5 and that we do not recommend its use on previous VMs--if necessary, you
could put in some code to prevent the JMX support from running on old VMs.
> Add JMX extensions to Derby
> ---------------------------
>
> Key: DERBY-1387
> URL: https://issues.apache.org/jira/browse/DERBY-1387
> Project: Derby
> Issue Type: New Feature
> Components: Services
> Reporter: Sanket Sharma
> Assignee: John H. Embretsen
> Attachments: DERBY-1387-1.diff, DERBY-1387-1.stat, DERBY-1387-2.diff,
> DERBY-1387-2.stat, DERBY-1387-3.diff, DERBY-1387-3.stat, DERBY-1387-4.diff,
> DERBY-1387-4.stat, DERBY-1387-5.diff, DERBY-1387-5.stat, DERBY-1387-6.zip,
> DERBY-1387-7.zip, DERBY-1387-8.zip, derbyjmx.patch, jmx.diff, jmx.stat,
> jmxFuncspec.html, Requirements for JMX Updated.html, Requirements for
> JMX.html, Requirements for JMX.zip
>
>
> This is a draft requirement specification for adding monitoring and
> management extensions to Apache Derby using JMX. The requirements document
> has been uploaded on JIRA as well as the Derby Wiki page at
> http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX
> Developers and Users are requested to please look at the document (feature
> list in particular) and add their own rating to features by adding a coloumn
> to the table.
> Comments are welcome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
