maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamás Cservenák (JIRA) <j...@codehaus.org>
Subject [jira] Updated: (ARCHETYPE-303) Externalize Archetype Catalog model into separate module
Date Thu, 18 Nov 2010 22:20:03 GMT

     [ http://jira.codehaus.org/browse/ARCHETYPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tamás Cservenák updated ARCHETYPE-303:
--------------------------------------

    Attachment: archetype-303.patch

Complete patch for resolving this issue, made against https://svn.apache.org/repos/asf/maven/archetype/trunk
@ 1036655

> Externalize Archetype Catalog model into separate module
> --------------------------------------------------------
>
>                 Key: ARCHETYPE-303
>                 URL: http://jira.codehaus.org/browse/ARCHETYPE-303
>             Project: Maven Archetype
>          Issue Type: Improvement
>            Reporter: Tamás Cservenák
>         Attachments: archetype-303.patch
>
>
> Externalize Archetype Catalog model into separate module (ideally, without any dependency).
> This model would be likely reused by 3rd parties, but without "dragging" all the dependencies
and other classes in archetype-common module.
> Typical example is Nexus's ArchetypePlugin, that publishes the archetype catalog, but
from Nexus Index. Currently, that plugin _copied_ (rev668260) of Modello model to be able
to publish. This obviously may lead to problems later.

-- 
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

       

Mime
View raw message