[jira] [Commented] (MNG-6877) Separate scope for annotation processing

["Stanislav Spiridonov (Jira)" <ji...@apache.org>]

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

Stanislav Spiridonov commented on MNG-6877:
-------------------------------------------

Test project: [https://github.com/foal/MNG-6877]

*mvn package* as well as *mvn install* - doesn't work on the first try.

to build this project for the first time you need to
 # run mvn install from the project root 
 # go to apt-processor
 # mvn install

Only after that *mvn package* and *mvn install* will work.

Please check the file *generated.txt* in *apt\target\generated-sources\annotations*. It should contains text "test 01"

BUT! if you change the source of apt-processor e.g *wr.append("test 01");* -> *wr.append("test 02");* in *org.gwtproject.editor.processor.AptProcessor* and run *mvn clean package* the file apt\target\generated-sources\annotations\generated.txt still contains text "test 01", even if run *mvn clean install* the file apt\target\generated-sources\annotations\generated.txt still contains text "test 01". You need to run *mvn clean install* second time to correct regenerate the test file.**

 

 

> Separate scope for annotation processing
> ----------------------------------------
>
>                 Key: MNG-6877
>                 URL: https://issues.apache.org/jira/browse/MNG-6877
>             Project: Maven
>          Issue Type: New Feature
>          Components: Dependencies
>    Affects Versions: 3.6.3
>            Reporter: Stanislav Spiridonov
>            Priority: Major
>
> Hi, I know about annotationProcessorPaths of maven-compiler-plugin and it works somehow, but with some limitations
>  #  dependencyManagement does not work for path elements (need to specify version). workaround use variable
>  # if I have apt-processor as a part of the project (separate module) and use it only in the maven-compiler-plugin configuration it has been built in the last order, that brakes build
>  #  the maven-compiler-plugin can use only INSTALLED artifacts, not from a reactor
>  
> Use the processor as a usual dependency is also not a case (even with provided scope)
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)