[jira] (MNG-2598) profile element in POM should support overriding project.build.directory

["Paul Benedict (JIRA)" <ji...@codehaus.org>]

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

Paul Benedict updated MNG-2598:
-------------------------------

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

> profile element in POM should support overriding project.build.directory
> ------------------------------------------------------------------------
>
>                 Key: MNG-2598
>                 URL: https://jira.codehaus.org/browse/MNG-2598
>             Project: Maven
>          Issue Type: Improvement
>          Components: Profiles
>    Affects Versions: 2.0.4
>            Reporter: Ian Springer
>
> I am trying to set up a 'dev' build profile that, when enabled, will cause my j2ee artifacts to be built directly to exploded j2ee deployment dirs, instead of target/classes/. The purpose is to make the everyday development process more efficient by skipping a number of time-consuming intermediate mvn steps (i.e. jarring artifacts, copying the jars to the local repo, then unjarring the artifacts to their deploy locations).
> The intuitive way to achieve this is to override 'project.build.directory' and/or 'project.build.outputDirectory' in a profile; e.g.:
> <profile>
> ...
>  <build>
>   <outputDirectory>${jboss.home}/server/default/deploy/my.ear/my-exploded-ejb.jar
>  </build>
> ...
> </profile>
> Unfortunately, profiles currently do not allow one to override either 'project.build.directory' or 'project.build.outputDirectory'. Please change Maven to allow profiles to override these props. Otherwise, I can't see any other way to achieve what my team needs to do to have a practical build/dev infrastructure.
> Thanks,
> Ian



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