You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (JIRA)" <ji...@codehaus.org> on 2010/05/05 13:59:12 UTC
[jira] Created: (ARCHETYPE-303) Externalize Archetype Catalog model
into separate module
Externalize Archetype Catalog model into separate module
--------------------------------------------------------
Key: ARCHETYPE-303
URL: http://jira.codehaus.org/browse/ARCHETYPE-303
Project: Maven Archetype
Issue Type: Improvement
Components: Archetypes
Reporter: Tamás Cservenák
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
[jira] Updated: (ARCHETYPE-303) Externalize Archetype Catalog model
into separate module
Posted by "Tamás Cservenák (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (ARCHETYPE-303) Externalize Archetype Catalog model
into separate module
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated ARCHETYPE-303:
------------------------------------
Component/s: (was: Archetypes)
> 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
>
> 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
[jira] Closed: (ARCHETYPE-303) Externalize Archetype Catalog model
into separate module
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/ARCHETYPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed ARCHETYPE-303.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.1
Assignee: Tamás Cservenák
> Externalize Archetype Catalog model into separate module
> --------------------------------------------------------
>
> Key: ARCHETYPE-303
> URL: https://jira.codehaus.org/browse/ARCHETYPE-303
> Project: Maven Archetype
> Issue Type: Improvement
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Fix For: 2.1
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-303) Externalize Archetype Catalog
model into separate module
Posted by "Tamás Cservenák (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243745#action_243745 ]
Tamás Cservenák commented on ARCHETYPE-303:
-------------------------------------------
Change applied in http://svn.apache.org/viewvc?view=revision&revision=1036834
> 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