[
http://jira.codehaus.org/browse/MNG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-139:
-----------------------------
Priority: Major (was: Trivial)
> server definitions should be reusable - review use of repository IDs
> --------------------------------------------------------------------
>
> Key: MNG-139
> URL: http://jira.codehaus.org/browse/MNG-139
> Project: Maven 2
> Issue Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Brett Porter
> Fix For: 2.x
>
>
> 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 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
