maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "tom nelson (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (ARCHETYPE-139) cannot create archetype for existing project without pre-existing pom
Date Tue, 26 Feb 2008 14:37:28 GMT
cannot create archetype for existing project without pre-existing pom
---------------------------------------------------------------------

                 Key: ARCHETYPE-139
                 URL: http://jira.codehaus.org/browse/ARCHETYPE-139
             Project: Maven Archetype
          Issue Type: Bug
          Components: Generator
    Affects Versions: 2.0-alpha-2
            Reporter: tom nelson


Unlike 1.0, the 2.0-alpha-2 version will not allow users to create a new archetype (e.g. a
new pom file) for an existing project. In DefaultFilesetArchetype.java, If the archetype is
'partial', and the project directory already exists, then the pom must already exist or an
exception is thrown. If the archetype is not partial, and the project directory already exists,
then a ProjectDirectoryExists exception is thrown.

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