[
https://jira.codehaus.org/browse/MNG-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355835#comment-355835
]
Robert Scholte commented on MNG-5720:
-------------------------------------
I don't think this is required for the merging, I have to investigate. It was
required for the {{<provides>}} element to be translated to {{Properties}} to
be able to uniquely identify the toolchains. Based on experience of
configurations of plugins I think it would still be nice to support
complex/nested structures. The only ones having a challenge are the toolchain
*developers*, but I that's fine by me. We could also add something like the
following method to help developers, if they just want to use properties:
{code}
public static Properties toProperties(Object configuration) throws
IllegalArgumentException
{code}
> Change 'configuration' from Object to Properties in toolchains.xml
> ------------------------------------------------------------------
>
> Key: MNG-5720
> URL: https://jira.codehaus.org/browse/MNG-5720
> Project: Maven
> Issue Type: Improvement
> Components: Toolchains
> Affects Versions: 3.2.3
> Reporter: Herve Boutemy
> Assignee: Robert Scholte
> Fix For: 3.2.4
>
>
> Officially the content of the {{<configuration>}} element in a toolchain was
> free of structure, although we only know Properties-like structures.
> To improve the automatic handling by Modello, it is better to drop the free
> structure and change it to Properties like it was done in MNG-5718 for
> <provides>.
> The {{jdk}} toolchain will be modified accordingly, being transparent for
> users.
> But any custom toolchain implementation will need to be updated.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
