Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
Description
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)
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
FORGE-5 Maven archetypes for Magnolia modules and projects
-
- Closed
-