Eclipse Community Forums: Plugin Development Environment (PDE) » [API Tools] API Tools for plain Java (not OSGi Bundles)

Home » Eclipse Projects » Plugin Development Environment (PDE) » [API Tools] API Tools for plain Java (not OSGi Bundles)

Show: Today's Messages :: Show Polls :: Message Navigator

[API Tools] API Tools for plain Java (not OSGi Bundles) [message #68929]

Thu, 23 July 2009 13:12

Jan Lohre

Messages: 8
Registered: July 2009

Junior Member

Hi,

we are starting to use the API tool for our internal processes.
Currently we have written applications to create a baseline for a simple
jar file and to compare a jar file with such a baseline.

In the long run we would like to support the developer in his regular
development environment (aka Eclipse). So I would like to ask for the
plans for 3.6

I have seen http://wiki.eclipse.org/PDE/Plan/3.6#API_Tools and
255068: Check API compatibility in Java projects with PDE API Tools
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255068

So it seems you are aware of the topic but have no concrete plans ;-)

Kind regards,
Jan

Report message to a moderator

Re: [API Tools] API Tools for plain Java (not OSGi Bundles) [message #68993 is a reply to message #68929]

Thu, 23 July 2009 22:24

Chris Aniszczyk

Messages: 674
Registered: July 2009

Senior Member

Jan Lohre wrote:
> Hi,
>
> we are starting to use the API tool for our internal processes.
> Currently we have written applications to create a baseline for a simple
> jar file and to compare a jar file with such a baseline.
>
> In the long run we would like to support the developer in his regular
> development environment (aka Eclipse). So I would like to ask for the
> plans for 3.6
>
> I have seen http://wiki.eclipse.org/PDE/Plan/3.6#API_Tools and
> 255068: Check API compatibility in Java projects with PDE API Tools
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=255068
>
> So it seems you are aware of the topic but have no concrete plans ;-)

It's still early in the planning cycle. The best bet is to stay on the bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=255068

I would also make known any requirement on the bug too.

The big problem with normal Java projects is that they have no way to
encode visibility like we have with OSGi artifacts. In the OSGi
MANIFEST.MF, you can specify what is visible via Export-Package and also
assign version numbers. How do you do something like that in normal Java
projects?

As a workaround, you can convert your Java projects to plug-in
projects... they should still work depending on your setup.

Cheers,

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

Report message to a moderator

Re: [API Tools] API Tools for plain Java (not OSGi Bundles) [message #69013 is a reply to message #68993]

Fri, 24 July 2009 09:01

Jan Lohre

Messages: 8
Registered: July 2009

Junior Member

Chris Aniszczyk schrieb:
> Jan Lohre wrote:
>> Hi,
>>
>> we are starting to use the API tool for our internal processes.
>> Currently we have written applications to create a baseline for a
>> simple jar file and to compare a jar file with such a baseline.
>>
>> In the long run we would like to support the developer in his regular
>> development environment (aka Eclipse). So I would like to ask for the
>> plans for 3.6
>>
>> I have seen http://wiki.eclipse.org/PDE/Plan/3.6#API_Tools and
>> 255068: Check API compatibility in Java projects with PDE API Tools
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=255068
>>
>> So it seems you are aware of the topic but have no concrete plans ;-)
>
> It's still early in the planning cycle. The best bet is to stay on the bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=255068
>
> I would also make known any requirement on the bug too.
>
> The big problem with normal Java projects is that they have no way to
> encode visibility like we have with OSGi artifacts. In the OSGi
> MANIFEST.MF, you can specify what is visible via Export-Package and also
> assign version numbers. How do you do something like that in normal Java
> projects?
>
> As a workaround, you can convert your Java projects to plug-in
> projects... they should still work depending on your setup.
>
> Cheers,
>
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Hi Chris,

we have a build system (proprietary) with it's own component model. So
what I would really like to see would be a way to plug in a custom
IApiComponent implementation. But that goes (far?) beyond the scope of
the existing bug report.

Should I still comment on 255068 or should I maybe raise a separate
enhancement request (although then both should get some kind of link)

Kind regards,
Jan

Report message to a moderator

Re: [API Tools] API Tools for plain Java (not OSGi Bundles) [message #69034 is a reply to message #69013]

Fri, 24 July 2009 14:33

Chris Aniszczyk

Messages: 674
Registered: July 2009

Senior Member

Jan Lohre wrote:
> we have a build system (proprietary) with it's own component model. So
> what I would really like to see would be a way to plug in a custom
> IApiComponent implementation. But that goes (far?) beyond the scope of
> the existing bug report

Wow, that's interesting! Most people generally use Maven or OSGi (PDE)

I could understand the desire to create something new though ;)

> Should I still comment on 255068 or should I maybe raise a separate
> enhancement request (although then both should get some kind of link)

I think you should comment on that bug and point to the newly created
enhancement request. Patches make everything go faster too ;)

Cheers,

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

Report message to a moderator