maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "G Fernandes (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (ARCHETYPE-347) Allow fields like scm, developers, licenses, etc to be set when generating an archetype
Date Thu, 11 Nov 2010 14:00:04 GMT

     [ http://jira.codehaus.org/browse/ARCHETYPE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

G Fernandes updated ARCHETYPE-347:
----------------------------------

    Attachment: archertype.patch

This patch allow setting in archetype.properties values for description, url. In case they
are not specified, the values are being taken from the project itself. The patch also fills
in values for licenses, developers, and SCM, all taken from the originating project. The patch
makes it possible to close and release a staging repository that has pom validation turned
on in Nexus Pro.

> Allow fields like scm, developers, licenses, etc to be set when generating an archetype
> ---------------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-347
>                 URL: http://jira.codehaus.org/browse/ARCHETYPE-347
>             Project: Maven Archetype
>          Issue Type: New Feature
>          Components: Creator
>            Reporter: Paul Gier
>         Attachments: archertype.patch
>
>
> Currently a generated archetype only sets basic fields like the groupId, artifactId,
etc.  There should be options to set generated values for all POM fields.

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

        

Mime
View raw message