[
https://jira.codehaus.org/browse/MNG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-139:
------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> server definitions should be reusable - review use of repository IDs
> --------------------------------------------------------------------
>
> Key: MNG-139
> URL: https://jira.codehaus.org/browse/MNG-139
> Project: Maven
> Issue Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Brett Porter
>
> currently if multiple projects use the same server for deployment, we are
> relying on inheritence to share the definition, or it must be copied. This
> applies similarly to the SCM connection and the dist/site management settings.
> It would be a good idea to be able to declare these elements in a deployed
> artifact.
> It may still be reasonable to do this through inheritence, but there is a
> chance we'll hit the need for multiple inheritence (because multiple projects
> inherit things from different sources), so we should enumerate the use cases
> and verify it.
> eg.
> A B
> / \ / \
> C D E
> Where A and B declare two different things that D uses both of, but which C
> and E desire only to inherit one of.
> This essentially using composition for some elements instead of inheritence.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
