[
https://jira.codehaus.org/browse/MCOMPILER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kriegisch updated MCOMPILER-194:
------------------------------------------
Attachment: SO_AJ_MavenSoftExceptions.zip
Sample AspectJ + Maven project showing what needs to be done in order to make
compilation work. Please note that I have to set 'useIncrementalCompilation' to
'false' in order to make incremental compilation work (reverse logic, needs to
be fixed).
I would like to see this issue resolved, I think it should be easy to fix and
is not just a minor thing.
P.S.: I have added the same ZIP file to MCOMPILER-209, just in case.
> Strange effects with springs @Configurable (AspectJ) and new compiler plugin
> version 3.0
> ----------------------------------------------------------------------------------------
>
> Key: MCOMPILER-194
> URL: https://jira.codehaus.org/browse/MCOMPILER-194
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Environment: jdk 1.6.0_38, jdk 1.6.0_37
> Reporter: Andreas Höhmann
> Priority: Blocker
> Attachments: SO_AJ_MavenSoftExceptions.zip
>
>
> I have no details I can only report the "effects" ..
> I have a maven project with compiler-plugin 2.5.1,
> aspectj-plugin 1.4, java 1.6 and a lot of @Configurable
> annotations in my code. Aspectj will decorate these classes
> so @Autowired dependencies injected during runtime.
> All is working fine.
> Now I switch to compiler-plugin 3.0 ... nothing else changed!
> Then "sometimes" I got NPE's because the injected service etc. are
> not available. I guess aspectj was not successfull. I have no
> errors etc. anywhere during build.
> Strang :)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
