- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
Re: Scala Eclipse Plugin Conflicts with AJDT
Tue, 2009-02-03, 19:35
I start out as a normal java project then I add the AJDT nature then I add the Dynamic Web Module facet. Step 6 involves nothing more than simply installing the plugin. I don't even add the Scala nature to the project nor do I create any scala files. In order to get AJDT working again I have to uninstall the Scala plugin and create a new workspace.
It might be that the AJDT plugin is trying to weave the bytecode of the plugin itself, but I can't think of a reason why it would do that. It would seem more plausible if AspectJ was trying to weave the Scala libs, but the libs arent even part of the project since the Scala nature has not been added to it.
It is interesting that changing the java compliance version to 1.5 fixes the weaving, especially since the Scala nature is not even in the project and it works at 1.6 compliance level without the Scala plugin installed.
On Tue, Feb 3, 2009 at 2:56 AM, Miles Sabin <miles [at] milessabin [dot] com> wrote:
On Tue, Feb 3, 2009 at 5:09 AM, Gordon Leland Hempton
<ghempton [at] gmail [dot] com> wrote:
> After lots of testing I have reduced it to a very simple case
> 1) Install a fresh copy of eclipse 3.4.1
> 2) Install latest AJDT 1.6.3
> 3) Install WTP and enable the Dynamic Web Module facet
> 4) Create a single java class
> 5) Create an aspect with a pointcut on the class from step 3
> At this point AJDT is working properly and the class is being correctly
> 6) Install Scala Plugin 2.6.3final
> After step 6 is performed AJDT is no longer working and nothing is being
> woven. The error message from my previous emails usually shows up in the
> logs, but my gut intuition is that it is not the cause of the problem.
> One thing that is interesting is that if I skip step 5, the class will be
> correctly woven. Has anyone else noticed a conflict between Scala and WTP?
Is it possible that aspectj is attempting to load-time weave Scala
bytecode (ie. of the plugin itself) and failing? As I said earlier,
aspectj chokes on at least some scalac generated bytecode.
Also it's not clear to me what kinds of projects you have in your
workspace at step (6) above ... do you have a Scala project? Are you
attempting to advise Java and/or Scala which is part of a Scala
tel: +44 (0)1273 720 779
mobile: +44 (0)7813 944 528