You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/08 02:46:21 UTC
[jira] Updated: (MNG-139) server definitions should be reusable
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Mon, 7 Feb 2005 8:45 PM
Changes:
Component changed to design
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-139?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-139
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-139
Summary: server definitions should be reusable
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Components:
design
Assignee:
Reporter: Brett Porter
Created: Mon, 7 Feb 2005 8:39 PM
Updated: Mon, 7 Feb 2005 8:45 PM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira