In TPTP 4.0, features and plug-ins were merged to reduce plug-in overhead. When building on top of TPTP 4.0, you will see unresolved features and plug-ins and compile errors caused by these unresolved items in the class path. Instead of investigating each problem individually, start with the mechanical migration steps because these changes will resolve the majority of the problems. If you still see problems after the mechanical change, then read through the Changes in TPTP behavior subtopic to see if that clarifies the situation.
1.0 Mechanical migration steps2.0 Changes in TPTP behavior
1.1 Update the names of the plug-ins in the plug-in manifest
Because several plug-ins were deleted or merged with other plug-ins, you need to migrate your code over to the new plug-ins. Update your plug-in manifest's dependencies by removing the plug-in in the Delete column and adding the plug-in in the corresponding Add column in its place. After the plug-ins have been updated, rebuild your workspace.
| Delete | Add | |
|---|---|---|
| 1. | org.eclipse.hyades.execution.core | org.eclipse.hyades.execution |
| 2. | org.eclipse.hyades.execution.harness | org.eclipse.hyades.test.core |
| 3. | org.eclipse.hyades.execution.local | org.eclipse.hyades.execution |
| 4. | org.eclipse.hyades.execution.remote | org.eclipse.hyades.execution |
| 5. | org.eclipse.hyades.execution.recorder | The plug-in to replace it with depends on the features that you need:
|
| 6. | org.eclipse.hyades.execution.recorder.http | The plug-in to replace it with depends on the features that you need:
|
| 7. | org.eclipse.hyades.execution.testgen | |
| 8. | org.eclipse.hyades.execution.testgen.http | org.eclipse.hyades.test.tools.core |
| 9. | org.eclipse.hyades.log.ui | The plug-in to replace it with depends on the features that you need:
|
| 10. | org.eclipse.hyades.logc | org.eclipse.hyades.trace.ui |
| 11. | org.eclipse.hyades.logging.adapter.config | org.eclipse.hyades.logging.parsers |
| 12. | org.eclipse.hyades.sd.logc | org.eclipse.tptp.platform.log.views |
| 13. | org.eclipse.hyades.models.* | org.eclipse.tptp.platform.models |
| 14. | org.eclipse.hyades.security | org.eclipse.hyades.ui |
| 15. | org.eclipse.hyades.test.datapool | org.eclipse.tptp.platform.models |
| 16. | org.eclipse.hyades.test.http | The plug-in to replace it with depends on the features that you need:
|
| 17. | org.eclipse.hyades.test.java | The plug-in to replace it with depends on the features that you need:
|
| 18. | org.eclipse.hyades.test.manual | The plug-in to replace it with depends on the features that you need:
|
| 19. | org.eclipse.hyades.test.ui | |
| 20. | org.eclipse.hyades.test.ui.datapool | org.eclipse.hyades.test.ui |
| 21. | org.eclipse.hyades.uml2sd.trace | org.eclipse.hyades.trace.views |
| 22. | org.eclipse.hyades.uml2sd.ui | org.eclipse.hyades.ui |
| 23. | org.eclipse.hyades.datacollection |
org.eclipse.tptp.platform.agentcontroller Client side agent code remains in the org.eclipse.hyades.perfmon plug-in. The package structure remains the same. Native agent code has been moved into the org.eclipse.tptp.platform.agentcontroller plug-in, under the src-native source folder. This contains the native code for the Windows System agent and Linux System agent under the same directory structure as previously used. |
| 24. | org.eclipse.hyades.datacollection |
org.eclipse.hyades.perfmon.agents Java agent code now resides in the org.eclipse.hyades.perfmon.agents plug-in in the Monitoring project under the src-jmxagent folder. The package structure has not changed. |
| 25. | org.eclipse.hyades.logging.java | org.eclipse.hyades.logging.core |
| 26. | org.eclipse.hyades.logging.commons | org.eclipse.hyades.logging.core |
| 27. | org.eclipse.hyades.logging.log4j | org.eclipse.hyades.logging.core |
1.2 Update the names of the extension points in the plug-in manifest
When plug-ins were combined, their contained extension points names' had to be renamed. Update your plug-in manifest to change the name of any extension's extension point from the value in the Delete column to the value in the Add column. After the plug-ins have been updated, rebuild your workspace.
| Delete | Add | |
|---|---|---|
| 1. | org.eclipse.hyades.security.JSSESecurityProviders | org.eclipse.hyades.ui.JSSESecurityProviders |
| 2. | org.eclipse.hyades.uml2sd.ui.uml2SDLoader | org.eclipse.hyades.ui.uml2SDLoader |
| 3. | org.eclipse.hyades.logc.logInteractionView | org.eclipse.hyades.trace.ui.logInteractionView |
| 4. | org.eclipse.hyades.logc.logParser | org.eclipse.hyades.logging.parsers.logParser |
| 5. | org.eclipse.hyades.logging.adapter.config.staticParser | org.eclipse.hyades.logging.parsers.staticParser |
| 6. | org.eclipse.hyades.execution.harness.harness - all extension points | org.eclipse.hyades.test.core |
| 7. | org.eclipse.hyades.RecorderApplication | org.eclipse.hyades.test.core.RecorderApplication |
| 8. | org.eclipse.hyades.TestGenerator | org.eclipse.hyades.test.core.TestGenerator |
| 9. | org.eclipse.hyades.test.ui.deploymentProvider.exsd | org.eclipse.hyades.test.core.launchconfigDeploymentProvider.exsd |
| 10. | org.eclipse.hyades.test.ui.executionHistoryDefaults.exsd | org.eclipse.hyades.test.core.launchconfigExecutionHistoryDefaults.exsd |
| 11. | org.eclipse.hyades.test.ui.executionHistoryDefaults2.exsd | org.eclipse.hyades.test.core.executionHistoryDefaults2.exsd |
| 12. | org.eclipse.hyades.test.ui. | org.eclipse.hyades.test.core.launchconfigExecutionHistoryLocationFilter.exsd |
| 13. | org.eclipse.hyades.test.ui.launchableType.exsd | org.eclipse.hyades.test.core.launchconfigLaunchableType.exsd |
| 14. | org.eclipse.hyades.test.ui.runHandler.exsd | org.eclipse.hyades.test.core.launchconfigRunHandler.exsd |
| 15. | org.eclipse.hyades.test.ui.launchConfigValidator.exsd | org.eclipse.hyades.test.core.launchConfigValidator.exsd |
1.3 Update the plug-ins in the plug-in manifest for packages that moved to a different plug-in
Some packages were moved into a different plug-in. After you have completed steps 1.1 and 1.2 above, for any packages in the Packages column, remove the plug-in in the Delete column and replace it with the plug-in in the Add column.
| Package | Delete Plug-in | Add Plug-in | |
|---|---|---|---|
| 1. | All packages in the org.eclipse.hyades.sd.logc plug-in | org.eclipse.hyades.sd.logc | org.eclipse.tptp.platform.log.views |
| 2. | All packages in the org.eclipse.hyades.uml2sd.trace plug-in | org.eclipse.hyades.uml2sd.trace | org.eclipse.hyades.trace.views |
| 3. | All packages in the org.eclipse.hyades.logging.adapter.config | org.eclipse.hyades.logging.adapter.config | org.eclipse.hyades.logging.parsers |
| 4. | org.eclipse.hyades.log.ui (Log Import code) | org.eclipse.hyades.log.ui | org.eclipse.tptp.monitoring.logui |
| 5. | org.eclipse.hyades.log.ui (Log Navigator code, including view actions: new correlation and new symptom database, save/delete) | org.eclipse.hyades.log.ui | org.eclipse.hyades.trace.ui |
| 6. | org.eclipse.hyades.ui.widgets | org.eclipse.hyades.statistical.ui | The views currently reside in the org.eclipse.hyades.statistical.ui plug-in in the platform component. The ZoomSlider and Grapher widgets have been moved and made publically available in the org.eclipse.hyades.ui plug-in in the org.eclipse.hyades.ui.widgets package. |
1.4 Update the names of packages to their new names
Some packages were refactored. After you have completed steps 1.1, 1.2, and 1.3 above, open the Java Perspective (Window > Open Perspective > Java) and then click Organize Imports (Source > Organize Imports). Any affected packages will be renamed.
| Delete Package | Add Package | Notes | |
|---|---|---|---|
| 1. | org.eclipse.hyades.execution.core | org.eclipse.hyades.execution | |
| 2. | org.eclipse.hyades.ui (Log import code) | org.eclipse.tptp.monitoring.logui | The code was internal in TPTP 3.3 and remains internal in TPTP 4.0. |
| 3. | org.eclipse.hyades.ui (Log view code) | org.eclipse.tptp.platform.log.views | |
| 4. | org.eclipse.hyades.statistical.ui.views | org.eclipse.hyades.statistical.ui.internal.views | The analysis views (Statistical Graph View, Agent Control View and the Graph Summaries View) all reside in the org.eclipse.hyades.statistical.ui.internal.views package. |
1.5 Replace references to the deleted classes
Update your plug-ins and features to reflect the changes to some deprecated classes, methods, and properties, which were removed as explained in the following document:
Deprecated Resources Removed in TPTP v4.0.0
1.6 Replace references to the deleted extension points
Some extension points were renamed and you need to update your extension point as explained in the table below.
| Deprecated | New | |
|---|---|---|
| 1. | org.eclipse.hyades.ui.reportExtensions.reportExtensions | org.eclipse.hyades.ui.reportGenerators |
| 2. | staticParser | org.eclipse.hyades.logging.parsers.staticParser |
The statistical analysis editor is not longer extensible through the StatConModule extension point. This extension point has been removed completely but this functionality is now solely contained through the use of the Launch Configurations. In order to implement a custom agent, the user will have to implement a custom Launch Configuration. This is now consistent with the standard TPTP method for invoking agent processes.
1.7 Optionally migrate existing parsers to the TPTP 4.0 Agent Controller
If existing parsers will be used for remote import with a 4.0 Agent Controller, then parser wrapper classes that extend the deprecated class org.eclipse.hyades.logging.adapter.config.StaticParserWrapper can be changed to extend the new class org.eclipse.hyades.logging.parsers.importer.ParserWrapper. Note: if existing parsers will also be used for remote import with a pre-4.0 Agent Controller then do not perform this migration.
In addition, the org.eclipse.hyades.logging.adapter.config packages are preserved but the classes are deprecated as follows:
- org.eclipse.hyades.logging.adapter.config.StaticParserWrapper replaced by org.eclipse.hyades.logging.parsers.importer.ParserWrapper
- org.eclipse.hyades.logging.adapter.config.sensors.StaticParserSensor replaced by org.eclipse.hyades.logging.parsers.adapter.sensors.StaticParserSensor
- org.eclipse.hyades.logging.adapter.config.outputters.StaticParserOutputter replaced by org.eclipse.hyades.logging.parsers.adapter.outputters.LogImportOutputter
1.8 Optionally migrate existing static parsers to the TPTP 4.0 Agent Controller
If existing parsers will be used for remote import with a 4.0 Agent Controller, then adapter configuration files can be changed to replace the deprecated StaticParserSensor and StaticParserOutputter classes with the new classes org.eclipse.hyades.logging.parsers.adapter.sensors.StaticParserSensor and org.eclipse.hyades.logging.parsers.adapter.outputters.LogImportOutputter. Note: if existing parsers will also be used for remote import with a pre-4.0 Agent Controller then do not perform this migration.
1.9 Optionally migrate existing rules parsers to the TPTP 4.0 Agent Controller
If existing parsers will be used for remote import with a 4.0 Agent Controller, then adapter configuration files can be changed to replace the deprecated StaticParserOutputter class with the new class org.eclipse.hyades.logging.parsers.adapter.outputters.LogImportOutputter. Note: if existing parsers will also be used for remote import with a pre-4.0 Agent Controller then do not perform this migration.
1.10 Optionally migrate existing code from deprecated code
If you wish to, migrate existing code from deprecated by following the instructions in the How column. You do not need to perform this migration in TPTP 4.0.
| Deprecated | New | How | |
|---|---|---|---|
| 1. | org.eclipse.hyades.logging.parsers.IWidgetListener | org.eclipse.hyades.logging.parsers.importer.IWidgetListener |
You can optionally change any Log Import wizard widget listener classes from implementing the deprecated interface to the new interface. Replace the "import org.eclipse.hyades.logging.parsers" with "import org.eclipse.hyades.logging.parsers.importer.IWidgetListener". You can replace the packname name either manually or open the Java Perspective (Window > Open Perspective > Java) and then click Organize Imports (Source > Organize Imports). Any affected packages will be renamed. |
1.11 Convert stand-alone class path to reflect moved content or JARs
If you depend on TPTP JARs in a stand-alone environment, then you need to manually modify your class path to reflect the following additions and renames.
| 1.11.1 | The runner library (java.runner.jar) of plug-in org.eclipse.hyades.test.java has been moved to org.eclipse.hyades.test.tools.core. Update your class path from org.eclipse.hyades.test.java_version\java.runner.jar to org.eclipse.hyades.test.tools.core_4.0.0\java.runner.jar. | ||
| 1.11.2 | Common Runner (common.runner.jar) of plug-in org.eclipse.hyades.test.common has been moved to org.eclipse.hyades.test.tools.core. Update your class path from org.eclipse.hyades.test.common_version\common.runner.jar to org.eclipse.hyades.test.tools.core_4.0.0\common.runner.jar. | ||
| 1.11.3 | org.eclipse.hyades.trace.views contains the trace statistic table views and graphical views, as it did before in earlier versions. Now, in addition, it contains the profiling perspective, profiling views, and trace interaction views. If your application needs to import the profiling perspective, profiling views, or trace interaction views, then update your class path to point to the JARs in this plug-in. | ||
| 1.11.4 | All static parser related classes are included in hparse.jar. | ||
| 1.11.5 | All classes required for utilizing parsers in LTA Log Import are included in a new jar called tpglimport.jar. | ||
| 1.11.6 | All classes required for configuring the Agent Controller for remote import are included in a new jar called config.jar. | ||
| 1.11.7 | The Logging Agent and Common Base Event support for Java Logging has a new JAR, hl14.jar, which contains the org.eclipse.hyades.logging.java.* packages. This code was moved from the org.eclipse.hyades.logging.java plug-in. | ||
| 1.11.8 | The Logging Agent and Common Base Event support for Apache Commons Logging has a new JAR, hlcommons.jar, which contains the org.eclipse.hyades.logging.commons.* packages. This code was moved from the org.eclipse.hyades.logging.commons plug-in. | ||
| 1.11.9 | The Logging Agent and Common Base Event support for Apache Log4J Logging has a new JAR, hllog4j.jar, which contains the org.eclipse.hyades.logging.log4j.* packages. This code was moved from the org.eclipse.hyades.logging.log4j plug-in. | ||
| 1.11.10 | The non-EMF Common Base Event v1.0.1 Java implementation has a new JAR, tlcbe101.jar, which contains the org.eclipse.tptp.logging.events.cbe.* packages. This JAR contains new function that replaced the old JAR, hlevents.jar, which contained the org.eclipse.hyades.logging.events.* packages. See the Deprecated Resources Removed in TPTP v4.0.0 document for details. | ||
| 1.11.11 | All of the plug-ins in the RAC now contain the version number as part of the directory name. Change your class path from, e.g. org.eclipse.hyades.logging.parsers to org.eclipse.hyades.logging.parsers_4.0.0. |
1.12 Convert stand-alone class path to remove references to removed JARs
If you depend on TPTP JARs in a stand-alone environment, then you need to manually modify your class path to remove the following JARs.
| 1.12.1 | The old non-EMF Common Base Event v1.0.1 Java implementation JAR, hlevents.jar, which contained the org.eclipse.hyades.logging.events.* packages has been replaced by the new non-EMF Common Base Event v1.0.1 Java implementation JAR, tlcbe101.jar, which contains the org.eclipse.tptp.logging.events.cbe.* packages. See the Deprecated Resources Removed in TPTP v4.0.0 document for details. |
This section explains some of the changes that you will see in TPTP.
1. A new view, the Test Execution Monitor view has been added to the test perspective at the bottom right.
2. The plug-in for the Java wrapper and C implementation of the Logging Agent changed its <requires> in its plugin.xml file:
- org.eclipse.hyades.execution.remote was changed to org.eclipse.hyades.execution.
- org.apache.jakarta_commons_logging was added.
- org.apache.jakarta_log4j_logging was added.
3. The plug-in for the Java and C implementations of the Common Base Event v1.0.1 specification as well as Common Base Event and Logging Agent support for Apache Log4J, Apache Commons and Java Logging changed its <requires> in its plugin.xml file:
- org.eclipse.hyades.execution.remote was changed to org.eclipse.hyades.execution.
- org.apache.jakarta_commons_logging was added.
- org.apache.jakarta_log4j_logging was added.
4. The statistical view and Statcon Editor have been removed and replaced with a refactored set of views, and a minimalised Statistical Analysis editor.
Related topics:
