Home » Language IDEs » AspectJ » Question to AJDT developers: reusing JTD plugin.
|
| Re: Question to AJDT developers: reusing JTD plugin. [message #54600 is a reply to message #54436] |
Wed, 06 July 2005 11:20   |
Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
Hi,
It's helpful to consider the Core and UI parts of JDT separately. JDT-Core
is essentially the Java compiler, and JDT-UI is the user interface support
for working with Java in Eclipse. The AspectJ compiler is the equivalent
of JDT-Core, and that does duplicate the JDT-Core code and extend it as
required. The changes are synchronised with the latest JDT-Core sources as
and when required. Some of the extensions are now implemented with
aspects, which will help the move up to future JDT-Core versions. The AJDT
plugin is the equivalent of JDT-UI, and that does *not* copy and extend
the JDT-UI code. We did try that but it proved difficult managing the
resultant contributions to Eclipse - e.g. you could end up with a project
containing two different instances of Java classes, which weren't
compatible with each. So the current approach in AJDT is to extend the
existing JDT-UI functionality whenever we can. In a few places where this
isn't possible, we do copy and extend a select few classes from JDT-UI
(and also PDE-UI to add support for AspectJ-enabled plugin projects). See
also the LDT: Language Development Toolkit (website and newsgroup), which
has been proposed as a technology project to look at generalising JDT to
support other languages.
Regards,
Matt.
On Tue, 05 Jul 2005 16:21:13 +0400, Sergey Gomanyuk wrote:
> We are planning to implement eclipse plugin that supports our extension
> of java language. So Id like to ask you as people who have done that
> job already.
>
>
>
> I have discovered that JDT plugin API can help to manage java project
> and java code but it is hard to reuse it to implement support of java
> language extension. But it is our goal! The one way to achieve it is
> copy all JDT source code to your plugin and modify it as you wish. Seems
> AJDT plugin uses this way. But there is a problem to be up-to-date with
> JDT plugin source code, its new features and bug fixes.
>
>
>
> Since AspectJ is Eclipse Technology Project, I suppose, developers of
> JDT plugin have plans to make their plugin more reusable. Is it true?
> Can I read some forums concerned to this problem? May be something was
> already done?
--
Matt Chapman
AJDT Development, http://www.eclipse.org/ajdt
|
|
|
| Re: Question to AJDT developers: reusing JTD plugin. [message #54626 is a reply to message #54600] |
Thu, 07 July 2005 09:17 |
| Eclipse User |
|
|
|
Originally posted by: sergg.kazbek.ispras.ru
Thank you for your comment, it's helpful.
It's a pity that developers of JDT plugin made it so non extendable. For
example, NetBeans plutform Java plugin is more flexible and we've
succesfully reused the big part of its classes just by extending them (no
code copy) and integrated in NetBeans IDE.
--
Sergey Gomanyuk,
ISP RAS,
junior research assistant,
e-mail: sergg@ispras.ru
phone: +7 (095) 912-5317 (4428 additional)
cell: +7 (926) 522-4506
"Matt Chapman" <mchapman@uk.ibm.com> wrote in message
news:pan.2005.07.06.15.20.20.2246@uk.ibm.com...
> Hi,
>
> It's helpful to consider the Core and UI parts of JDT separately. JDT-Core
> is essentially the Java compiler, and JDT-UI is the user interface support
> for working with Java in Eclipse. The AspectJ compiler is the equivalent
> of JDT-Core, and that does duplicate the JDT-Core code and extend it as
> required. The changes are synchronised with the latest JDT-Core sources as
> and when required. Some of the extensions are now implemented with
> aspects, which will help the move up to future JDT-Core versions. The AJDT
> plugin is the equivalent of JDT-UI, and that does *not* copy and extend
> the JDT-UI code. We did try that but it proved difficult managing the
> resultant contributions to Eclipse - e.g. you could end up with a project
> containing two different instances of Java classes, which weren't
> compatible with each. So the current approach in AJDT is to extend the
> existing JDT-UI functionality whenever we can. In a few places where this
> isn't possible, we do copy and extend a select few classes from JDT-UI
> (and also PDE-UI to add support for AspectJ-enabled plugin projects). See
> also the LDT: Language Development Toolkit (website and newsgroup), which
> has been proposed as a technology project to look at generalising JDT to
> support other languages.
>
> Regards,
>
> Matt.
>
> On Tue, 05 Jul 2005 16:21:13 +0400, Sergey Gomanyuk wrote:
>
>> We are planning to implement eclipse plugin that supports our extension
>> of java language. So I'd like to ask you as people who have done that
>> job already.
>>
>>
>>
>> I have discovered that JDT plugin API can help to manage java project
>> and java code but it is hard to reuse it to implement support of java
>> language extension. But it is our goal! The one way to achieve it is
>> copy all JDT source code to your plugin and modify it as you wish. Seems
>> AJDT plugin uses this way. But there is a problem to be up-to-date with
>> JDT plugin source code, its new features and bug fixes.
>>
>>
>>
>> Since AspectJ is Eclipse Technology Project, I suppose, developers of
>> JDT plugin have plans to make their plugin more reusable. Is it true?
>> Can I read some forums concerned to this problem? May be something was
>> already done?
>
> --
> Matt Chapman
> AJDT Development, http://www.eclipse.org/ajdt
>
|
|
|
| Re: Question to AJDT developers: reusing JTD plugin. [message #589253 is a reply to message #54436] |
Wed, 06 July 2005 11:20 |
| Eclipse User |
|
|
|
Hi,
It's helpful to consider the Core and UI parts of JDT separately. JDT-Core
is essentially the Java compiler, and JDT-UI is the user interface support
for working with Java in Eclipse. The AspectJ compiler is the equivalent
of JDT-Core, and that does duplicate the JDT-Core code and extend it as
required. The changes are synchronised with the latest JDT-Core sources as
and when required. Some of the extensions are now implemented with
aspects, which will help the move up to future JDT-Core versions. The AJDT
plugin is the equivalent of JDT-UI, and that does *not* copy and extend
the JDT-UI code. We did try that but it proved difficult managing the
resultant contributions to Eclipse - e.g. you could end up with a project
containing two different instances of Java classes, which weren't
compatible with each. So the current approach in AJDT is to extend the
existing JDT-UI functionality whenever we can. In a few places where this
isn't possible, we do copy and extend a select few classes from JDT-UI
(and also PDE-UI to add support for AspectJ-enabled plugin projects). See
also the LDT: Language Development Toolkit (website and newsgroup), which
has been proposed as a technology project to look at generalising JDT to
support other languages.
Regards,
Matt.
On Tue, 05 Jul 2005 16:21:13 +0400, Sergey Gomanyuk wrote:
> We are planning to implement eclipse plugin that supports our extension
> of java language. So Id like to ask you as people who have done that
> job already.
>
>
>
> I have discovered that JDT plugin API can help to manage java project
> and java code but it is hard to reuse it to implement support of java
> language extension. But it is our goal! The one way to achieve it is
> copy all JDT source code to your plugin and modify it as you wish. Seems
> AJDT plugin uses this way. But there is a problem to be up-to-date with
> JDT plugin source code, its new features and bug fixes.
>
>
>
> Since AspectJ is Eclipse Technology Project, I suppose, developers of
> JDT plugin have plans to make their plugin more reusable. Is it true?
> Can I read some forums concerned to this problem? May be something was
> already done?
--
Matt Chapman
AJDT Development, http://www.eclipse.org/ajdt
|
|
|
| Re: Question to AJDT developers: reusing JTD plugin. [message #589271 is a reply to message #54600] |
Thu, 07 July 2005 09:17 |
| Eclipse User |
|
|
|
Thank you for your comment, it's helpful.
It's a pity that developers of JDT plugin made it so non extendable. For
example, NetBeans plutform Java plugin is more flexible and we've
succesfully reused the big part of its classes just by extending them (no
code copy) and integrated in NetBeans IDE.
--
Sergey Gomanyuk,
ISP RAS,
junior research assistant,
e-mail: sergg@ispras.ru
phone: +7 (095) 912-5317 (4428 additional)
cell: +7 (926) 522-4506
"Matt Chapman" <mchapman@uk.ibm.com> wrote in message
news:pan.2005.07.06.15.20.20.2246@uk.ibm.com...
> Hi,
>
> It's helpful to consider the Core and UI parts of JDT separately. JDT-Core
> is essentially the Java compiler, and JDT-UI is the user interface support
> for working with Java in Eclipse. The AspectJ compiler is the equivalent
> of JDT-Core, and that does duplicate the JDT-Core code and extend it as
> required. The changes are synchronised with the latest JDT-Core sources as
> and when required. Some of the extensions are now implemented with
> aspects, which will help the move up to future JDT-Core versions. The AJDT
> plugin is the equivalent of JDT-UI, and that does *not* copy and extend
> the JDT-UI code. We did try that but it proved difficult managing the
> resultant contributions to Eclipse - e.g. you could end up with a project
> containing two different instances of Java classes, which weren't
> compatible with each. So the current approach in AJDT is to extend the
> existing JDT-UI functionality whenever we can. In a few places where this
> isn't possible, we do copy and extend a select few classes from JDT-UI
> (and also PDE-UI to add support for AspectJ-enabled plugin projects). See
> also the LDT: Language Development Toolkit (website and newsgroup), which
> has been proposed as a technology project to look at generalising JDT to
> support other languages.
>
> Regards,
>
> Matt.
>
> On Tue, 05 Jul 2005 16:21:13 +0400, Sergey Gomanyuk wrote:
>
>> We are planning to implement eclipse plugin that supports our extension
>> of java language. So I'd like to ask you as people who have done that
>> job already.
>>
>>
>>
>> I have discovered that JDT plugin API can help to manage java project
>> and java code but it is hard to reuse it to implement support of java
>> language extension. But it is our goal! The one way to achieve it is
>> copy all JDT source code to your plugin and modify it as you wish. Seems
>> AJDT plugin uses this way. But there is a problem to be up-to-date with
>> JDT plugin source code, its new features and bug fixes.
>>
>>
>>
>> Since AspectJ is Eclipse Technology Project, I suppose, developers of
>> JDT plugin have plans to make their plugin more reusable. Is it true?
>> Can I read some forums concerned to this problem? May be something was
>> already done?
>
> --
> Matt Chapman
> AJDT Development, http://www.eclipse.org/ajdt
>
|
|
|
Goto Forum:
Current Time: Tue Nov 04 07:10:15 EST 2025
Powered by FUDForum. Page generated in 0.70600 seconds |
Home