[
http://jira.codehaus.org/browse/MNG-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115108
]
Siarhei Dudzin commented on MNG-3303:
-------------------------------------
TBH, settings.xml would be probably the last place (unless other choices is not
an option) where I would want to have this. It's much more controllable if you
have it in a parent pom (even on the organization level) then you can easier
roll out changes, while settings.xml is more difficult to automatically
distribute. And if a quick startup project is needed a new archetype can be
created.
The idea behind the plugin (my understanding) is to have pom settings reflected
on your eclipse project. By moving something out of the reproducible
dependency/configuration tree may make the result of a project less
reproducible.
Even though I understand the motion behind this request I wouldn't want to have
a developer in my team who is unable to generate his eclipse project correctly
just because he has wrong version of settings.xml or forgotten to put something
(may become a nightmare in bigger teams), - just my2 cents though.
> read some plugin settings from settings.xml
> -------------------------------------------
>
> Key: MNG-3303
> URL: http://jira.codehaus.org/browse/MNG-3303
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Paul Harrison
>
> It is not appropriate that all of the possible settings for the plug-in are
> read from the pom, as they will be dependent on details of the user's
> personal eclipse installation - it would be more appropriate if they were
> picked up from the settings.xml file.
> e.g. additionalProjectnatures propetry
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
