Home » Language IDEs » AspectJ » ajdt 117 on M8 - no colored syntax in editor ?
| ajdt 117 on M8 - no colored syntax in editor ? [message #33781] |
Fri, 16 April 2004 08:43  |
Eclipse User |
|
|
|
Originally posted by: edoardoATenigmatecDOTnet.no.spam
Hallo,
if I use the aj extension for aspect files, the editor shows no color
coding
If I use the java extension (and open them with the AJ editor color
coding works)
known bug/workarounds ?
thanks,
Edoardo
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #33849 is a reply to message #33781] |
Fri, 16 April 2004 08:57  |
| Eclipse User |
|
|
|
Originally posted by: edoardoATenigmatecDOTnet.no.spam
actually, besides coloring, the editor is unusable as keybindings are
all messed up ! I'm using M8 linux gtk on mandrake10 with a UK keyboard.
ok, will use .java ....
Edoardo Comar wrote:
> Hallo,
> if I use the aj extension for aspect files, the editor shows no color
> coding
> If I use the java extension (and open them with the AJ editor color
> coding works)
>
> known bug/workarounds ?
>
> thanks,
> Edoardo
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #33882 is a reply to message #33781] |
Fri, 16 April 2004 08:52 |
| Eclipse User |
|
|
|
Originally posted by: luzius.meisser.uk.ibm.com
Edoardo Comar wrote:
> Hallo,
> if I use the aj extension for aspect files, the editor shows no color
> coding
> If I use the java extension (and open them with the AJ editor color
> coding works)
> known bug/workarounds ?
> thanks,
> Edoardo
Hi Eduardo,
There is indeed no color coding/syntax highlighting when working with .aj
files. To quote Andy Clement:
"Yes, there is no syntax highlighting in .aj files. Because the current
AJDT codebase is not tightly enough integrated with JDT, features that you
are used to from editing standard Java do not work in .aj files. Editing
aspects in .java files will give you syntax highlighting and 1.1.7 even
offers you some degree of code assist."
I know that does not help a lot, but at least you know now why this is the
case.
Regards,
Luzius
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #34011 is a reply to message #33882] |
Fri, 16 April 2004 09:14 |
 Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
Renaming the aspectj files .java makes their handling much easier
indeed! Nevertheless I hope that Andy finds a quick solution to make
the java-editor handle .aj files, too, because personally, I would
prefer to keep aspectj files named differently.
IMHO having an own name for aspectj files will ease their handling
considerably (easier selection/detection in build-scripts, etc.) but
also gives a clear indication to a developer, that there are aspects
used in a package (which imposes additional requirements not only on
the devleopment environment but also onto the later runtime:
additional libraries requires, etc.).
The main reason though is (for me): since aspects cause compile errors
in environments that are not yet adequately extended, I think it is a
very bad idea to keep them in normal .java files, since this could
cause the "sneak-in" of lots of non-compilable source code into many
projects without any warning. Of course such "sneak-in" may also be a
tactic to "force" the quick spreading of AspectJ extensions, but I
doubt that this is a good approach.
Michael
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #34024 is a reply to message #34011] |
Fri, 16 April 2004 09:15 |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
Hello (again!)
You are exactly right - it is very convenient to manage your aspects as
aj files. Until this release with the New Aspect Wizard, there wasn't an
easy way to create .aj files. Because that is now easy to do - it
highlights this problem with the editor support.
Andy.
Michael Moser wrote:
> Renaming the aspectj files .java makes their handling much easier
> indeed! Nevertheless I hope that Andy finds a quick solution to make
> the java-editor handle .aj files, too, because personally, I would
> prefer to keep aspectj files named differently.
> IMHO having an own name for aspectj files will ease their handling
> considerably (easier selection/detection in build-scripts, etc.) but
> also gives a clear indication to a developer, that there are aspects
> used in a package (which imposes additional requirements not only on
> the devleopment environment but also onto the later runtime:
> additional libraries requires, etc.).
> The main reason though is (for me): since aspects cause compile errors
> in environments that are not yet adequately extended, I think it is a
> very bad idea to keep them in normal .java files, since this could
> cause the "sneak-in" of lots of non-compilable source code into many
> projects without any warning. Of course such "sneak-in" may also be a
> tactic to "force" the quick spreading of AspectJ extensions, but I
> doubt that this is a good approach.
> Michael
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #34050 is a reply to message #34011] |
Fri, 16 April 2004 09:15 |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
Hello (again!)
You are exactly right - it is very convenient to manage your aspects as
aj files. Until this release with the New Aspect Wizard, there wasn't an
easy way to create .aj files. Because that is now easy to do - it
highlights this problem with the editor support.
Andy.
Michael Moser wrote:
> Renaming the aspectj files .java makes their handling much easier
> indeed! Nevertheless I hope that Andy finds a quick solution to make
> the java-editor handle .aj files, too, because personally, I would
> prefer to keep aspectj files named differently.
> IMHO having an own name for aspectj files will ease their handling
> considerably (easier selection/detection in build-scripts, etc.) but
> also gives a clear indication to a developer, that there are aspects
> used in a package (which imposes additional requirements not only on
> the devleopment environment but also onto the later runtime:
> additional libraries requires, etc.).
> The main reason though is (for me): since aspects cause compile errors
> in environments that are not yet adequately extended, I think it is a
> very bad idea to keep them in normal .java files, since this could
> cause the "sneak-in" of lots of non-compilable source code into many
> projects without any warning. Of course such "sneak-in" may also be a
> tactic to "force" the quick spreading of AspectJ extensions, but I
> doubt that this is a good approach.
> Michael
|
|
|
| Advice marker updates failed... [message #34526 is a reply to message #34024] |
Tue, 20 April 2004 09:07 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
I have a somewhat nasty effect:
I renamed my my aspect file from <...>.aj to <...>.java, since that
makes it easier to handle and edit, it also triggers automatic
rebuilds on save (which does not happen with .aj files) which then
triggers the Aspect Visualization to update, etc. etc.
But now whenever I do a rebuild I get an error popup telling me
-------------------
"Advice marker updates failed"
Reason:
Resource <....>.aj does not exist.
[OK]
-------------------
I have triggered refreshes of the package and the entire project a
couple of times, I have done a Project => Clean and Rebuild All, I
have terminated and restarted eclipse, but I keep getting the above
error alert, whenever the project rebuilds.
How do I get rid of this?
Michael
"Andy Clement" <clemas@uk.ibm.com> wrote in message
news:c5o86u$j1i$1@eclipse.org...
> Hello (again!)
>
> You are exactly right - it is very convenient to manage your aspects
as
> aj files. Until this release with the New Aspect Wizard, there
wasn't an
> easy way to create .aj files. Because that is now easy to do - it
> highlights this problem with the editor support.
>
> Andy.
>
> Michael Moser wrote:
>
> > Renaming the aspectj files .java makes their handling much easier
> > indeed! Nevertheless I hope that Andy finds a quick solution to
make
> > the java-editor handle .aj files, too, because personally, I
would
> > prefer to keep aspectj files named differently.
>
> > IMHO having an own name for aspectj files will ease their handling
> > considerably (easier selection/detection in build-scripts, etc.)
but
> > also gives a clear indication to a developer, that there are
aspects
> > used in a package (which imposes additional requirements not only
on
> > the devleopment environment but also onto the later runtime:
> > additional libraries requires, etc.).
>
> > The main reason though is (for me): since aspects cause compile
errors
> > in environments that are not yet adequately extended, I think it
is a
> > very bad idea to keep them in normal .java files, since this could
> > cause the "sneak-in" of lots of non-compilable source code into
many
> > projects without any warning. Of course such "sneak-in" may also
be a
> > tactic to "force" the quick spreading of AspectJ extensions, but I
> > doubt that this is a good approach.
>
> > Michael
>
>
|
|
|
| Advice marker updates failed... [message #34560 is a reply to message #34024] |
Tue, 20 April 2004 09:08 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
I have a somewhat nasty effect:
I renamed my my aspect file from <...>.aj to <...>.java, since that
makes it easier to handle and edit, it also triggers automatic
rebuilds on save (which does not happen with .aj files) which then
triggers the Aspect Visualization to update, etc. etc.
But now whenever I do a rebuild I get an error popup telling me
-------------------
"Advice marker updates failed"
Reason:
Resource <....>.aj does not exist.
[OK]
-------------------
I have triggered refreshes of the package and the entire project a
couple of times, I have done a Project => Clean and Rebuild All, I
have terminated and restarted eclipse, but I keep getting the above
error alert, whenever the project rebuilds.
How do I get rid of this?
Michael
"Andy Clement" <clemas@uk.ibm.com> wrote in message
news:c5o86u$j1i$1@eclipse.org...
> Hello (again!)
>
> You are exactly right - it is very convenient to manage your aspects
as
> aj files. Until this release with the New Aspect Wizard, there
wasn't an
> easy way to create .aj files. Because that is now easy to do - it
> highlights this problem with the editor support.
>
> Andy.
>
> Michael Moser wrote:
>
> > Renaming the aspectj files .java makes their handling much easier
> > indeed! Nevertheless I hope that Andy finds a quick solution to
make
> > the java-editor handle .aj files, too, because personally, I
would
> > prefer to keep aspectj files named differently.
>
> > IMHO having an own name for aspectj files will ease their handling
> > considerably (easier selection/detection in build-scripts, etc.)
but
> > also gives a clear indication to a developer, that there are
aspects
> > used in a package (which imposes additional requirements not only
on
> > the devleopment environment but also onto the later runtime:
> > additional libraries requires, etc.).
>
> > The main reason though is (for me): since aspects cause compile
errors
> > in environments that are not yet adequately extended, I think it
is a
> > very bad idea to keep them in normal .java files, since this could
> > cause the "sneak-in" of lots of non-compilable source code into
many
> > projects without any warning. Of course such "sneak-in" may also
be a
> > tactic to "force" the quick spreading of AspectJ extensions, but I
> > doubt that this is a good approach.
>
> > Michael
>
>
|
|
|
| Re: Advice marker updates failed... [message #34594 is a reply to message #34526] |
Tue, 20 April 2004 09:15 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
Oops - sorry:
first for the accidental double posting (I clicked once too often) and
then the mentioned error was on my side:
I still had an editor window open (I have too many...) on the old
..aj-file (I had done the rename externally via the file-system not via
refactoring, since that doesn't allow to change file extensions. And
that editor window's markes could not be updated since its target file
did not exist any more.
Michael
"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:c62ovu$oip$1@eclipse.org...
> I have a somewhat nasty effect:
>
> I renamed my my aspect file from <...>.aj to <...>.java, since that
> makes it easier to handle and edit, it also triggers automatic
> rebuilds on save (which does not happen with .aj files) which then
> triggers the Aspect Visualization to update, etc. etc.
>
> But now whenever I do a rebuild I get an error popup telling me
> -------------------
> "Advice marker updates failed"
> Reason:
> Resource <....>.aj does not exist.
> [OK]
> -------------------
>
> I have triggered refreshes of the package and the entire project a
> couple of times, I have done a Project => Clean and Rebuild All, I
> have terminated and restarted eclipse, but I keep getting the above
> error alert, whenever the project rebuilds.
>
> How do I get rid of this?
>
> Michael
>
>
> "Andy Clement" <clemas@uk.ibm.com> wrote in message
> news:c5o86u$j1i$1@eclipse.org...
> > Hello (again!)
> >
> > You are exactly right - it is very convenient to manage your
aspects
> as
> > aj files. Until this release with the New Aspect Wizard, there
> wasn't an
> > easy way to create .aj files. Because that is now easy to do - it
> > highlights this problem with the editor support.
> >
> > Andy.
> >
> > Michael Moser wrote:
> >
> > > Renaming the aspectj files .java makes their handling much
easier
> > > indeed! Nevertheless I hope that Andy finds a quick solution to
> make
> > > the java-editor handle .aj files, too, because personally, I
> would
> > > prefer to keep aspectj files named differently.
> >
> > > IMHO having an own name for aspectj files will ease their
handling
> > > considerably (easier selection/detection in build-scripts, etc.)
> but
> > > also gives a clear indication to a developer, that there are
> aspects
> > > used in a package (which imposes additional requirements not
only
> on
> > > the devleopment environment but also onto the later runtime:
> > > additional libraries requires, etc.).
> >
> > > The main reason though is (for me): since aspects cause compile
> errors
> > > in environments that are not yet adequately extended, I think it
> is a
> > > very bad idea to keep them in normal .java files, since this
could
> > > cause the "sneak-in" of lots of non-compilable source code into
> many
> > > projects without any warning. Of course such "sneak-in" may also
> be a
> > > tactic to "force" the quick spreading of AspectJ extensions, but
I
> > > doubt that this is a good approach.
> >
> > > Michael
> >
> >
>
>
|
|
| | |
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #578380 is a reply to message #33882] |
Fri, 16 April 2004 09:14 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
Renaming the aspectj files .java makes their handling much easier
indeed! Nevertheless I hope that Andy finds a quick solution to make
the java-editor handle .aj files, too, because personally, I would
prefer to keep aspectj files named differently.
IMHO having an own name for aspectj files will ease their handling
considerably (easier selection/detection in build-scripts, etc.) but
also gives a clear indication to a developer, that there are aspects
used in a package (which imposes additional requirements not only on
the devleopment environment but also onto the later runtime:
additional libraries requires, etc.).
The main reason though is (for me): since aspects cause compile errors
in environments that are not yet adequately extended, I think it is a
very bad idea to keep them in normal .java files, since this could
cause the "sneak-in" of lots of non-compilable source code into many
projects without any warning. Of course such "sneak-in" may also be a
tactic to "force" the quick spreading of AspectJ extensions, but I
doubt that this is a good approach.
Michael
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #578402 is a reply to message #34011] |
Fri, 16 April 2004 09:15 |
Andrew Clement
Messages: 162
Registered: July 2009 |
Senior Member |
|
|
Hello (again!)
You are exactly right - it is very convenient to manage your aspects as
aj files. Until this release with the New Aspect Wizard, there wasn't an
easy way to create .aj files. Because that is now easy to do - it
highlights this problem with the editor support.
Andy.
Michael Moser wrote:
> Renaming the aspectj files .java makes their handling much easier
> indeed! Nevertheless I hope that Andy finds a quick solution to make
> the java-editor handle .aj files, too, because personally, I would
> prefer to keep aspectj files named differently.
> IMHO having an own name for aspectj files will ease their handling
> considerably (easier selection/detection in build-scripts, etc.) but
> also gives a clear indication to a developer, that there are aspects
> used in a package (which imposes additional requirements not only on
> the devleopment environment but also onto the later runtime:
> additional libraries requires, etc.).
> The main reason though is (for me): since aspects cause compile errors
> in environments that are not yet adequately extended, I think it is a
> very bad idea to keep them in normal .java files, since this could
> cause the "sneak-in" of lots of non-compilable source code into many
> projects without any warning. Of course such "sneak-in" may also be a
> tactic to "force" the quick spreading of AspectJ extensions, but I
> doubt that this is a good approach.
> Michael
|
|
|
| Re: ajdt 117 on M8 - no colored syntax in editor ? [message #578436 is a reply to message #34011] |
Fri, 16 April 2004 09:15 |
Andrew Clement
Messages: 162
Registered: July 2009 |
Senior Member |
|
|
Hello (again!)
You are exactly right - it is very convenient to manage your aspects as
aj files. Until this release with the New Aspect Wizard, there wasn't an
easy way to create .aj files. Because that is now easy to do - it
highlights this problem with the editor support.
Andy.
Michael Moser wrote:
> Renaming the aspectj files .java makes their handling much easier
> indeed! Nevertheless I hope that Andy finds a quick solution to make
> the java-editor handle .aj files, too, because personally, I would
> prefer to keep aspectj files named differently.
> IMHO having an own name for aspectj files will ease their handling
> considerably (easier selection/detection in build-scripts, etc.) but
> also gives a clear indication to a developer, that there are aspects
> used in a package (which imposes additional requirements not only on
> the devleopment environment but also onto the later runtime:
> additional libraries requires, etc.).
> The main reason though is (for me): since aspects cause compile errors
> in environments that are not yet adequately extended, I think it is a
> very bad idea to keep them in normal .java files, since this could
> cause the "sneak-in" of lots of non-compilable source code into many
> projects without any warning. Of course such "sneak-in" may also be a
> tactic to "force" the quick spreading of AspectJ extensions, but I
> doubt that this is a good approach.
> Michael
|
|
|
| Advice marker updates failed... [message #578720 is a reply to message #34024] |
Tue, 20 April 2004 09:07 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
I have a somewhat nasty effect:
I renamed my my aspect file from <...>.aj to <...>.java, since that
makes it easier to handle and edit, it also triggers automatic
rebuilds on save (which does not happen with .aj files) which then
triggers the Aspect Visualization to update, etc. etc.
But now whenever I do a rebuild I get an error popup telling me
-------------------
"Advice marker updates failed"
Reason:
Resource <....>.aj does not exist.
[OK]
-------------------
I have triggered refreshes of the package and the entire project a
couple of times, I have done a Project => Clean and Rebuild All, I
have terminated and restarted eclipse, but I keep getting the above
error alert, whenever the project rebuilds.
How do I get rid of this?
Michael
"Andy Clement" <clemas@uk.ibm.com> wrote in message
news:c5o86u$j1i$1@eclipse.org...
> Hello (again!)
>
> You are exactly right - it is very convenient to manage your aspects
as
> aj files. Until this release with the New Aspect Wizard, there
wasn't an
> easy way to create .aj files. Because that is now easy to do - it
> highlights this problem with the editor support.
>
> Andy.
>
> Michael Moser wrote:
>
> > Renaming the aspectj files .java makes their handling much easier
> > indeed! Nevertheless I hope that Andy finds a quick solution to
make
> > the java-editor handle .aj files, too, because personally, I
would
> > prefer to keep aspectj files named differently.
>
> > IMHO having an own name for aspectj files will ease their handling
> > considerably (easier selection/detection in build-scripts, etc.)
but
> > also gives a clear indication to a developer, that there are
aspects
> > used in a package (which imposes additional requirements not only
on
> > the devleopment environment but also onto the later runtime:
> > additional libraries requires, etc.).
>
> > The main reason though is (for me): since aspects cause compile
errors
> > in environments that are not yet adequately extended, I think it
is a
> > very bad idea to keep them in normal .java files, since this could
> > cause the "sneak-in" of lots of non-compilable source code into
many
> > projects without any warning. Of course such "sneak-in" may also
be a
> > tactic to "force" the quick spreading of AspectJ extensions, but I
> > doubt that this is a good approach.
>
> > Michael
>
>
|
|
|
| Advice marker updates failed... [message #578732 is a reply to message #34024] |
Tue, 20 April 2004 09:08 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
I have a somewhat nasty effect:
I renamed my my aspect file from <...>.aj to <...>.java, since that
makes it easier to handle and edit, it also triggers automatic
rebuilds on save (which does not happen with .aj files) which then
triggers the Aspect Visualization to update, etc. etc.
But now whenever I do a rebuild I get an error popup telling me
-------------------
"Advice marker updates failed"
Reason:
Resource <....>.aj does not exist.
[OK]
-------------------
I have triggered refreshes of the package and the entire project a
couple of times, I have done a Project => Clean and Rebuild All, I
have terminated and restarted eclipse, but I keep getting the above
error alert, whenever the project rebuilds.
How do I get rid of this?
Michael
"Andy Clement" <clemas@uk.ibm.com> wrote in message
news:c5o86u$j1i$1@eclipse.org...
> Hello (again!)
>
> You are exactly right - it is very convenient to manage your aspects
as
> aj files. Until this release with the New Aspect Wizard, there
wasn't an
> easy way to create .aj files. Because that is now easy to do - it
> highlights this problem with the editor support.
>
> Andy.
>
> Michael Moser wrote:
>
> > Renaming the aspectj files .java makes their handling much easier
> > indeed! Nevertheless I hope that Andy finds a quick solution to
make
> > the java-editor handle .aj files, too, because personally, I
would
> > prefer to keep aspectj files named differently.
>
> > IMHO having an own name for aspectj files will ease their handling
> > considerably (easier selection/detection in build-scripts, etc.)
but
> > also gives a clear indication to a developer, that there are
aspects
> > used in a package (which imposes additional requirements not only
on
> > the devleopment environment but also onto the later runtime:
> > additional libraries requires, etc.).
>
> > The main reason though is (for me): since aspects cause compile
errors
> > in environments that are not yet adequately extended, I think it
is a
> > very bad idea to keep them in normal .java files, since this could
> > cause the "sneak-in" of lots of non-compilable source code into
many
> > projects without any warning. Of course such "sneak-in" may also
be a
> > tactic to "force" the quick spreading of AspectJ extensions, but I
> > doubt that this is a good approach.
>
> > Michael
>
>
|
|
|
| Re: Advice marker updates failed... [message #578746 is a reply to message #34526] |
Tue, 20 April 2004 09:15 |
Michael Moser
Messages: 914
Registered: July 2009 |
Senior Member |
|
|
Oops - sorry:
first for the accidental double posting (I clicked once too often) and
then the mentioned error was on my side:
I still had an editor window open (I have too many...) on the old
..aj-file (I had done the rename externally via the file-system not via
refactoring, since that doesn't allow to change file extensions. And
that editor window's markes could not be updated since its target file
did not exist any more.
Michael
"Michael Moser" <mmo@zurich.ibm.com> wrote in message
news:c62ovu$oip$1@eclipse.org...
> I have a somewhat nasty effect:
>
> I renamed my my aspect file from <...>.aj to <...>.java, since that
> makes it easier to handle and edit, it also triggers automatic
> rebuilds on save (which does not happen with .aj files) which then
> triggers the Aspect Visualization to update, etc. etc.
>
> But now whenever I do a rebuild I get an error popup telling me
> -------------------
> "Advice marker updates failed"
> Reason:
> Resource <....>.aj does not exist.
> [OK]
> -------------------
>
> I have triggered refreshes of the package and the entire project a
> couple of times, I have done a Project => Clean and Rebuild All, I
> have terminated and restarted eclipse, but I keep getting the above
> error alert, whenever the project rebuilds.
>
> How do I get rid of this?
>
> Michael
>
>
> "Andy Clement" <clemas@uk.ibm.com> wrote in message
> news:c5o86u$j1i$1@eclipse.org...
> > Hello (again!)
> >
> > You are exactly right - it is very convenient to manage your
aspects
> as
> > aj files. Until this release with the New Aspect Wizard, there
> wasn't an
> > easy way to create .aj files. Because that is now easy to do - it
> > highlights this problem with the editor support.
> >
> > Andy.
> >
> > Michael Moser wrote:
> >
> > > Renaming the aspectj files .java makes their handling much
easier
> > > indeed! Nevertheless I hope that Andy finds a quick solution to
> make
> > > the java-editor handle .aj files, too, because personally, I
> would
> > > prefer to keep aspectj files named differently.
> >
> > > IMHO having an own name for aspectj files will ease their
handling
> > > considerably (easier selection/detection in build-scripts, etc.)
> but
> > > also gives a clear indication to a developer, that there are
> aspects
> > > used in a package (which imposes additional requirements not
only
> on
> > > the devleopment environment but also onto the later runtime:
> > > additional libraries requires, etc.).
> >
> > > The main reason though is (for me): since aspects cause compile
> errors
> > > in environments that are not yet adequately extended, I think it
> is a
> > > very bad idea to keep them in normal .java files, since this
could
> > > cause the "sneak-in" of lots of non-compilable source code into
> many
> > > projects without any warning. Of course such "sneak-in" may also
> be a
> > > tactic to "force" the quick spreading of AspectJ extensions, but
I
> > > doubt that this is a good approach.
> >
> > > Michael
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Wed Feb 05 08:48:40 GMT 2025
Powered by FUDForum. Page generated in 0.08994 seconds |
] 
Search
Help
Register
Login
Home
