Yep sorry, my bad, this was a configuration issue on my side, the fix
worked.
Cheers !
2015-07-06 21:51 GMT+02:00 Andy Clement andrew.clem...@gmail.com:
Hi Romain,
It should be in - I can see the fix in the git log (although I wish we’d
tracked this in a real bugzilla rather than just in
Hi Andy,
Contacting you again abount this issue, did the fix make it into 1.8.6? We
get the same errors at compile time.
Cheers
Romain
2015-04-12 19:53 GMT+02:00 Andy Clement andrew.clem...@gmail.com:
Nope I have no testcase, I couldn’t recreate it in a simple scenario after
trying for a
Hi Romain,
It should be in - I can see the fix in the git log (although I wish we’d
tracked this in a real bugzilla rather than just in email). Are you sure you
aren’t hitting something new now, having changed a bit of code?
cheers,
Andy
On Jul 6, 2015, at 5:33 AM, Romain Primet
Hi Andy.
Possibly it is the use of declare parents extends (with generics),
that is just not as common as declare parents implements.
Actually, no. That was the first thing I tried, namely getting rid of the
interface implementation 'DefaultIdentifiable' and replacing it like this:
package
Hey,
Yes, Romain sent me some repo references off list so the discussion ended up
continuing there. I was planning to post back here when we got to a conclusion
(which we just did last night when Romain tested a 1.8.6 snapshot I created
with a potential fix).
The new method will make it into
Romain,
I was just curious, it is not necessary to dig deeper. It was just an idea, I
did not expect it to work anyway. Compilation errors exist for a reason. ;-)
--
Alexander Kriegisch
http://scrum-master.de
Romain Primet schrieb am 11.04.2015 15:03:
Le 11/04/2015 14:47, Alexander
Hi Andy.
I have looked into this a little more and noticed that the build within Eclipse
Luna with AJDT works nicely, but fails with AspectJ Maven Plugin and on the
command line via ajc.bat. So this might be a clue what it going wrong if you
can answer one question: What does ADJT differently
If there is one ajc, yep. I'm afraid I haven't had a chance to dig further
into this yet.
cheers
Andy
On 6 April 2015 at 12:34, Romain Primet romain.pri...@gmail.com wrote:
For a particular compilation we collect up all the aspects we know
about. We then apply all the aspects affecting the
Hi list,
I have an aspectJ-based codebase that currently uses 1.6.6 (compiler and
runtime) and builds fine.
Moving to 1.6.7+, I get errors related to inter-type declarations.
Specifically, a library is being weaved by an aspect that declares a new
parent for an existing class. This parent
