[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] AJDT Compiles
|
I might have stumbled upon a possible clue to this (or situations like
it). I was working with a project that generated an outjar, which a second
project then used on its aspectpath (and the jar was also in its java
build path). I hit a scenario whereby compiling the library project
appeared to be successful, *BUT*, the new classes I had added did not make
it into the jar. After discovering this, I tried to delete the jar to
force a recreate - *but Eclipse was unable to delete it*. This implies to
me that there is a nasty silent failure mode whereby somewhere in eclipse
(or in a launched program, but I didn't have one in this scenario)
something has a handle on the jar file, and we therefore fail to write to
it but don't detect that fact. This would explain both the behaviour that
I saw and that Ron is seeing. The first thing we should do is detect this
: we should try to delete a jar before writing it, and if wef ind that we
can't, we should fail with a good error message. The second thing we
should do is try and figure out who's got a handle and why so that we can
succeed a lot more often....
-- Adrian
Adrian_Colyer@xxxxxxxxxx
"DiFrango, Ron" <ron.difrango@xxxxxxxxxxxxxx>
Sent by: aspectj-users-admin@xxxxxxxxxxx
12/08/2004 15:26
Please respond to
aspectj-users@xxxxxxxxxxx
To
"'aspectj-users@xxxxxxxxxxx'" <aspectj-users@xxxxxxxxxxx>
cc
Subject
RE: [aspectj-users] AJDT Compiles
Matt,
Here is a quick description of how I have MyEclipse setup:
1) Enterprise Application Project [MyEclipse]
2) Web Project, but no source code [MyEclipse]
3) aspecjt project
The aspectj project contains all my source code and it compiles the code
into a linked directory which ends up in the Web Project's WEB-INF/classes
directory. As I mentioned below, in addition to my source files, I have
an
InJar that I am weaving some code into along with my source code.
It really seems to be intermittent. The concrete scenario I can come up
is
as follows:
1) Compile and weave my source project
2) Introduce a new aspect that only affects my code.
3) Compile and weave again
Deploy my code to my app server [Jboss] and when I do the new code breaks
because it is not woven correctly.
Thanks,
Ron
-----Original Message-----
From: Matt Chapman [mailto:MCHAPMAN@xxxxxxxxxx]
Sent: Thursday, August 12, 2004 5:25 AM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] AJDT Compiles
Hi,
We have done some initial testing of AJDT and MyEclipse together, although
we haven't yet hit the problems noted here. We hope to do some more
testing in the future, particularly on their final release. If you think
we can do something on the AJDT side to improve the situation, please
raise an AJDT bug. Being able to provide a project setup to recreate the
issue would obviously be a great help (even if it requires MyEclipse).
Regards,
Matt.
AJDT Development
aspectj-users-admin@xxxxxxxxxxx wrote on 11/08/2004 18:39:47:
> >
> > AJDT: 1.1.11
> > Eclipse 3.0
> > MyEclipse ID 3.8.0 Beta 2
> >
> > I have a Aspectj project setup with the output directory as a link
> > to
> > the
> > classes directory in my Web project. In the Aspectj project, I have
> > source
> > files and in addition to that, I have aspectj InPath definition to
> > perform
> > final weaving into an external jar along with my source files. The
> > behavior
> > I am seeing is that on some if I add in a new Aspect, it does not
> > always get
> > compiled into the code. The only way for me to guarantee that this
> > occurs
> > is that I perform a "Clean" then build then I am always sure to get
> > the code
> > compiled.
>
> Same setup here, on Linux and on MacOS X. I have talked to the
> myeclipseide guys and they are aware of a bug where the myeclipseide
> build system (JSP Compiler) and the AspectJ compiler can crash eclipse.
> You can search their support forums to get more informations. And they
> have fixed this issue for 3.0 final.
>
> I can not confirm the behaviour you are reporting. But I can confirm,
> that this is true for properties files. I have properties files on the
> build path and they do not get copied over to the classes folder if I
> change them. I have to clean the project ...
>
> I I then remove the aspectj nature, everything is ok. But what I can
> report is, that the behaviour on MacOS X and Linux is different. I had
> problems on MacOS X where the same project did not make troubles on
> Linux. Troubles means, Exceptions while building the project.
>
> Probably 3.0 final will fix some problem, while some problems are
> related to the aspectj compiler (properties files) - but I am not sure,
> have not proven that in a simple aspectj project without myecliseIDE.
>
>
> Regards,
>
> Cyrill
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
**************************************************************************
The information transmitted herewith is sensitive information intended
only
for use by the individual or entity to which it is addressed. If the
reader
of this message is not the intended recipient, you are hereby notified
that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users
