| RAD 6.0 (eclipse 3.0) with / AJDT 1.2.1 & AspectJ 1.5.1 [message #63945] |
Wed, 05 April 2006 18:41  |
Eclipse User |
|
|
|
Originally posted by: matthew.smith.valtech.com
Hello, I'm trying to get AJDT 1.2.1 to build with an updated copy of the
AspectJ compiler (1.5.1) in order to take advantage of the memory savings
the new version of the compiler offers. I'm using Rational Application
Developer 6.0 (eclipse 3.0x). One of my co-workers (B Schuchert) posted
a description of our development group/project size a few days ago.
Disclaimer: I'm never developed an eclipse plug-in before, so forgive me
if my questions have obvious answers.
To start, I checked out the ajdt 1.2 branch, and pointed the
aspectj.lib.dir ant var at an aspect 1.5.1 lib directory.
One of the build files refers to a hard path (the build.xml in
org.aspectj.ajde has a path
" ${aspectj.lib.dir}/../../ide/eclipse/org.aspectj.ajde.source /src/jdtcore-for-aspectj-src.zip ").
Should I have checked out something in addition to the ajdt projects
(like the aspectj tree in cvs) mentioned in the ajdt faq entry?
I ran the "plugin jars" task to create a new ajde.jar and I fixed a
compilation error with some new methods added to AjBuilder.java. Now,
the error I am getting is an IDE pop-up complaining that the version
declared in my aspectjrt.jar does not match what's expected. It expects
1.5.0, but finds 1.5.1. The only place I can find a reference to the
number 1.5.0 is the ajdt plugin I'm currently using. So that brings up
the question.... am I in a chicken-and-the-egg scenario? Can I upgrade
the compiler and test the upgrade inside a workspace that is using an old
ajdt/aj version?
Many CoreTests are failing.
Should I be running the coretests is a seperate workspace I kick off? Or
should they be able to work in my current workspace?
It wasn't entirely clear to me from the faq instructions (which did
mention kicking off a seperate workspace -- but that workspace would not
have the .test projects in it), right?
Appreciate any help you can provide.
|
|
|
| Re: RAD 6.0 (eclipse 3.0) with / AJDT 1.2.1 & AspectJ 1.5.1 [message #63970 is a reply to message #63945] |
Thu, 06 April 2006 02:16  |
| Eclipse User |
|
|
|
Hi Matthew,
It's great that you're getting the source and getting involved! We are
committed to creating an AJDT 1.2.2 containing AspectJ 1.5.1 (we're fairly
confident it will be possible!), just as soon as AJDT 1.3.1 is done (we
nearly made it yesterday, but a last minute problem arose). So you might
want to wait for that - we'll put out dev builds for you to try as soon as
we have something. But I've included some quick answers below in case you
want to continue your plug-in development adventure :)
Matthew Smith wrote:
> One of the build files refers to a hard path (the build.xml in
> org.aspectj.ajde has a path
>
" ${aspectj.lib.dir}/../../ide/eclipse/org.aspectj.ajde.source /src/jdtcore-for-aspectj-src.zip ").
> Should I have checked out something in addition to the ajdt projects
> (like the aspectj tree in cvs) mentioned in the ajdt faq entry?
No, you don't need the aspectj tree, just the org.aspectj* plugins from
the ajdt tree.
> I ran the "plugin jars" task to create a new ajde.jar and I fixed a
> compilation error with some new methods added to AjBuilder.java.
I believe there were some other ajdt changes required for aspectj versions
since 1.5.0 - we'll have to check back in CVS.
> Now,
> the error I am getting is an IDE pop-up complaining that the version
> declared in my aspectjrt.jar does not match what's expected. It expects
> 1.5.0, but finds 1.5.1. The only place I can find a reference to the
> number 1.5.0 is the ajdt plugin I'm currently using. So that brings up
> the question.... am I in a chicken-and-the-egg scenario? Can I upgrade
> the compiler and test the upgrade inside a workspace that is using an old
> ajdt/aj version?
Yes, this issue is specific to the case of using AspectJ to build AJDT.
The short answer should be to temporarily close the org.aspect.runtime
plug-in in your workspace.
> Many CoreTests are failing.
> Should I be running the coretests is a seperate workspace I kick off? Or
> should they be able to work in my current workspace?
> It wasn't entirely clear to me from the faq instructions (which did
> mention kicking off a seperate workspace -- but that workspace would not
> have the .test projects in it), right?
You need to run the ajdt core (and ui) tests via Run As > JUnit Plugin
test.
This launch config simulates normal workbench startup so the test plug-ins
should appear to be installed in the launched environment. Then the test
harness creates the testcase projects by copying from under the workspace
folder in the test plug-in projects.
Regards,
Matt.
|
|
|
| Re: RAD 6.0 (eclipse 3.0) with / AJDT 1.2.1 & AspectJ 1.5.1 [message #593174 is a reply to message #63945] |
Thu, 06 April 2006 02:16 |
| Eclipse User |
|
|
|
Hi Matthew,
It's great that you're getting the source and getting involved! We are
committed to creating an AJDT 1.2.2 containing AspectJ 1.5.1 (we're fairly
confident it will be possible!), just as soon as AJDT 1.3.1 is done (we
nearly made it yesterday, but a last minute problem arose). So you might
want to wait for that - we'll put out dev builds for you to try as soon as
we have something. But I've included some quick answers below in case you
want to continue your plug-in development adventure :)
Matthew Smith wrote:
> One of the build files refers to a hard path (the build.xml in
> org.aspectj.ajde has a path
>
" ${aspectj.lib.dir}/../../ide/eclipse/org.aspectj.ajde.source /src/jdtcore-for-aspectj-src.zip ").
> Should I have checked out something in addition to the ajdt projects
> (like the aspectj tree in cvs) mentioned in the ajdt faq entry?
No, you don't need the aspectj tree, just the org.aspectj* plugins from
the ajdt tree.
> I ran the "plugin jars" task to create a new ajde.jar and I fixed a
> compilation error with some new methods added to AjBuilder.java.
I believe there were some other ajdt changes required for aspectj versions
since 1.5.0 - we'll have to check back in CVS.
> Now,
> the error I am getting is an IDE pop-up complaining that the version
> declared in my aspectjrt.jar does not match what's expected. It expects
> 1.5.0, but finds 1.5.1. The only place I can find a reference to the
> number 1.5.0 is the ajdt plugin I'm currently using. So that brings up
> the question.... am I in a chicken-and-the-egg scenario? Can I upgrade
> the compiler and test the upgrade inside a workspace that is using an old
> ajdt/aj version?
Yes, this issue is specific to the case of using AspectJ to build AJDT.
The short answer should be to temporarily close the org.aspect.runtime
plug-in in your workspace.
> Many CoreTests are failing.
> Should I be running the coretests is a seperate workspace I kick off? Or
> should they be able to work in my current workspace?
> It wasn't entirely clear to me from the faq instructions (which did
> mention kicking off a seperate workspace -- but that workspace would not
> have the .test projects in it), right?
You need to run the ajdt core (and ui) tests via Run As > JUnit Plugin
test.
This launch config simulates normal workbench startup so the test plug-ins
should appear to be installed in the launched environment. Then the test
harness creates the testcase projects by copying from under the workspace
folder in the test plug-in projects.
Regards,
Matt.
|
|
|
Powered by
FUDForum. Page generated in 0.02933 seconds
Home