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 2007/05/31 22:00:58 UTC
[jira] Closed: (MNG-2347) MavenExecutionRequest.getBaseDirectory()
should be propagated to the ${basedir} expression
[ http://jira.codehaus.org/browse/MNG-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2347.
------------------------------
Resolution: Fixed
Patch applied.
> MavenExecutionRequest.getBaseDirectory() should be propagated to the ${basedir} expression
> ------------------------------------------------------------------------------------------
>
> Key: MNG-2347
> URL: http://jira.codehaus.org/browse/MNG-2347
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
> Affects Versions: 2.0-alpha-1
> Environment: Maven 2.1-SNAPSHOT
> Reporter: Ovidio Mallo
> Assignee: Jason van Zyl
> Fix For: 2.1-alpha-1
>
> Attachments: MNG-2347-maven-core.patch
>
>
> When executing a goal given by a MavenExecutionRequest (e.g. on the MavenEmbedder) which has no POM file set (e.g. archetype:create), the MavenExecutionRequest.getBaseDirectory() is not propagated to the expression ${basedir} for the plugins to be used.
> Currently, the ${basedir} is set to the directory where the POM file resides, if any is specified. Otherwise, it is simply set to the current working directory. I guess that when no POM file is given, ${basedir} should be set to the base directory set on the MavenExecutionRequest.
--
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