[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Changes in API in Juno
Just to clarify: the PDE API did not change. Anything in internal packages can change at any day. For details see http://www.eclipse.org/articles/article.php?file=Article-API-Use/index.html.

Dani

From: Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>
To: "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>,
Date: 27.02.2012 17:20
Subject: Re: [pde-dev] Changes in API in Juno




Hi Dimitar,

What classes are you using from those packages? It is unlikely that we will replace the internal classes assuming the same tasks can be accomplished using the official API.

Curtis

From: "Giormov, Dimitar" <dimitar.giormov@xxxxxxx>
To: "pde-dev@xxxxxxxxxxx" <pde-dev@xxxxxxxxxxx>,
Date: 2012/02/27 10:09 AM
Subject: [pde-dev] Changes in API in Juno
Sent by: pde-dev-bounces@xxxxxxxxxxx



Hi,
 
We are trying to adopt Juno for our product so we can assure that everything works. Unfortunately we stumbled upon an change in the packages of the PDE that we use a lot.
These are: org.eclipse.pde.internal.core.target packages.  Which have become an API so the “internal” from the package is now removed. However this puts us in a situation where we have to start maintain 2 separate versions of our product one for Indigo and one for Juno.  (and this is the only thing that we use and is different between the 2 versions).
 
So my question would be: Is it possible that we get the packages back and set them to deprecated for Juno release and remove them in the next release?
 
Best regards,
Dimitar
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev

_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev