[
https://jira.codehaus.org/browse/MCOMPILER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Sanwal updated MCOMPILER-227:
----------------------------------
Description:
The parent project of our software specifies <proc>none</proc> for compiler
plugin.
However some of the child projects need to re-enable it. But none of "none" or
"only" fits the need. Basically we need to get the same behavior has specified
by "no value set" i.e both annotation processing and compilation.
Would it be possible to have an option as "both" which can be explicitly
specified and behaves same as currently it behaves when no value for <proc> is
set.
was:
The parent project of our software specifies <proc>none</proc> for compiler
plugin.
However some of the child projects need to re-enable it. But none of "none" or
"only" fits the need. Basically we need to get the same behavior has specified
by "no value set" i.e both annotation processing and compilation.
Would it be possible to have an option as "both" which as be explicitly
specified. This behaves same as currently it behaves when no value for <proc>
is set.
> Ability to reset the annotation processing to "not specified"
> -------------------------------------------------------------
>
> Key: MCOMPILER-227
> URL: https://jira.codehaus.org/browse/MCOMPILER-227
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: Ravi Sanwal
>
> The parent project of our software specifies <proc>none</proc> for compiler
> plugin.
> However some of the child projects need to re-enable it. But none of "none"
> or "only" fits the need. Basically we need to get the same behavior has
> specified by "no value set" i.e both annotation processing and compilation.
> Would it be possible to have an option as "both" which can be explicitly
> specified and behaves same as currently it behaves when no value for <proc>
> is set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
