[ 
https://jira.codehaus.org/browse/MNG-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Benedict updated MNG-2086:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Support writing all generated output to a different filesystem base to that 
> of the project files (i.e. all non generated files)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2086
>                 URL: https://jira.codehaus.org/browse/MNG-2086
>             Project: Maven
>          Issue Type: Improvement
>          Components: Reactor and workspace
>            Reporter: John Allen
>
> It is a useful and powerful feature for a build system to support using a 
> different base directory for all generated output. This enables the project 
> source (pom et al) to be accessed from read-only or networked location and 
> for all generated output to be written to a local filesystem location. 
> Currently maven will write all generated output locations relative to the 
> project and although this can be ovverriden via build-directory on a per 
> project basis (ignoring the outstanding JIRA re this not working) it would be 
> better if maven could be given a new output directory root for all generated 
> output and have it replicate the project structure as required...
> E.g.:
> \mnt\dev\projects\A
> \mnt\dev\projects\A\src\...
> \mnt\dev\projects\A\B
> \mnt\dev\projects\A\B\src\...
> maven.build-root = \home\developer\dev
> Results in:
> \home\developer\dev\projects\A
> \home\developer\dev\projects\A\target\...
> \home\developer\dev\projects\A\B
> \home\developer\dev\projects\A\B\target\...



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to