[ 
https://issues.apache.org/jira/browse/MCOMPILER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403474#comment-16403474
 ] 

Alexander Kriegisch edited comment on MCOMPILER-194 at 3/17/18 3:12 PM:
------------------------------------------------------------------------

That's the problem with ignoring a ticket for too long. The extra repository 
specified in the POM is no longer available, but instead you can use this fork 
available on Maven Central. I had to change all my POMs as well about 2 years 
ago or so:
{code:xml}
<groupId>com.jolira</groupId>
<artifactId>onejar-maven-plugin</artifactId>
<version>1.4.4</version>
{code}


was (Author: kriegaex):
That's the problem with ignoring a ticket for too long. The extra repository 
specified in the POM is no longer available, but instead you can use this fork. 
I had to change all my POMs as well about 2 years ago or so:

{code:xml}
<groupId>com.jolira</groupId>
<artifactId>onejar-maven-plugin</artifactId>
<version>1.4.4</version>
{code}

> Strange effects with springs @Configurable (AspectJ) and new compiler plugin 
> version 3.0
> ----------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-194
>                 URL: https://issues.apache.org/jira/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
(v7.6.3#76005)

Reply via email to