[
https://issues.apache.org/jira/browse/TOBAGO-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst resolved TOBAGO-270.
---------------------------------------
Resolution: Not A Problem
This is not causing any issues in Tobago.
> APT option values passed to the APT compiler are wrong: -Akey=value =>
> -Akey=value=null
> ---------------------------------------------------------------------------------------
>
> Key: TOBAGO-270
> URL: https://issues.apache.org/jira/browse/TOBAGO-270
> Project: MyFaces Tobago
> Issue Type: Bug
> Components: Maven Apt Plugin
> Affects Versions: 1.0.9
> Reporter: Thierry Monney
> Assignee: Dennis Kieselhorst
>
> When APT options are specified, the plugin does not split the supplied
> options as quiet=true (as one would expect it). Instead, the annotation
> processor's environment gets an option of the type quiet=true=null, where
> quiet=true is the actual key and null is the actual value.
> For example, <A>-Aquiet=true</A> ends up as -Aquiet=true=null. The same
> happens whether -A is explicit or not.
> The workaround is to manually parse the key in the annotation processor, e.g.,
> String value = null;
> Set<String> keys = env.getOptions().keySet();
> for (String key : keys) {
> if (key.startsWith(optionName)) {
> int index = key.indexOf('=');
> if (index > 0) {
> value = key.substring(index + 1, key.length());
> }
> break;
> }
> }
> I am not sure whether this is a bug in the Maven plugin, in Plexus command
> line lib or even in APT itself. Currently I haven't too much time to
> seriously dig into it, but I will try to narrow things down a little and give
> more precisions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
