[jira] Updated: (ARCHETYPE-323) FilesetArchetypeCreator.getGeneratedSourcesDirectory() returns hardcoded directory

["Herve Boutemy (JIRA)" <ji...@codehaus.org>]

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

Herve Boutemy updated ARCHETYPE-323:
------------------------------------

    Fix Version/s: 2.0-alpha-6

> FilesetArchetypeCreator.getGeneratedSourcesDirectory() returns hardcoded directory
> ----------------------------------------------------------------------------------
>
>                 Key: ARCHETYPE-323
>                 URL: http://jira.codehaus.org/browse/ARCHETYPE-323
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Creator
>    Affects Versions: 2.0-alpha-5
>            Reporter: Michael Bruns
>            Priority: Minor
>             Fix For: 2.0-alpha-6
>
>
> The method {{FilesetArchetypeCreator.getGeneratedSourcesDirectory()}} always returns the hardcoded value {{"target" + File.separator + "generated-sources" + File.separator + "archetype"}}. Thus setting a different value for {{outputDirectory}} or {{${project.build.directory}}} doesn't have an effect at all, even though the [documentation|http://maven.apache.org/archetype/maven-archetype-plugin/create-from-project-mojo.html#outputDirectory] says so.
> This should respect the properties set by the user. I do have a scenario in which I want to create an archetype from a project which shall be deployed in an automatic cycle, and in this case it is not useful to generate the archetype to {{target/...}}

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