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

Bug 472778

Summary: Launch validation doesn't find plugin needed in two versions
Product: [Eclipse Project] PDE Reporter: Donald Dunne <donald.g.dunne>
Component: UIAssignee: Vikas Chandra <Vikas.Chandra>
Status: VERIFIED FIXED QA Contact:
Severity: major    
Priority: P3 CC: claudiai, curtis.windatt.public, donp, eclipse, Lars.Vogel, Vikas.Chandra
Version: 4.5   
Target Milestone: 4.6 M3   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 480020    
Attachments:
Description Flags
Constriant error
none
Fix for this issue
none
Updated patch none

Description Donald Dunne CLA 2015-07-15 19:31:58 EDT 
Debug launch configuration validation gets Missing Constraint when two versions of same bundle are required.

Looks like the same issue as bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=367187 which was fixed in 4.5.  I downloaded the same demo patch for luna and mars and proved that the fix worked for the product editor validtion.  Howeer, it is still is broken for launch configuration dialog validation.

Demo workspace from bug above at https://bugs.eclipse.org/bugs/attachment.cgi?id=246785 can be used to reproduce problem.

- Download Mars 
- Download above workspace
- Launch Mars with workspace
- Add required gmf budles to resolve compile issues
- Debug pulldown
- Debug Configurations
- Eclipse Application - product.product
- Plugins tab
- Validate gets batik [1.6.0, 1.7.0) missing constraint errors
Comment 1 Vikas Chandra CLA 2015-08-03 04:37:18 EDT 
Created attachment 255584 [details]
Constriant error

I followed the steps and got this issue. Is this the issue mentioned.


Can you please give detailed steps to recreate the issue with snapshot if possible.
Comment 2 Curtis Windatt CLA 2015-08-06 14:25:23 EDT 
A simple test will not reproduce the problem.  I created two plug-ins, both depending on org.apache.commons.logging, but each require a different version.  I then create a launch config that includes the two test plug-ins as well as both versions of the logging plugin.  Validating the plug-in contents of the launch config indicates that all plug-in requirements are met.

I am removing the milestone of 4.5.1 as I don't think the described problem is happening.  If you can provide a test case to reproduce or at point at the code path that causes it, we can take another look.

If you are using multiple versions of a plug-in that are in your workspace, you may be running into Bug 449102.

I also noticed that the manifest editor does not allow you to add dependencies on multiple versions of the same bundle.
Comment 3 Don Purnhagen CLA 2015-08-20 13:43:10 EDT 
To confirm this bug (or behavior if it is not a bug) do this:

Make sure that you have these 2 features installed:
    org.eclipse.e4.rcp
    org.eclipse.sirius.runtime.ide.ui
    (you may need to install the sirius modeling components)
Create a Run Configuration for an Eclipse Application.
Go to the Plug-ins tab.
Change "Launch with:" combo to "features selected below".
Deselect all features.
Select the 2 features above.
Press "Select Required".
Press "Validate Plug-ins".

The problem is that org.eclipse.e4.rcp needs some of the org.apache.batik.* plug-ins in the range [1.7.0,1.8.0) and org.eclipse.sirius.runtime.ide.ui requires the same plug-ins in the range [1.6.0,1.7.0). Both co-exist just fine in the main Eclipse installation, but will not both load in the Run Configuration. 

Also, trying to export a product that needs both of those features will result in missing bundle errors on the same plug-ins too.
Comment 4 Don Purnhagen CLA 2015-09-16 12:30:40 EDT 
Is there any chance of getting this looked at? We are unable to move our application from Kepler to Mars as long as this condition is present. At least a status change to CONFIRMED would be some progress.
Comment 5 Vikas Chandra CLA 2015-09-23 04:29:09 EDT 
I am unable to get these plugins for Neon( or do they not exist in Neon)

org.eclipse.e4.rcp
org.eclipse.sirius.runtime.ide.ui

Can you please point to me right install location
Comment 6 Vikas Chandra CLA 2015-09-25 05:31:32 EDT 
Hi Lars,

For Neon, what is the installation location for the feature/plugin- org.eclipse.e4.rcp?
Comment 7 Vikas Chandra CLA 2015-09-25 05:35:09 EDT 
Don, 

