cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: M10N
Date Wed, 11 Jan 2006 15:57:18 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/756.html

Document ID: 756
Branch: main
Language: default
Name: M10N (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/11/06 3:57:06 PM
Updated by: Jorg Heymans

A new version has been created, state: publish

Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 11492 bytes (previous version: 9916 bytes)
Content diff:
(180 equal lines skipped)
    development purposes. However if you do <tt>mvn jetty6:run</tt> you'll see
that
    it has a classloader issue with JCL.</p>
    
+++ <h2>Archetypes</h2>
+++ 
+++ <p>Archetypes are application templates ("skeletons") that are managed by
+++ maven2. They are useful to create a standard project directory structure, to
+++ some degree variable substitution can be used to customize the contents (ie the
+++ files) of the skeleton.</p>
+++ 
+++ <p>There are a number of problems with the current archetype implementation :
+++ </p>
+++ 
+++ <ul>
+++ <li>The template variable substitution looks for $myplaceholder references in
+++ all files and tries to subsitute them with the values supplied on the
+++ commandline. This ofcourse does not work on binary files, so maven usually
+++ throws an exception or corrupts the binary file. The substitution engine also
+++ garbles special chars like ©, this happens currently in
+++ core-archetype/welcome.xslt, making the xslt processor barf.
+++ (<a href="http://jira.codehaus.org/browse/ARCHETYPE-3">http://jira.codehaus.org/browse/ARCHETYPE-3</a>)   
+++ </li>
+++ <li>It is impossible to use archetypes unless they are published on ibiblio
+++ (<a href="http://jira.codehaus.org/browse/MNG-1670">http://jira.codehaus.org/browse/MNG-1670</a>)
+++ </li>
+++ <li>There is no support for filesets in the archetype descriptor, meaning you
+++ have to physically list every file that needs to to in the skeleton. This is
+++ annoying for us because we're linking in the webapp files through svn:external.
+++ </li>
+++ </ul>
+++ 
+++ <p>You can read a bit more on archetypes
+++ <a href="http://maven.apache.org/guides/mini/guide-creating-archetypes.html">here</a>
+++ or check out the
+++ <a href="http://svn.apache.org/repos/asf/maven/archetype/trunk/">maven repo</a>
+++ for examples.</p>
+++ 
    <h2>How to add a new dependency to an existing module</h2>
    
    <p>There are two possibilities here : the new dependency is already using maven,
(64 equal lines skipped)


Fields
======
no changes

Links
=====
no changes

Custom Fields
=============
no changes

Collections
===========
no changes

Mime
View raw message