Improve and update archetypes
-----------------------------
Key: MPARCH-13
URL: http://jira.magnolia-cms.com/browse/MPARCH-13
Project: Magnolia Maven Archetypes
Issue Type: Improvement
Reporter: Joerg Bellmann
Assignee: Grégory Joseph
Hi Grégory,
maybe you remember my forge-request for an archetype-project 4 weeks ago? When
I was in Basel to an magnolia course christian ringele told us that the
archetypes provided in svn aren't really usable. So I created an archetype
that, maybe, brings better support for the community and my company. I had a
look at the archetypes in svn and tried to create a module-project with them. I
got strange log-messages from maven I've never seen before and the result was
not acceptable. Here are my points for working:
* throw away the old archetypes with a tag in svn
* create new (or take mine) archetypes for module-projects and webapp-projects
in trunk
* create a separate parent-module that allows to release archetypes
independently
* provide/maintain a catalog-file in a directory in svn (accessable by http)
with updated archetype informations that can be used in IDE and on console to
create new projects
* improve/extend documentation on project creation in the wiki and maybe with
small screencasts (on youtube embedded in wiki-pages when possible)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
