Hi Vikas,
Since I'm using a target platform that references p2 update sites only, the only meaningful test
for me is when the patch is applied to
download.eclipse.org/eclipse/updates/4.5. So whenever it's made available there, let me know. Do you know when 4.5.2 will be released?
I appreciate your help
From: Vikas Chandra <Vikas.Chandra@xxxxxxxxxx>
Sent: Wednesday, November 4, 2015 11:31 PM
To: Eclipse PDE general developers list.
Cc: vinceos@xxxxxxxxxxx
Subject: Re: [pde-dev] product failing to load multiple versions of the sameplugin
Hi Vincent
Can you check if this fix has solved the issue -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=472778
We are planning to port this in 4.5.2 via bug 480020.
Regards,
Vikas
------------------------------------------------------------------------
Eclipse Modeling/ PDE
IBM Rational
EGL D Block - Bangalore, India
Office Phone No : +91 - 80 - 41776506
------------------------------------------------------------------------
Vincent
Smith ---11/05/2015 05:29:13 AM---Mars p2 repositories (download.eclipse.org/eclipse/updates/4.5 and download.eclipse.org/releases/mar
From: Vincent Smith <vinceos@xxxxxxxxxxx>
To: "pde-dev@xxxxxxxxxxx" <pde-dev@xxxxxxxxxxx>
Date: 11/05/2015 05:29 AM
Subject: [pde-dev] product failing to load multiple versions of the same plugin
Sent by: pde-dev-bounces@xxxxxxxxxxx
Mars p2 repositories (download.eclipse.org/eclipse/updates/4.5
and download.eclipse.org/releases/mars) have 2 versions of several bundles:
org.apache.batik.util_1.6.0.v201011041432
org.apache.batik.util_1.7.0.v201011041433
org.apache.batik.util.gui_1.6.0.v201011041432
org.apache.batik.util.gui_1.7.0.v200903091627
org.apache.batik.css_1.6.0.v201011041432
org.apache.batik.css_1.7.0.v201011041433
Bundles with 1.6.0.v201011041432 version are required by BIRT and GMF and 1.7.0.v201011041433 are required by the Eclipse Platform.
The problem is when a product is launched, only the latest version of the batik plugins is included, which results in plugin validation failures at launch. The only way to address it is to add the plugins manually in the run configuration
for the product. This is an unacceptable solution when it comes to building and deploying the feature-based product automatically from p2 sites.
I found a bugzilla article that shows this is not a new issue (https://bugs.eclipse.org/bugs/show_bug.cgi?id=367187).
The article implies the the problem is in the org.eclipe.pde.ui plugin and a patch was supposed to have been applied in 4.5 that fixed this issue. If it has been fixed, can someone provide me an update site for the pde that contains the patch? If not, do you
know when it will be fixed and updated?
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pde-dev
|