Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <1359112924.1214001345046.JavaMail.jira@brutus>
Date: Fri, 20 Jun 2008 15:35:45 -0700 (PDT)
From: "David Legg (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2214) Update C22 block building process
 through use of Maven archetype:generate command
In-Reply-To: <1788547946.1213829145067.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606923#action_12606923 ] 

David Legg commented on COCOON-2214:
------------------------------------

Thanks for that Grek.

I began updating the documentation but then ran into a problem.  It seems Maven can't handle remote archetype catalogs yet after all.  I naturally assumed that since it handled the file:// protocol it would also handle http:// protocol but it mangles the URL.

I've raised a report on the Maven JIRA (http://jira.codehaus.org/browse/ARCHETYPE-124) and we'll see how it goes.

One work around is to download the file from the server and then use the file:// protocol.  I've tested that and it works.

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