Re: [pde-dev] Apitool question

[Vincent GUIGNOT <Vincent.GUIGNOT@xxxxxxxxxxxx>]

Thanks Vikas,
How can I specify APITools to not scan internal package ? 



-----Message d'origine-----
De : pde-dev-bounces@xxxxxxxxxxx [mailto:pde-dev-bounces@xxxxxxxxxxx] De la part de Vikas Chandra
Envoyé : jeudi 20 novembre 2014 13:46
Cc : Eclipse PDE general developers list.; pde-dev-bounces@xxxxxxxxxxx
Objet : Re: [pde-dev] Apitool question

If you remove an already exposed API method, it is breakage ( major version increase required). If you added a new API method it is new-api-added.  (only minor version increase required).

As per my understanding, all functions/class/constructors/fields in internal packages are not APIs.
 ( but sometimes the internal  packages are exposed to few friend plugins).
Ideally internal packages
shouldn't be exposed. And there can be changes to internal package's contents without any major/minor version increase or notice. ( may be only the service segment should be increased if bug fixes are made).

Regards,
Vikas
------------------------------------------------------------------------
Eclipse Modeling/ PDE
IBM Rational
EGL D Block - Bangalore, India
Office Phone No : +91 - 80 - 41776506
------------------------------------------------------------------------



From:	Vincent GUIGNOT <Vincent.GUIGNOT@xxxxxxxxxxxx>
To:	"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Date:	11/20/2014 12:43 PM
Subject:	Re: [pde-dev] Apitool question
Sent by:	pde-dev-bounces@xxxxxxxxxxx



Thanks Curtis,
Each time I add a method to an interface, I’ve an API breakage.
Even for internal Interface ? it’s not explained clearly.
Or maybe the solution is to create other Interface instead of changing them.

De : pde-dev-bounces@xxxxxxxxxxx [mailto:pde-dev-bounces@xxxxxxxxxxx] De la part de Curtis Windatt Envoyé : mercredi 19 novembre 2014 17:02 À : Eclipse PDE general developers list.
Objet : Re: [pde-dev] Apitool question



http://wiki.eclipse.org/Version_Numbering
This wiki page describes how we increment our bundle versions.

You only need to change the bundle's major version if you make a breaking API change.  This is because changing API this way could potentially break someone using the API.  Adding new API or changing non-API code in a externally visible way only requires that the bundle gets an increment to the minor version.

If you set up PDE API Tools in your workspace with the correct API baseline, the tools can warn you if you have made a breaking API change.

Curtis

(Embedded image moved to file: pic03687.gif)Inactive hide details for Vincent GUIGNOT ---11/19/2014 09:55:46 AM---Hello everyone ! I'm beggining into the APitool world, anVincent GUIGNOT ---11/19/2014 09:55:46 AM---Hello everyone ! I'm beggining into the APitool world, and a somes questions.

From: Vincent GUIGNOT <Vincent.GUIGNOT@xxxxxxxxxxxx>
To: "pde-dev@xxxxxxxxxxx" <pde-dev@xxxxxxxxxxx>
Date: 11/19/2014 09:55 AM
Subject: [pde-dev] Apitool question
Sent by: pde-dev-bounces@xxxxxxxxxxx




Hello everyone !
I’m beggining into the APitool world, and a somes questions.
How eclipse is able to keep plugins version below the eclipse product ?
As I’ve instderstood and tried,  if we follow the APItool rules, each time an interface change, the major of the containing plugins is upgraded. So between two eclipse versions how it’s possible when following the apitool, to not upgrade the major version.

Thanks for your help_______________________________________________
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
_______________________________________________
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