Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 178160

Summary: Changes to Agent Controller's plugins folder
Product: z_Archived Reporter: Navid Mehregani <nmehrega>
Component: TPTPAssignee: Hubert Leung <hkyleung>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: guru.nagarajan, hkyleung, jkubasta, randy.d.smith
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: closed460
Bug Depends on:    
Bug Blocks: 117085, 154388    

Description Navid Mehregani CLA 2007-03-19 18:39:42 EDT
This defect is related to enhancement 173330.  Ensure that all the plugins packaged in the Agent Controller's 'plugins' folder are Eclipse plugins and they're also included as part of the TPTP's workbench plugins.

They need to be included as part of the workbench plugins in order for the new Integrated Agent Controller to be able to pick them up.  The embedded Agent Conroller always uses the plugin folder of the workbench to resolve the location of its own plugins.  This will allow the embedded Agent Controller to pick up the JVMTI and Perfmon agents.

These plugins need to be Eclipse plugins in order for the update manager to be able to update them.
Comment 1 Navid Mehregani CLA 2007-04-04 11:57:47 EDT
The components that will be affected by this are:

- JVMTI
- Probekit
- BtM
- Perfmon
Comment 2 Navid Mehregani CLA 2007-04-05 14:21:06 EDT
I've created and checked in an Eclipse plugin to hold the runtime files for perfmon.  The newly added plugin is: org.eclipse.hyades.perfmon.agents.  The runtime perfmon plugin only contains JAR files (it doesn't contain any native file).  Thus, there were no folders created for the different platforms.  This plugin should contain the same exact files as the pefrmon AC plugin.

I've added the following folder structure to the org.eclipse.tptp.platform.jvmti.runtime plugin:

- agent_files
  + linux_em64t
  + linux_ia32
  + linux_ipf
  + win_em64t
  + win_ia32
  + win_ipf

Each of these folders will contain the JVMTI native code for the indicated platform.  This plugin is currently not being shipped as part of TPTP's workbench plugins.  This has to be done in order for the JVMTI agent to work with the new IAC.  Guru, also note that you guys will need to update your pluginconfig.xml files in order for it to point to the correct location in the IAC scenario.
Comment 3 Guru Nagarajan CLA 2007-04-05 18:51:07 EDT
Navid, I just refreshed my sources and I do not see the org.eclipse.tptp.platform.jvmti.runtime -> agentfiles folder. 
Comment 4 Navid Mehregani CLA 2007-04-07 01:32:46 EDT
Guru, since the folders are empty, CVS automatically ignores them and doesn't check them out.  They will show up once the folders are populated by the build team.
Comment 5 Kiryl Kazakevich CLA 2007-04-17 12:10:32 EDT
Guru, Navid

Please let me clarify the things.

What is right and what is wrong from the following statements:

1) JVMTI profiler is going to be included to TPTP packages and AC packages in the same form: as plugins/org.eclipse.tptp.platform.jvmti.runtime.

2) This plug-in is true Eclise plug-in both in TPTP and AC packages.

3) This plug-in has identical content for all six AC packages for different platforms  (i.e. win_ia32, linux_ia32, win_ipf, etc.), and includes all six native run-times at once.
Comment 6 Guru Nagarajan CLA 2007-04-17 14:26:13 EDT
1) JVMTI profiler is going to be included to TPTP packages and AC packages in
the same form: as plugins/org.eclipse.tptp.platform.jvmti.runtime.
>>The AC package is in <<AC_HOME>>/plugins directory as the plugin org.eclipse.tptp.javaprofiler. I will find out if the name change is possible now to have the same name on both the Client side i.e. for IAC and for AC.
>>On the Eclipse WOrkbench/Client side the plugin will be called as org.eclipse.tptp.platform.jvmti.runtime.
2) This plug-in is true Eclise plug-in both in TPTP and AC packages.
This is indeed a true Eclipse plugin with its configuration file.
3) This plug-in has identical content for all six AC packages for different
platforms  (i.e. win_ia32, linux_ia32, win_ipf, etc.), and includes all six
native run-times at once.
>> I will let Navid confirm this but the answer is no on this. i.e. The IAC plugin (6 AC packages) is a seperate plugin and the so is the jvmti runtime plugin. There is no IAC package that has the IAC(AC) containing the JVMTI runtime pluging. The JVMTI runtime plugin is a seperate plugin that includes all the 6 platform packages together per comment #2
Comment 7 Navid Mehregani CLA 2007-04-17 14:36:16 EDT
Kiryl,

