Re: [aspectj-users] problems with generated code

[Andy Clement <andrew.clement@xxxxxxxxx>]

Steve is right, the 'missing prototype' bug is actually here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=252199

Andy

On 6 November 2011 15:43, Steve Ash <stevemash@xxxxxxxxx> wrote:
> Asad-
> Would you mind posting the link to the enhancement request whenever you open
> it so that I can vote for it?  We have been wanted to use Project Lambok for
> some time now without the tricky maven acrobatics.  Andy C mentioned that he
> had prototyped a fix for it in IAJC, but misplaced the workspace somewhere
> (IIRC).
> Thanks,
> Steve
>
> On Wed, Nov 2, 2011 at 4:23 PM, Andrew Eisenberg <andrew@xxxxxxxxxxxx>
> wrote:
>>
>> At this point, the best you can do is compile on the command line (or
>> use maven directly) to generate the extra classes.  The AspectJ
>> builder (ie- the Eclipse-based wrapper for the ajc compiler) will
>> correctly generate the extra source/class files, but it will not feed
>> them back into the compilation process so that they will be used to
>> track down references in standard source files.
>>
>> This may be something that we can fix in AJDT, but I can't say how
>> long before this feature makes it through the pipeline.
>>
>> On Wed, Nov 2, 2011 at 5:41 PM, Asad Jawahar <room7hostel4@xxxxxxxxx>
>> wrote:
>> > It is a Java 5 annotation processor and it generates code which is not
>> > getting compiled. That's exactly why I am looking for a workaround. Is there
>> > any way we can invoke the aspectj builder to compile the generated code?
>> >
>> > Thanks,
>> > -Asad
>> >
>> > --- On Tue, 11/1/11, Andrew Eisenberg <andrew@xxxxxxxxxxxx> wrote:
>> >
>> >> From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>> >> Subject: Re: [aspectj-users] problems with generated code
>> >> To: "Asad Jawahar" <room7hostel4@xxxxxxxxx>
>> >> Cc: aspectj-users@xxxxxxxxxxx
>> >> Date: Tuesday, November 1, 2011, 11:27 PM
>> >> What kind of annotation processor are
>> >> you using?  Java 5 or 6?  If it
>> >> is Java 6, then there is not much that we can do.  If
>> >> it is Java 5,
>> >> then things should work as long as you are not generating
>> >> new source
>> >> files.
>> >>
>> >> On Wed, Nov 2, 2011 at 12:11 AM, Asad Jawahar <room7hostel4@xxxxxxxxx>
>> >> wrote:
>> >> > Batch mode works as you said. Is there any workaround
>> >> to make it work in Eclipse? We were planning to provide the
>> >> plug-in to our customers and the experience won't be good if
>> >> we ask them to compile from the command line.
>> >> >
>> >> > I will raise a bug for this.
>> >> >
>> >> > Thanks,
>> >> > -Asad
>> >> >
>> >> > --- On Fri, 10/28/11, Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>> >> wrote:
>> >> >
>> >> >> From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
>> >> >> Subject: Re: [aspectj-users] problems with
>> >> generated code
>> >> >> To: aspectj-users@xxxxxxxxxxx
>> >> >> Date: Friday, October 28, 2011, 12:32 PM
>> >> >> AJDT does not fully support Java 5
>> >> >> annotation processors, and does not
>> >> >> support Java 6 style processors at all.
>> >> >>
>> >> >> What is supported is the following:
>> >> >>
>> >> >> 1. generating new files
>> >> >> 2. adding compile errors or warnings to existing
>> >> files
>> >> >>
>> >> >> However, we do not run the AspectJ compiler in a
>> >> loop to
>> >> >> handle new
>> >> >> files generated from APT.  This is required for
>> >> your
>> >> >> situation.  I
>> >> >> believe that running the aspectj compiler in batch
>> >> mode
>> >> >> (ie- from the
>> >> >> command line) will properly handle this
>> >> situation.
>> >> >>
>> >> >> The reason why this has not been implemented is
>> >> that we
>> >> >> have not had
>> >> >> this requirement in the past.  Could you raise a
>> >> bug
>> >> >> for this inside
>> >> >> of bugzilla?
>> >> >>
>> >> >> https://bugs.eclipse.org/bugs/
>> >> >>
>> >> >> On Thu, Oct 27, 2011 at 12:53 PM, Asad Jawahar
>> >> <room7hostel4@xxxxxxxxx>
>> >> >> wrote:
>> >> >> > I am using AspectJ in a project that also has
>> >> my
>> >> >> custom Java 5 style annotation peocessor. The
>> >> annotation
>> >> >> processor generates some code that has no AspectJ
>> >> dependency
>> >> >> at all. The problem appears to be that the AJDT
>> >> builder is
>> >> >> ignoring the generated files and they and they
>> >> don't get
>> >> >> compiled. I get Java compilation errors when I try
>> >> to use
>> >> >> the generated types anywhere in the
>> >> >> > project. If I disable AspectJ (AspectJ tools
>> >> >
>> >> >> Remove AspectJ Capability), the code compiles
>> >> fine. At this
>> >> >> point if I convert the project back to AspectJ and
>> >> do a
>> >> >> clean, the errors come back. Is this a supported
>> >>  scenario?
>> >> >> If so, is there something additional I need to do
>> >> in my
>> >> >> annotation processor to make the builder aware of
>> >> the
>> >> >> generated files?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > -Asad
>> >> >> >
>> >> >> >
>> >> _______________________________________________
>> >> >> > aspectj-users mailing list
>> >> >> > aspectj-users@xxxxxxxxxxx
>> >> >> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >> >> >
>> >> >> _______________________________________________
>> >> >> aspectj-users mailing list
>> >> >> aspectj-users@xxxxxxxxxxx
>> >> >> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >> >>
>> >> >
>> >>
>> >
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>