can you give install location for org.eclipse.sirius.runtime.ide.ui for Neon? Will the full modelling install install this?
Comment 8 Don Purnhagen CLA 2015-10-09 10:05:52 EDT 
Sorry for the delay in responding. It is not that we have lost interest, we still need this desperately, I have just been busy trying to port to Mars.

We installed Neon M2, the committers edition. Go to the Neon update site and under the Modeling category, install the feature:

	Graphical Modeling Framework (GMF) Runtime

Create a new run configuration for an Eclipse Application. On the plug-ins tab, change to "features selected below". Deselect all features, and then select only:

	org.eclipse.e4.rcp
	org.eclipse.gmf.runtime.thirdparty

Then select required. Now validate the plug-ins.

The validation error is caused because the two features require different versions of the plug-ins:

	org.apache.batik.css
	org.apache.batik.util
	org.apache.batik.util.gui

Besides the validation error, there is a similar error when you try to run the configuration. There would also be an error if you try to export a product that requires both of those features.
Comment 9 Donald Dunne CLA 2015-10-12 15:26:47 EDT 
(In reply to Don Purnhagen from comment #8)
> Sorry for the delay in responding. It is not that we have lost interest, we
> still need this desperately, I have just been busy trying to port to Mars.
> 
> We installed Neon M2, the committers edition. Go to the Neon update site and
> under the Modeling category, install the feature:
> 
> 	Graphical Modeling Framework (GMF) Runtime
> 
> Create a new run configuration for an Eclipse Application. On the plug-ins
> tab, change to "features selected below". Deselect all features, and then
> select only:
> 
> 	org.eclipse.e4.rcp
> 	org.eclipse.gmf.runtime.thirdparty
> 
> Then select required. Now validate the plug-ins.
> 
> The validation error is caused because the two features require different
> versions of the plug-ins:
> 
> 	org.apache.batik.css
> 	org.apache.batik.util
> 	org.apache.batik.util.gui
> 
> Besides the validation error, there is a similar error when you try to run
> the configuration. There would also be an error if you try to export a
> product that requires both of those features.

Thanks for coming up with a repeatable case.  This is exactly what we're seeing using both Luna and Mars and it's affecting our development.  Only work-around is to switch to plugin-based launching which has it's own complications.  We are equaly as interested in getting this resolved.
Comment 10 Vikas Chandra CLA 2015-10-13 05:42:43 EDT 
I am able to recreate the issue mentioned in comment#8.
Comment 11 Vikas Chandra CLA 2015-10-16 07:18:10 EDT 
Created attachment 257296 [details]
Fix for this issue

>>		//remove conflicting duplicates - if they have same version or both are singleton

In BundleLauncherHelper, even when this criteria was not satisfied, one of the  bundles was removed if the plugin name was same ( reason being they were added by a HashMap and not a MultiHashMap). 

I have attached a potential fix. I will test it and release it early next week in 4.6 stream ( Neon)

Do you think the fix should be there in 4.5.2 (Mars) as well?
Comment 12 Don Purnhagen CLA 2015-10-16 08:03:36 EDT 
(In reply to Vikas Chandra from comment #11)
> ...
> Do you think the fix should be there in 4.5.2 (Mars) as well?

Since it is a very short patch, YES. If it works for Neon, I would like to see it back ported to Mars as well. In fact, we are going to look at the possibility of applying it to Mars here so that we can get a head start.

There is also a very similar issue in PDE when trying to export a product with the same conflicting plugins. Do I need to submit a new bug report to have that looked at?

Thank you for your efforts.
Comment 13 Vikas Chandra CLA 2015-10-16 08:22:23 EDT 
>There is also a very similar issue in PDE when trying to export a product with >the same conflicting plugins. Do I need to submit a new bug report to have that >looked at?

If the problem persists with this patch, then you can probably create a new bug with steps on how to recreate it.
Comment 14 Donald Dunne CLA 2015-10-16 11:18:35 EDT 
(In reply to Vikas Chandra from comment #11)
> Created attachment 257296 [details]
> Fix for this issue
> 
> >>		//remove conflicting duplicates - if they have same version or both are singleton
> 
> In BundleLauncherHelper, even when this criteria was not satisfied, one of
> the  bundles was removed if the plugin name was same ( reason being they
> were added by a HashMap and not a MultiHashMap). 
> 
> I have attached a potential fix. I will test it and release it early next
> week in 4.6 stream ( Neon)
> 
> Do you think the fix should be there in 4.5.2 (Mars) as well?

We would very much like the fix in Mars.
Comment 15 Vikas Chandra CLA 2015-10-17 06:53:19 EDT 
Created attachment 257328 [details]
Updated patch

Updated patch attached
Comment 16 Vikas Chandra CLA 2015-10-17 07:31:58 EDT 
Fixed via https://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/?id=c8079e8af76c30b7e875f3bab24048f4ddda8aed



If the fix doesn't fix "export a product with the same conflicting plugins", can you please open a bug for that.
Comment 17 Vikas Chandra CLA 2015-10-17 07:34:54 EDT 
opened bug 480020 for Mars stream
Comment 18 Claudia Irvine CLA 2015-10-21 15:45:52 EDT 
The patch fixed both the launch and the export product. Thanks.
Comment 19 Vikas Chandra CLA 2015-10-21 15:53:22 EDT 
Excellent  !!

I will port the patch in 4.5.2 via bug 480020.
Comment 20 Vikas Chandra CLA 2015-10-27 02:32:26 EDT 
verified in

Version: Neon (4.6)
Build id: N20151024-1500
Comment 21 Claudia Irvine CLA 2018-09-25 08:41:00 EDT 
I am still encountering this problem in 2018-09 (4.9)
Build id: I20180906-0745.

Same batik plugins too. This time with the plugin org.eclipse.sirius.diagram.ui
Comment 22 Niko Stotz CLA 2019-06-14 07:45:31 EDT 
I still get this in 2019-06RC2. Still batik, but also org.antlr.runtime (3.2 required from Xtext 2.18 vs. 4.3 required from Sirius 6.2).
Comment 23 Niko Stotz CLA 2019-06-14 07:46:22 EDT 
For clarification: The *validation* finds the issue, but not the *add required dependencies*.
Comment 24 Vikas Chandra CLA 2019-06-17 00:27:13 EDT 
(In reply to Niko Stotz from comment #22)
> I still get this in 2019-06RC2. Still batik, but also org.antlr.runtime (3.2
> required from Xtext 2.18 vs. 4.3 required from Sirius 6.2).

Can you give detailed steps please?
Comment 25 Niko Stotz CLA 2019-06-18 08:35:07 EDT 
(In reply to Vikas Chandra from comment #24)
> (In reply to Niko Stotz from comment #22)
> > I still get this in 2019-06RC2. Still batik, but also org.antlr.runtime (3.2
> > required from Xtext 2.18 vs. 4.3 required from Sirius 6.2).
> 
> Can you give detailed steps please?

Sure, see https://github.com/enikao/eclipse-bug-472778/tree/master

Steps to reproduce:

1. Create new workspace
2. Load all projects from repository
3. Set target platform in target project
4. Open Launch Configs dialog
5. Select Eclipse-Bug launch config. It contains only the single custom plug-in.
6. Trigger Add Required Plug-ins
7. Trigger Validate Plug-ins

Expected outcome: Complete launch config without missing dependencies
Actual outcome: The following dependencies are missing, because there is a newer version available and included in the run config (newer version in parenthesis):

* org.apache.batik.css 1.6.0 (1.11.0) [also some other batik stuff]
* org.antlr.runtime 3.2.0 (4.3.0)
* com.google.guava 21.0.0 (27.1.0)

Versions:

Version: 2019-06 RC1 (4.12.0RC1)
Build id: 20190606-1049

Relevant Plug-ins:
org.eclipse.equinox.app (1.4.200.v20190516-1504) "Equinox Application Container" [Active]
org.eclipse.equinox.bidi (1.2.0.v20190514-1046) "Bidirectional Text Support" [Starting]
org.eclipse.equinox.common (3.10.400.v20190516-1504) "Common Eclipse Runtime" [Active]
org.eclipse.equinox.concurrent (1.1.300.v20190514-1046) "Equinox Concurrent API" [Active]
org.eclipse.equinox.console (1.3.300.v20190516-1504) "Console plug-in" [Active]
org.eclipse.equinox.event (1.5.100.v20190528-1257) "Event Admin" [Active]
org.eclipse.equinox.frameworkadmin (2.1.300.v20190318-1320) "Equinox Framework Admin" [Active]
org.eclipse.equinox.frameworkadmin.equinox (1.1.100.v20180822-1258) "Equinox Framework Admin for Equinox" [Active]
org.eclipse.equinox.http.jetty (3.7.100.v20190516-1504) "Jetty Http Service" [Starting]
org.eclipse.equinox.http.registry (1.1.700.v20190214-1948) "Http Service Registry Extensions" [Resolved]
org.eclipse.equinox.http.servlet (1.6.100.v20190516-1504) "Http Services Servlet" [Starting]
org.eclipse.equinox.jsp.jasper (1.1.200.v20190214-1948) "Jasper Jsp Support Bundle" [Starting]
org.eclipse.equinox.jsp.jasper.registry (1.1.200.v20190214-1948) "Jasper Jsp Registry Support Plug-in" [Starting]
org.eclipse.equinox.launcher (1.5.400.v20190515-0925) "Equinox Launcher" [Resolved]
org.eclipse.equinox.launcher.win32.win32.x86_64 (1.1.1000.v20190125-2016) "Equinox Launcher Win32 X86_64 Fragment" [Resolved]
org.eclipse.equinox.p2.artifact.repository (1.3.100.v20190330-1646) "Equinox Provisioning Artifact Repository Support" [Active]
org.eclipse.equinox.p2.console (1.1.100.v20180822-1258) "Equinox Provisioning Console" [Starting]
org.eclipse.equinox.p2.core (2.6.0.v20190215-2242) "Equinox Provisioning Core" [Active]
org.eclipse.equinox.p2.director (2.4.300.v20190215-2242) "Equinox Provisioning Director" [Active]
org.eclipse.equinox.p2.director.app (1.1.200.v20180822-1302) "Equinox Provisioning Director Application" [Starting]
org.eclipse.equinox.p2.directorywatcher (1.2.200.v20190204-0752) "Equinox Provisioning Directory Watcher" [Active]
org.eclipse.equinox.p2.discovery (1.1.100.v20180822-1302) "Equinox Provisioning Discovery" [Resolved]
org.eclipse.equinox.p2.discovery.compatibility (1.1.100.v20180822-1302) "Equinox Provisioning Discovery" [Starting]
org.eclipse.equinox.p2.engine (2.6.300.v20190318-1320) "Equinox Provisioning Engine" [Active]
org.eclipse.equinox.p2.extensionlocation (1.3.100.v20180822-1302) "Equinox Provisioning Extension Location Repository Support" [Active]
org.eclipse.equinox.p2.garbagecollector (1.1.100.v20180822-1302) "Equinox Provisioning Garbage Collector" [Active]
org.eclipse.equinox.p2.jarprocessor (1.1.200.v20180921-1009) "Equinox Provisioning JAR Processor" [Resolved]
org.eclipse.equinox.p2.metadata (2.4.400.v20190409-0548) "Equinox Provisioning Metadata" [Active]
org.eclipse.equinox.p2.metadata.repository (1.3.100.v20180822-1302) "Equinox Provisioning Metadata Repository" [Active]
org.eclipse.equinox.p2.operations (2.5.400.v20190408-2008) "Equinox Provisioning Operations API" [Active]
org.eclipse.equinox.p2.publisher (1.5.100.v20180822-1302) "Equinox Provisioning Publisher Infrastructure" [Active]
org.eclipse.equinox.p2.publisher.eclipse (1.3.200.v20190329-1624) "Equinox Provisioning Publisher for Eclipse" [Starting]
org.eclipse.equinox.p2.reconciler.dropins (1.3.0.v20181023-0914) "Equinox Provisioning Drop-in" [Active]
org.eclipse.equinox.p2.repository (2.4.400.v20190318-1320) "Equinox Provisioning Repository" [Active]
org.eclipse.equinox.p2.repository.tools (2.2.200.v20181102-0649) "Equinox Provisioning Repository Tools" [Starting]
org.eclipse.equinox.p2.touchpoint.eclipse (2.2.300.v20190215-2242) "Equinox Provisioning Eclipse Touchpoint" [Active]
org.eclipse.equinox.p2.touchpoint.natives (1.3.200.v20180921-1019) "Equinox Provisioning Native Touchpoint" [Active]
org.eclipse.equinox.p2.transport.ecf (1.2.100.v20180822-1354) "Equinox Provisioning ECF based Transport" [Active]
org.eclipse.equinox.p2.ui (2.5.500.v20190220-1158) "Equinox Provisioning UI Support" [Active]
org.eclipse.equinox.p2.ui.discovery (1.1.100.v20180822-1357) "Equinox Provisioning Discovery UI" [Resolved]
org.eclipse.equinox.p2.ui.importexport (1.2.100.v20180827-1122) "Equinox Provisioning Import and Export" [Starting]
org.eclipse.equinox.p2.ui.sdk (1.1.200.v20181214-0802) "Equinox Provisioning Platform Update Support" [Active]
org.eclipse.equinox.p2.ui.sdk.scheduler (1.4.200.v20181102-0649) "Equinox Provisioning Platform Automatic Update Support" [Active]
org.eclipse.equinox.p2.updatechecker (1.2.100.v20180827-1122) "Equinox Provisioning Update Checker" [Active]
org.eclipse.equinox.p2.updatesite (1.1.100.v20180827-1122) "Equinox Provisioning Legacy Update Site Support" [Starting]
org.eclipse.equinox.preferences (3.7.400.v20190516-1504) "Eclipse Preferences Mechanism" [Active]
org.eclipse.equinox.registry (3.8.400.v20190516-1504) "Extension Registry Support" [Active]
org.eclipse.equinox.security (1.3.200.v20190516-1504) "Equinox Java Authentication and Authorization Service (JAAS)" [Active]
org.eclipse.equinox.security.ui (1.2.300.v20190514-1046) "Equinox Security Default UI" [Starting]
org.eclipse.equinox.security.win32.x86_64 (1.1.100.v20180827-1235) "Windows Data Protection services integration (64 bit)" [Resolved]
org.eclipse.equinox.simpleconfigurator (1.3.200.v20181101-1115) "Simple Configurator" [Active]
org.eclipse.equinox.simpleconfigurator.manipulator (2.1.200.v20181123-1405) "Simple Configurator Manipulator" [Active]
org.eclipse.equinox.util (1.1.200.v20181008-1820) "Equinox Util Bundle" [Starting]
org.eclipse.osgi (3.14.0.v20190517-1309) "OSGi System Bundle" [Active]
org.eclipse.osgi.compatibility.state (1.1.500.v20190516-1407) "Equinox State and Resolver Compatibility Fragment" [Resolved]
org.eclipse.osgi.services (3.8.0.v20190206-2147) "OSGi Release 4.2.0 Services" [Resolved]
org.eclipse.osgi.util (3.5.200.v20190115-2323) "OSGi Release 4.2.0 Utility Classes" [Resolved]
org.eclipse.pde (3.13.600.v20190531-0245) "PDE" [Resolved]
org.eclipse.pde.api.tools (1.1.800.v20190517-1501) "API Tools" [Starting]
org.eclipse.pde.api.tools.annotations (1.1.300.v20190513-1223) "PDE API Tools Annotations" [Resolved]
org.eclipse.pde.api.tools.ui (1.1.700.v20190513-1223) "API Tools UI" [Starting]
org.eclipse.pde.build (3.10.400.v20190320-1020) "Plug-in Development Environment Build Support" [Active]
org.eclipse.pde.core (3.13.0.v20190513-1223) "PDE Core" [Active]
org.eclipse.pde.doc.user (3.14.400.v20190529-0756) "PDE User Guide" [Resolved]
org.eclipse.pde.ds.annotations (1.1.400.v20190514-1319) "Declarative Services Annotations Support" [Active]
org.eclipse.pde.ds.core (1.1.500.v20190513-1223) "PDE DS Core" [Starting]
org.eclipse.pde.ds.lib (1.1.300.v20190417-0900) "Annotations for Declarative Services v1.3" [Resolved]
org.eclipse.pde.ds.ui (1.1.600.v20190513-1223) "PDE DS UI" [Starting]
org.eclipse.pde.ds1_2.lib (1.0.300.v20190417-0900) "Annotations for Declarative Services v1.2" [Resolved]
org.eclipse.pde.genericeditor.extension (1.0.500.v20190513-1223) "Target definition generic editor extension" [Active]
org.eclipse.pde.junit.runtime (3.5.400.v20190513-1223) "PDE JUnit Runtime Support" [Starting]
org.eclipse.pde.launching (3.7.600.v20190513-1223) "PDE Launching Support" [Active]
org.eclipse.pde.runtime (3.6.500.v20190513-1223) "PDE Runtime" [Starting]
org.eclipse.pde.ua.core (1.1.300.v20190513-1223) "PDE UA Core" [Starting]
org.eclipse.pde.ua.ui (1.1.500.v20190513-1223) "PDE UA UI" [Starting]
org.eclipse.pde.ui (3.11.0.v20190520-2013) "PDE UI" [Active]
org.eclipse.pde.ui.templates (3.6.600.v20190513-1223) "PDE Templates" [Resolved]
org.eclipse.platform (4.12.0.v20190531-0245) "Eclipse Platform" [Resolved]
Comment 26 Vikas Chandra CLA 2019-06-19 03:49:42 EDT 
(In reply to Niko Stotz from comment #25)
> (In reply to Vikas Chandra from comment #24)
> > (In reply to Niko Stotz from comment #22)
> > > I still get this in 2019-06RC2. Still batik, but also org.antlr.runtime (3.2
> > > required from Xtext 2.18 vs. 4.3 required from Sirius 6.2).
> > 
> > Can you give detailed steps please?
> 
> Sure, see https://github.com/enikao/eclipse-bug-472778/tree/master
> 
> Steps to reproduce:
> 
> 1. Create new workspace
> 2. Load all projects from repository
> 3. Set target platform in target project
> 4. Open Launch Configs dialog
> 5. Select Eclipse-Bug launch config. It contains only the single custom
> plug-in.
> 6. Trigger Add Required Plug-ins
> 7. Trigger Validate Plug-ins
> 
> Expected outcome: Complete launch config without missing dependencies
> Actual outcome: The following dependencies are missing, because there is a
> newer version available and included in the run config (newer version in
> parenthesis):
> 
> * org.apache.batik.css 1.6.0 (1.11.0) [also some other batik stuff]
> * org.antlr.runtime 3.2.0 (4.3.0)
> * com.google.guava 21.0.0 (27.1.0)
> 
> Versions:
> 
> Version: 2019-06 RC1 (4.12.0RC1)
> Build id: 20190606-1049
> 
> Relevant Plug-ins:
> org.eclipse.equinox.app (1.4.200.v20190516-1504) "Equinox Application
> Container" [Active]
> org.eclipse.equinox.bidi (1.2.0.v20190514-1046) "Bidirectional Text Support"
> [Starting]
> org.eclipse.equinox.common (3.10.400.v20190516-1504) "Common Eclipse
> Runtime" [Active]
> org.eclipse.equinox.concurrent (1.1.300.v20190514-1046) "Equinox Concurrent
> API" [Active]
> org.eclipse.equinox.console (1.3.300.v20190516-1504) "Console plug-in"
> [Active]
> org.eclipse.equinox.event (1.5.100.v20190528-1257) "Event Admin" [Active]
> org.eclipse.equinox.frameworkadmin (2.1.300.v20190318-1320) "Equinox
> Framework Admin" [Active]
> org.eclipse.equinox.frameworkadmin.equinox (1.1.100.v20180822-1258) "Equinox
> Framework Admin for Equinox" [Active]
> org.eclipse.equinox.http.jetty (3.7.100.v20190516-1504) "Jetty Http Service"
> [Starting]
> org.eclipse.equinox.http.registry (1.1.700.v20190214-1948) "Http Service
> Registry Extensions" [Resolved]
> org.eclipse.equinox.http.servlet (1.6.100.v20190516-1504) "Http Services
> Servlet" [Starting]
> org.eclipse.equinox.jsp.jasper (1.1.200.v20190214-1948) "Jasper Jsp Support
> Bundle" [Starting]
> org.eclipse.equinox.jsp.jasper.registry (1.1.200.v20190214-1948) "Jasper Jsp
> Registry Support Plug-in" [Starting]
> org.eclipse.equinox.launcher (1.5.400.v20190515-0925) "Equinox Launcher"
> [Resolved]
> org.eclipse.equinox.launcher.win32.win32.x86_64 (1.1.1000.v20190125-2016)
> "Equinox Launcher Win32 X86_64 Fragment" [Resolved]
> org.eclipse.equinox.p2.artifact.repository (1.3.100.v20190330-1646) "Equinox
> Provisioning Artifact Repository Support" [Active]
> org.eclipse.equinox.p2.console (1.1.100.v20180822-1258) "Equinox
> Provisioning Console" [Starting]
> org.eclipse.equinox.p2.core (2.6.0.v20190215-2242) "Equinox Provisioning
> Core" [Active]
> org.eclipse.equinox.p2.director (2.4.300.v20190215-2242) "Equinox
> Provisioning Director" [Active]
> org.eclipse.equinox.p2.director.app (1.1.200.v20180822-1302) "Equinox
> Provisioning Director Application" [Starting]
> org.eclipse.equinox.p2.directorywatcher (1.2.200.v20190204-0752) "Equinox
> Provisioning Directory Watcher" [Active]
> org.eclipse.equinox.p2.discovery (1.1.100.v20180822-1302) "Equinox
> Provisioning Discovery" [Resolved]
> org.eclipse.equinox.p2.discovery.compatibility (1.1.100.v20180822-1302)
> "Equinox Provisioning Discovery" [Starting]
> org.eclipse.equinox.p2.engine (2.6.300.v20190318-1320) "Equinox Provisioning
> Engine" [Active]
> org.eclipse.equinox.p2.extensionlocation (1.3.100.v20180822-1302) "Equinox
> Provisioning Extension Location Repository Support" [Active]
> org.eclipse.equinox.p2.garbagecollector (1.1.100.v20180822-1302) "Equinox
> Provisioning Garbage Collector" [Active]
> org.eclipse.equinox.p2.jarprocessor (1.1.200.v20180921-1009) "Equinox
> Provisioning JAR Processor" [Resolved]
> org.eclipse.equinox.p2.metadata (2.4.400.v20190409-0548) "Equinox
> Provisioning Metadata" [Active]
> org.eclipse.equinox.p2.metadata.repository (1.3.100.v20180822-1302) "Equinox
> Provisioning Metadata Repository" [Active]
> org.eclipse.equinox.p2.operations (2.5.400.v20190408-2008) "Equinox
> Provisioning Operations API" [Active]
> org.eclipse.equinox.p2.publisher (1.5.100.v20180822-1302) "Equinox
> Provisioning Publisher Infrastructure" [Active]
> org.eclipse.equinox.p2.publisher.eclipse (1.3.200.v20190329-1624) "Equinox
> Provisioning Publisher for Eclipse" [Starting]
> org.eclipse.equinox.p2.reconciler.dropins (1.3.0.v20181023-0914) "Equinox
> Provisioning Drop-in" [Active]
> org.eclipse.equinox.p2.repository (2.4.400.v20190318-1320) "Equinox
> Provisioning Repository" [Active]
> org.eclipse.equinox.p2.repository.tools (2.2.200.v20181102-0649) "Equinox
> Provisioning Repository Tools" [Starting]
> org.eclipse.equinox.p2.touchpoint.eclipse (2.2.300.v20190215-2242) "Equinox
> Provisioning Eclipse Touchpoint" [Active]
> org.eclipse.equinox.p2.touchpoint.natives (1.3.200.v20180921-1019) "Equinox
> Provisioning Native Touchpoint" [Active]
> org.eclipse.equinox.p2.transport.ecf (1.2.100.v20180822-1354) "Equinox
> Provisioning ECF based Transport" [Active]
> org.eclipse.equinox.p2.ui (2.5.500.v20190220-1158) "Equinox Provisioning UI
> Support" [Active]
> org.eclipse.equinox.p2.ui.discovery (1.1.100.v20180822-1357) "Equinox
> Provisioning Discovery UI" [Resolved]
> org.eclipse.equinox.p2.ui.importexport (1.2.100.v20180827-1122) "Equinox
> Provisioning Import and Export" [Starting]
> org.eclipse.equinox.p2.ui.sdk (1.1.200.v20181214-0802) "Equinox Provisioning
> Platform Update Support" [Active]
> org.eclipse.equinox.p2.ui.sdk.scheduler (1.4.200.v20181102-0649) "Equinox
> Provisioning Platform Automatic Update Support" [Active]
> org.eclipse.equinox.p2.updatechecker (1.2.100.v20180827-1122) "Equinox
> Provisioning Update Checker" [Active]
> org.eclipse.equinox.p2.updatesite (1.1.100.v20180827-1122) "Equinox
> Provisioning Legacy Update Site Support" [Starting]
> org.eclipse.equinox.preferences (3.7.400.v20190516-1504) "Eclipse
> Preferences Mechanism" [Active]
> org.eclipse.equinox.registry (3.8.400.v20190516-1504) "Extension Registry
> Support" [Active]
> org.eclipse.equinox.security (1.3.200.v20190516-1504) "Equinox Java
> Authentication and Authorization Service (JAAS)" [Active]
> org.eclipse.equinox.security.ui (1.2.300.v20190514-1046) "Equinox Security
> Default UI" [Starting]
> org.eclipse.equinox.security.win32.x86_64 (1.1.100.v20180827-1235) "Windows
> Data Protection services integration (64 bit)" [Resolved]
> org.eclipse.equinox.simpleconfigurator (1.3.200.v20181101-1115) "Simple
> Configurator" [Active]
> org.eclipse.equinox.simpleconfigurator.manipulator (2.1.200.v20181123-1405)
> "Simple Configurator Manipulator" [Active]
> org.eclipse.equinox.util (1.1.200.v20181008-1820) "Equinox Util Bundle"
> [Starting]
> org.eclipse.osgi (3.14.0.v20190517-1309) "OSGi System Bundle" [Active]
> org.eclipse.osgi.compatibility.state (1.1.500.v20190516-1407) "Equinox State
> and Resolver Compatibility Fragment" [Resolved]
> org.eclipse.osgi.services (3.8.0.v20190206-2147) "OSGi Release 4.2.0
> Services" [Resolved]
> org.eclipse.osgi.util (3.5.200.v20190115-2323) "OSGi Release 4.2.0 Utility
> Classes" [Resolved]
> org.eclipse.pde (3.13.600.v20190531-0245) "PDE" [Resolved]
> org.eclipse.pde.api.tools (1.1.800.v20190517-1501) "API Tools" [Starting]
> org.eclipse.pde.api.tools.annotations (1.1.300.v20190513-1223) "PDE API
> Tools Annotations" [Resolved]
> org.eclipse.pde.api.tools.ui (1.1.700.v20190513-1223) "API Tools UI"
> [Starting]
> org.eclipse.pde.build (3.10.400.v20190320-1020) "Plug-in Development
> Environment Build Support" [Active]
> org.eclipse.pde.core (3.13.0.v20190513-1223) "PDE Core" [Active]
> org.eclipse.pde.doc.user (3.14.400.v20190529-0756) "PDE User Guide"
> [Resolved]
> org.eclipse.pde.ds.annotations (1.1.400.v20190514-1319) "Declarative
> Services Annotations Support" [Active]
> org.eclipse.pde.ds.core (1.1.500.v20190513-1223) "PDE DS Core" [Starting]
> org.eclipse.pde.ds.lib (1.1.300.v20190417-0900) "Annotations for Declarative
> Services v1.3" [Resolved]
> org.eclipse.pde.ds.ui (1.1.600.v20190513-1223) "PDE DS UI" [Starting]
> org.eclipse.pde.ds1_2.lib (1.0.300.v20190417-0900) "Annotations for
> Declarative Services v1.2" [Resolved]
> org.eclipse.pde.genericeditor.extension (1.0.500.v20190513-1223) "Target
> definition generic editor extension" [Active]
> org.eclipse.pde.junit.runtime (3.5.400.v20190513-1223) "PDE JUnit Runtime
> Support" [Starting]
> org.eclipse.pde.launching (3.7.600.v20190513-1223) "PDE Launching Support"
> [Active]
> org.eclipse.pde.runtime (3.6.500.v20190513-1223) "PDE Runtime" [Starting]
> org.eclipse.pde.ua.core (1.1.300.v20190513-1223) "PDE UA Core" [Starting]
> org.eclipse.pde.ua.ui (1.1.500.v20190513-1223) "PDE UA UI" [Starting]
> org.eclipse.pde.ui (3.11.0.v20190520-2013) "PDE UI" [Active]
> org.eclipse.pde.ui.templates (3.6.600.v20190513-1223) "PDE Templates"
> [Resolved]
> org.eclipse.platform (4.12.0.v20190531-0245) "Eclipse Platform" [Resolved]

I think we should make a new bug out of this.
Comment 27 Niko Stotz CLA 2019-06-19 07:30:10 EDT 
(In reply to Vikas Chandra from comment #26)
> I think we should make a new bug out of this.

Done: Bug 548429