You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2012/11/14 01:49:18 UTC
[jira] (MNG-4733) project.build.directory should be settable by
default
[ https://jira.codehaus.org/browse/MNG-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-4733.
------------------------------
Resolution: Won't Fix
> project.build.directory should be settable by default
> -----------------------------------------------------
>
> Key: MNG-4733
> URL: https://jira.codehaus.org/browse/MNG-4733
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.2.1
> Reporter: Joseph Walton
> Priority: Minor
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: target-dir.diff
>
>
> I'd like to be able to use a different target directory for projects without having to edit their poms directly. I can set project.build.directory in my parent pom but would also like to be able to make the change when building third-party projects.
> I have two use cases.
> 1. A temporary build that doesn't affect the target directories used by Eclipse
> e.g. mvn -Dtarget.dir=target.tmp test
> 2. A complete build outside the source tree of a multi-module project
> e.g. mvn -Dtarget.dir=/tmp/build/\${project.artifactId} test
> I attach a simple patch to the superpom that allows this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira