Bugzilla – Full Text Bug Listing
| Summary: | Move to using MX4J plugins from Orbit instead of a TPTP only copy | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Dave Smith <smith> |
| Component: | TPTP.monitoring | Assignee: | Kathy Chan <kathy> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | analexee, apnan, jcayne, sluiman |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | housecleaned460 closed460 | ||
|
Description
Dave Smith
This should be done in the next release if possible. moving to 4.5 Targetting to i4 Set to P1. Joel, Please following packages from Orbit into the TPTP build. MX4J net.sourceforge.mx4j 3.0.1 MX4J Remote net.sourceforge.mx4j.remote 3.0.1 After you are done, please reassing to mmings. Just as a tip, if you open these defects against Release Engineering > Build, they will automatically get assigned to Joel. This change should be done in i5 (as targetted by Matt), we don't want to destabilize the build. I am proposing to move this defect out of the 4.5 plan since there are no resources on the BTM side to address it. (In reply to comment #8) > I am proposing to move this defect out of the 4.5 plan since there are no > resources on the BTM side to address it. Does this involve a code change or a JRE dependancy problem? or is this just a one time migration test effort after improving the packaging as suggested? It is a general imperative across Eclipse to avoid redundancy, and this seems like a good one to clean up. Alex, are all 4 jars required to replace the 2 that we package ourselves? The 2 Mx4j jars are referenced in SetConfig.java, so a source change is only required if you need to use javax.management.jar and javax.management.remote.jar as well. I think so. If this defect could be defered to i6 then perhaps we could give it another try. There is no one available to do the changes now. Matt is not available, Richard and myself are fully booked with 4.4.1 and the remaining 4.5 i5. I think that postponing to i6 is not possible because of legal constraints. Joel, was this handled already? Are there other legal reqts over and above the two Orbit requests we submitted? I think you are referring to the Xerces bundles from Orbit. No legal approval was requested for the four MX4J bundles yet. The build updates are ready but pending plug-in changes required by the component owner prior to build change check-in. Re-assigning to component owner. Moving to future, this change cannot be contained in 4.5. Reassigning to new component lead. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since the originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |