The following comment has been added to this issue:
Author: Ryan Hoegg
Created: Thu, 21 Aug 2003 1:10 PM
Body:
Re: the taglib. I am new to jelly, so I wasn't aware this was even possible. Perhaps
someone more experienced with jelly can help out? I was under the impression that
other plugins would define a couple properties and then attainGoal genapp.
Brian: I think the capability for other plugins to have templates can only help. The
genapp plugin in my mind is both an educational tool for new users and a central place
for application generation functionality. Any templates provided by the genapp
plugin should probably be fairly generic. For example, it should be up to the writers
of the war plugin to decide if they even want to provide an application template, and
if so what it should look like.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-426
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-426
Summary: Allow genapp to support multiple templates
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Versions:
1.0-beta-9
1.1
Assignee:
Reporter: Brian Ewins
Created: Wed, 14 May 2003 10:27 AM
Updated: Wed, 20 Aug 2003 1:17 AM
Environment: all
Description:
At the moment the genapp plugin is pretty rudimentary, you only get the 'standard'
maven template project. I'd like maven to support multiple project templates, to make
it easier to (for example) set up a beginner's webapp, ejb, maven-plugin project; a
project with a standard setup for a company (logos, developers, scm); etc etc.
Attached is some code to support this proposal. It changes the structure of the genapp
'plugin.resources' directory so that it more closely matches a normal project:
plugin-resources/:
project.properties project.xml src
plugin-resources/src:
conf java test
plugin-resources/src/conf:
app.properties
plugin-resources/src/java:
App.java
plugin-resources/src/test:
AbstractTestCase.java AppTest.java NaughtyTest.java
Next we identify the three kinds of resource which need copied - those which need
'repackaged' like java, test; those which need filtered (project.xml), and those which
just need copied (everything else). I do this by adding a plugin.properties with the
lines:
maven.genapp.repackage=java,test
maven.genapp.filter=project.xml
Finally I updated the plugin.jelly (attached). The plugin.jelly was written for b8,
(hence the missing 'ant:' stuff) and takes an extra parameter:
maven -Dpackage=blah -Dtemplate=example genapp
this will try to copy the 'example' project from the user's home dir. This code isn't
really sophisticated enough, it should try the user's home dir first then fall back on
the plugin.resources dir, with the 'default' output of genapp moved to a project
called 'default'; this would let maven ship with more examples (including a reactor
example!) while giving the user a way to override them.
If the comments on this idea involve more changes to the plugin I'd be happy to oblige.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
