[
https://issues.apache.org/jira/browse/COCOON-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606267#action_12606267
]
Grzegorz Kossakowski commented on COCOON-2214:
----------------------------------------------
David, I've previously missed three important issues about your
achetype-catalog.xml:
1. It should contain Apache header but since you have attached it as
contribution that's not a show-stopper.
2. Versions listed in the file are SNAPSHOT ones coming from building the
Cocoon from trunk. That's a mistake as other people won't be able to use them
because SNAPSHOTs are never released to central repository. Here you can
consult versions of Cocoon artifacts that has been released:
http://repo1.maven.org/maven2/org/apache/cocoon/
3. The description of archetypes is little bit misleading. The best option is
to borrow them from
http://cocoon.apache.org/2.2/maven-plugins/
Even though I can fix those myself I'll have time for this tomorrow. If you
don't mind upload improved file please so it'll faster get uploaded.
> Update C22 block building process through use of Maven archetype:generate
> command
> ---------------------------------------------------------------------------------
>
> Key: COCOON-2214
> URL: https://issues.apache.org/jira/browse/COCOON-2214
> Project: Cocoon
> Issue Type: Improvement
> Components: - Build System: Maven, - Documentation
> Affects Versions: 2.2, 2.2-dev (Current SVN)
> Reporter: David Legg
> Assignee: Grzegorz Kossakowski
> Priority: Minor
> Attachments: archetype-catalog.xml
>
>
> Version 2.0.9 (and maybe earlier) of Maven has deprecated the use of the
> archetype:create goal in favour of archetype:generate.
> As of this report the Cocoon Tutorial uses archetype:create in its
> instructions and this causes a warning to be issued when attempting to build
> blocks.
> After discussion on the list it was felt the solution was to start using
> archetype:generate but this changes the behaviour of Maven such that it
> interactively asks for values such as the artifactId and groupId etc.
> Unfortunately, the first question it asks is which archetype you wish to
> build and by default this list is huge and will continue to grow as more
> projects use it.
> Attached to this note is a file which if placed in a suitable location on the
> Cocoon web site could be used to reduce the archetype list to just those
> required for Cocoon (Currently 3 items).
> The Cocoon tutorial would need to be updated to replace the archetype:create
> command to something like the following: -
> mvn archetype:generate -DarchetypeCatalog=http://[path to
> catalog]/archetype-catalog.xml
> This would generate output similar to the following: -
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> ...
> [INFO] [archetype:generate]
> [INFO] Generating project in Interactive mode
> [INFO] No archetype defined. Using maven-archetype-quickstart
> (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)
> Choose archetype:
> 1: local -> cocoon-22-archetype-block-plain (Creates an empty Cocoon block)
> 2: local -> cocoon-22-archetype-block (Creates a minimal Cocoon block)
> 3: local -> cocoon-22-archetype-webapp (Creates a web application Cocoon
> block)
> Choose a number: (1/2/3): Choose archetype:
> This should be much more comprehensible to new users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
