[
http://jira.codehaus.org/browse/ARCHETYPE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113773
]
Ernesto Barreras edited comment on ARCHETYPE-70 at 11/13/07 9:43 PM:
---------------------------------------------------------------------
Today I was trying to create my first archetype and was very surprised when I
realized that using arbitrary parameters didn't work. I would say that this is
almost a must for any not very simple archetype.
Ernesto
was:
I have been trying to create my first archetype and was very surprised to see
that I couldn't use arbitrary parameters. I would say that this is almost a
must for any not very simple archetype.
Ernesto
> Add project description as a mojo parameter
> -------------------------------------------
>
> Key: ARCHETYPE-70
> URL: http://jira.codehaus.org/browse/ARCHETYPE-70
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Plugin
> Reporter: Michael Heuer
> Priority: Minor
> Attachments: patch.txt
>
>
> For my archetype bundle, I require the project description as a parameter.
> I use it in the pom.xml
> <description>${description}</description>
> in a license HEADER.txt
> /*
> ${artifactId} ${description}
> Copyright ...
> in a package.html
> <html>
> <body>
> <p>${description}</p>
> </body>
> </html>
> and so on.
> The attached patch to MavenArchetypeMojo.java provides a project description
> parameter in addition to project groupId, artifactId, and version:
> $ mvn -X archetype:create
> -DgroupId=foo
> -DartifactId=bar
> -Dversion=1.0-SNAPSHOT
> -Ddescription="bar description." ...
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
