Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » eclipse3M6 and AspectJ
eclipse3M6 and AspectJ [message #29497] Mon, 26 January 2004 08:03 Go to next message
Eclipse UserFriend
Originally posted by: richard.fairall.nexus-ag.com

It's very disappointing that an organisation such as eclipse.org
creates milestone builds such as 3M6 that contain a pile of small
bug-fixes and in the process creates bigger undocumented bugs.
Why dont they reply to the problems posted on this forum?

It's understandable that a Milestone release has problems but
why can't these problems be documented?
Just a few lines in 3M5 and 3M6 release notes saying something like
" AJDT entire business does not work anymore! sorry for the inconvenience!"
It's not good for the industry when countless eclipse users spend hours
discovering the latest cockups and omissions.
Just a few honest lines out of courtesy to the users who have invested
time in developing projects with aspectj would be so easy for them to
include.
By the way, we were advised to use 3M6 in order to run Omondo Enterprise,
so
it's a dilemma for us now.
How about a quick fix eclipse people ? 3M7 next week? Great. Thanks in
advance.
Richard F.
Re: eclipse3M6 and AspectJ [message #29532 is a reply to message #29497] Mon, 26 January 2004 15:55 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: hcs33.egon.gyaloglo.hu

Hi,

I understand that you are disappointed in some ways (because you cannot use
AJDT in 3.0M6), but...

- In the Eclipse 3.0 development stream it is *expected* to have api changes
compared to Eclipse 2.1. See the Eclipse 3.0 plan for more details
( http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_0.html).
- Most likely AJDT does not work for 3.0M5 and M6 because between 3.0M4 and
3.0M5 was a large plugin-restructuring introducing RCP (Rich Client
Platform). This change was clearly introduced in the "New and Noteworthy in
Eclipse 3.0M5" document
( http://download2.eclipse.org/downloads/drops/S-3.0M5-2003112 11210/eclipse-n
ews-all-M5.html). See "Rich Client Platform UI" and "Eclipse 3.0 Porting
Guide" sections. If this is the case then it is not an Eclipse bug.
- If you read the "New and noteworthy in Eclipse 3.0M6" document
( http://download2.eclipse.org/downloads/drops/S-3.0M6-2003121 82000/eclipse-n
ews-all-M6.html) you see that there are tons of new features in this release
(not only a pile of small bug fixes).
- From Eclipse 3.0M5 there is a well-written Porting Guide (See
Help-->Platform Plugin Developer Guide-->Porting Guide).
- I think it is a good thing from Eclipse people to provide public access to
pre-release versions of 3.0 - because plugin writers has few additional
months to update their plugins to work with the final 3.0. If you do not
want to get bad expectations than you have to use the latest production
release - Eclipse 2.1.x.
- I think AJDT is - in some ways - only a set of plugins in top of Eclipse
Platform and JDT, so AJDT developers must port this excellent feature to the
new 3.0 api (and they are doing that - see the sreenshots of the 'Lancaster'
release - they are very promising).

So, in my opinion: Eclipse 3.0 is an ongoing development which becomes
better and better and so does AJDT. I hope that the new AJDT release will
become downloadable within a couple of weeks so you can use it with Eclipse
3.0M6 or later versions.

Regards,
Csaba

"Richard Fairall" <richard.fairall@nexus-ag.com> wrote in message
news:bv2hl8$tl$1@eclipse.org...
> It's very disappointing that an organisation such as eclipse.org
> creates milestone builds such as 3M6 that contain a pile of small
> bug-fixes and in the process creates bigger undocumented bugs.
> Why dont they reply to the problems posted on this forum?
>
> It's understandable that a Milestone release has problems but
> why can't these problems be documented?
> Just a few lines in 3M5 and 3M6 release notes saying something like
> " AJDT entire business does not work anymore! sorry for the
inconvenience!"
> It's not good for the industry when countless eclipse users spend hours
> discovering the latest cockups and omissions.
> Just a few honest lines out of courtesy to the users who have invested
> time in developing projects with aspectj would be so easy for them to
> include.
> By the way, we were advised to use 3M6 in order to run Omondo Enterprise,
> so
> it's a dilemma for us now.
> How about a quick fix eclipse people ? 3M7 next week? Great. Thanks in
> advance.
> Richard F.
>
>
>
>
Re: eclipse3M6 and AspectJ [message #29559 is a reply to message #29532] Tue, 27 January 2004 07:16 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richard.fairall.nexus-ag.com

Thanks a lot for the reply.
It's a big big job developing eclipse,
and a big job that we're developing on it.
Dont forget those nice helpful release notes in 3M7!
One text line of info probably saves 1000s of hours out here
for us all.

Rich
Re: eclipse3M6 and AspectJ [message #30584 is a reply to message #29559] Mon, 09 February 2004 14:34 Go to previous message
Eclipse UserFriend
Originally posted by: clemas.uk.ibm.com

Hi,

I'd just like to add that AJDT is a little more awkward than many plugins in
keeping up with Eclipse releases because we use a few internal APIs in
Eclipse which can 'move' at any moment. This is due to the lack of
extension points where we need them. With our new Lancaster codebase we can
hopefully become more robust against changes due to our new architecture.

Andy.

Andy Clement
AJDT/AspectJ development
Re: eclipse3M6 and AspectJ [message #574200 is a reply to message #29497] Mon, 26 January 2004 15:55 Go to previous message
Eclipse UserFriend
Originally posted by: hcs33.egon.gyaloglo.hu

Hi,

I understand that you are disappointed in some ways (because you cannot use
AJDT in 3.0M6), but...

- In the Eclipse 3.0 development stream it is *expected* to have api changes
compared to Eclipse 2.1. See the Eclipse 3.0 plan for more details
( http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_0.html).
- Most likely AJDT does not work for 3.0M5 and M6 because between 3.0M4 and
3.0M5 was a large plugin-restructuring introducing RCP (Rich Client
Platform). This change was clearly introduced in the "New and Noteworthy in
Eclipse 3.0M5" document
( http://download2.eclipse.org/downloads/drops/S-3.0M5-2003112 11210/eclipse-n
ews-all-M5.html). See "Rich Client Platform UI" and "Eclipse 3.0 Porting
Guide" sections. If this is the case then it is not an Eclipse bug.
- If you read the "New and noteworthy in Eclipse 3.0M6" document
( http://download2.eclipse.org/downloads/drops/S-3.0M6-2003121 82000/eclipse-n
ews-all-M6.html) you see that there are tons of new features in this release
(not only a pile of small bug fixes).
- From Eclipse 3.0M5 there is a well-written Porting Guide (See
Help-->Platform Plugin Developer Guide-->Porting Guide).
- I think it is a good thing from Eclipse people to provide public access to
pre-release versions of 3.0 - because plugin writers has few additional
months to update their plugins to work with the final 3.0. If you do not
want to get bad expectations than you have to use the latest production
release - Eclipse 2.1.x.
- I think AJDT is - in some ways - only a set of plugins in top of Eclipse
Platform and JDT, so AJDT developers must port this excellent feature to the
new 3.0 api (and they are doing that - see the sreenshots of the 'Lancaster'
release - they are very promising).

So, in my opinion: Eclipse 3.0 is an ongoing development which becomes
better and better and so does AJDT. I hope that the new AJDT release will
become downloadable within a couple of weeks so you can use it with Eclipse
3.0M6 or later versions.

Regards,
Csaba

"Richard Fairall" <richard.fairall@nexus-ag.com> wrote in message
news:bv2hl8$tl$1@eclipse.org...
> It's very disappointing that an organisation such as eclipse.org
> creates milestone builds such as 3M6 that contain a pile of small
> bug-fixes and in the process creates bigger undocumented bugs.
> Why dont they reply to the problems posted on this forum?
>
> It's understandable that a Milestone release has problems but
> why can't these problems be documented?
> Just a few lines in 3M5 and 3M6 release notes saying something like
> " AJDT entire business does not work anymore! sorry for the
inconvenience!"
> It's not good for the industry when countless eclipse users spend hours
> discovering the latest cockups and omissions.
> Just a few honest lines out of courtesy to the users who have invested
> time in developing projects with aspectj would be so easy for them to
> include.
> By the way, we were advised to use 3M6 in order to run Omondo Enterprise,
> so
> it's a dilemma for us now.
> How about a quick fix eclipse people ? 3M7 next week? Great. Thanks in
> advance.
> Richard F.
>
>
>
>
Re: eclipse3M6 and AspectJ [message #574253 is a reply to message #29532] Tue, 27 January 2004 07:16 Go to previous message
Eclipse UserFriend
Originally posted by: richard.fairall.nexus-ag.com

Thanks a lot for the reply.
It's a big big job developing eclipse,
and a big job that we're developing on it.
Dont forget those nice helpful release notes in 3M7!
One text line of info probably saves 1000s of hours out here
for us all.

Rich
Re: eclipse3M6 and AspectJ [message #574889 is a reply to message #29559] Mon, 09 February 2004 14:34 Go to previous message
Andrew Clement is currently offline Andrew ClementFriend
Messages: 162
Registered: July 2009
Senior Member
Hi,

I'd just like to add that AJDT is a little more awkward than many plugins in
keeping up with Eclipse releases because we use a few internal APIs in
Eclipse which can 'move' at any moment. This is due to the lack of
extension points where we need them. With our new Lancaster codebase we can
hopefully become more robust against changes due to our new architecture.

Andy.

Andy Clement
AJDT/AspectJ development
Previous Topic:Lancaster?
Next Topic:-> A question about Lancaster
Goto Forum:
  


Current Time: Tue Mar 19 03:24:02 GMT 2024

Powered by FUDForum. Page generated in 0.01789 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top