Eclipse Community Forums: Plugin Development Environment (PDE)

Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE API Tooling

Thu, 25 June 2009 12:24

Eclipse User

Hi Folks,

I'm trialling the pde api tools for use within our organization and I'm
seeing some behavior that I dont understand. Hopefully someone will be able
to explain the rational.

I have a reference plugin v1.0.0 (my baseline)

I have a separate identical copy of that plugin imported into my workspace
(the working copy).

I create a baseline using the reference copy.

I enable the working copy for api analysis.

And I immediately get an error stating:-

"The minor version should be incremented in version 1.0.0.qualifier, since
new APIs have been added since version 1.0.0.qualifier."

But I havent yet changed the plugin at all.

I would not expect this sort of error to appear until I make the first
change. Is this an incorrect expectation? If so, why?

Mnay thanks
_Paul

Re: PDE API Tooling [message #65715 is a reply to message #65693]

Thu, 25 June 2009 12:35

Eclipse User

Paul Warren wrote:
> I would not expect this sort of error to appear until I make the first
> change. Is this an incorrect expectation? If so, why?

If you hover over the quickfix, it generally tells you what APIs were
added. If there's nothing there, it sounds like a bug.

One thing you can do quickly is to use the new 'Compare With' option in
PDE API Tools... check this blog to see how to use it:
http://eclipsesource.com/blogs/2009/04/28/comparing-api-base lines/

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: PDE API Tooling [message #66243 is a reply to message #65715]

Tue, 30 June 2009 04:38

Eclipse User

Hi Chris,

If I hover over the quick fix it tells me:-

List of compatible changes:
- The type api.ITest has been added to test_1.0.0

So it definitely thinks something has changed but I believe it may be
incorrect because the baseline version of the project has the exact same API
too. I exported the project right before the "compare with" and I used this
exported version of the project as the baseline - so the two are identical.

Am I misunderstanding somehting or do you think this is a bug?

Cheers
_Paul

"Chris Aniszczyk" <zx@eclipsesource.com> wrote in message
news:h208vp$6l4$1@build.eclipse.org...
> Paul Warren wrote:
>> I would not expect this sort of error to appear until I make the first
>> change. Is this an incorrect expectation? If so, why?
>
> If you hover over the quickfix, it generally tells you what APIs were
> added. If there's nothing there, it sounds like a bug.
>
> One thing you can do quickly is to use the new 'Compare With' option in
> PDE API Tools... check this blog to see how to use it:
> http://eclipsesource.com/blogs/2009/04/28/comparing-api-base lines/
>
> Cheers,
>
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
>

Re: PDE API Tooling [message #66336 is a reply to message #66243]

Tue, 30 June 2009 10:09

Eclipse User

Paul Warren wrote:
> Hi Chris,
>
> If I hover over the quick fix it tells me:-
>
> List of compatible changes:
> - The type api.ITest has been added to test_1.0.0
>
> So it definitely thinks something has changed but I believe it may be
> incorrect because the baseline version of the project has the exact same API
> too. I exported the project right before the "compare with" and I used this
> exported version of the project as the baseline - so the two are identical.
>
> Am I misunderstanding somehting or do you think this is a bug?

Are you sure that you're using that project as the baseline?

Are you regenerating the baseline when you export with that new bundle
in it?

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: PDE API Tooling [message #66363 is a reply to message #66336]

Tue, 30 June 2009 18:02

Eclipse User

I am positive I am using the very same project as the baseline. Checked it
a few times.

I am not sure if I am regenerating the baseline though. Are you saying I
should or I shouldnt be doing that?

What I do know is that when I set a newly exported project as the new
baseline it prompts me to recompile the code, which I do.

So what I am doing is this:-

1. Create plugin project and mark it for api analysis
2. Create interface in some package, add some simple methods to it and
export the package
3. Export whole project to file system
4. Back in the workspace set newly exported project as the project's
baseline (either compare with... or via windows preferences) which prompts
me to recompile code - I choose yes.

And I alwyas get the aforementioned error.

This is the same basic process that I would hope to follow (on a much larger
scale) for our eclipse-based products prior to a release. Checkout last
release code and use it as a baseline for current codeline. But I dont
want it reporting false positives.

Many thanks
_Paul

"Chris Aniszczyk" <zx@eclipsesource.com> wrote in message
news:h2d6b8$tri$1@build.eclipse.org...
> Paul Warren wrote:
>> Hi Chris,
>>
>> If I hover over the quick fix it tells me:-
>>
>> List of compatible changes:
>> - The type api.ITest has been added to test_1.0.0
>>
>> So it definitely thinks something has changed but I believe it may be
>> incorrect because the baseline version of the project has the exact same
>> API too. I exported the project right before the "compare with" and I
>> used this exported version of the project as the baseline - so the two
>> are identical.
>>
>> Am I misunderstanding somehting or do you think this is a bug?
>
> Are you sure that you're using that project as the baseline?
>
> Are you regenerating the baseline when you export with that new bundle in
> it?
>
> Cheers,
>
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: PDE API Tooling [message #598600 is a reply to message #65693]

Thu, 25 June 2009 12:35

Eclipse User