Number 1 and 2 are correct.  For #2, the org.eclipse.tptp.javaprofiler plugin should be replaced by org.eclipse.tptp.platform.jvmti.runtime.

As for #3: Since we have separate download links for each platform of the *stand-alone* AC, it doesn't make sense to include the native files for all the platforms in the this plug-in for the AC case.  For example, if someone downloads the AC for windows IA32, then that plugin should only contain the native files in the win_ia32 folder.  All the other folders can be empty.  

However, for the IAC scenario, we'll need to include the native files for all the platforms in this plug-in.  Now, there is a possibility that we might introduce separate download links for TPTP's workbench plugins as well, but this hasn't been confirmed yet.  For now, I'd rather include all the native files in this plugin for the IAC scenario.  We can take care of this later, if we do decide to include separate download links for TPTP's workbench.
Comment 8 Kiryl Kazakevich CLA 2007-04-19 06:37:10 EDT
Guru,

I do not see org.eclipse.tptp.platform.jvmti.runtime plug-in in TPTP packages.

I expect this one is prepared by upstream build (Hubert) and then downstream build (me) populates it with native code. As this is done for org.eclipse.tptp.platform.ac.*.

The plug-in should be just a placeholder, i.e. includes only Eclipse specific plug-in files (plugin.properties, META-INF/MANIFEST.MF).

I can not create plug-in in downstream build because it is Eclipse specific. For example the plug-in should be declared as part of some feature.
Comment 9 Navid Mehregani CLA 2007-04-19 11:58:24 EDT
As I've noted above, the org.eclipse.tptp.platform.jvmti.runtime plug-in is currently in CVS, but it's not being built into our drivers.  Hubert, can you please include this plug-in as part of TPTP's drivers so Kiryl can populate it with JVMTI's native files?
Comment 10 Hubert Leung CLA 2007-04-23 10:18:27 EDT
Kiryl, I'm reassigning this bug to you.  Please close it if your part is done. 
Comment 11 Navid Mehregani CLA 2007-04-24 12:16:18 EDT
Kiryl, the org.eclipse.platform.jvmti.runtime plug-in has been included as part of TPTP's workbench plug-ins (Thanks!), but this plug-in hasn't replaced org.eclipse.tptp.javaprofiler in the plugins folder of the stand-alone Agent Controller.
Comment 12 Navid Mehregani CLA 2007-04-27 10:21:14 EDT
Actually, let's keep the stand-alone AC packaging the same for now.  We could make things more complicated if we change it now.  
Comment 13 Navid Mehregani CLA 2007-05-02 09:58:09 EDT
Hubert, I noticed that the 'org.eclipse.hyades.perfmon.agents' AC plugin is still not being included as part of the workbench plugins.  This has to be done in order for perfmon to function properly with the new IAC.  Can you please let me know when you're planning to do this by?
Comment 14 Kiryl Kazakevich CLA 2007-05-03 02:35:17 EDT
It seems my part is done.

Hubert, reassigning to you to complete org.eclipse.hyades.perfmon.agents.
Comment 15 Hubert Leung CLA 2007-05-04 13:10:05 EDT
org.eclipse.hyades.perfmon.agents is now in the build. 
Comment 16 Sorin Stoian CLA 2007-05-04 13:24:36 EDT
org.eclipse.hyades.perfmon.agents is in the build now (TPTP-4.4.0-200705041104).
Right now it is packed as a jar but I already changed the feature to unpack it. The next builds will have the plugin unpacked.
Comment 17 Paul Slauenwhite CLA 2009-06-30 14:15:28 EDT
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 enhancement/defect has been resolved and unverified for more than 1 year 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.