<executable> path is not relative to 'current' project in multi-module project
------------------------------------------------------------------------------
Key: MEXEC-36
URL: http://jira.codehaus.org/browse/MEXEC-36
Project: Maven 2.x Exec Plugin
Issue Type: Bug
Affects Versions: 1.1-beta-1
Environment: Maven 2.0.7, Windows
Reporter: Maarten Brugman
I have a configuration that runs fine with exec-maven-plugin v1.0.2, but fails
with version 1.1-beta1.
In 1.0.2, the <executable> path is relative to the 'current' project in a
multi-module project.
E.g. I have a multi-module project, with a sub-project 'ear' that runs a batch
file ear/target/install.bat.
I refer to this batch file with <executable>target/install.bat</executable>.
This works fine in 1.0.2, both when I run maven in the main project directory
and when I run maven in the 'ear' sub-project directory.
It does not work in 1.1-beta-1 when I run it in the main project directory: '
BUILD ERROR - system cannot find the path specified'.
It seems that the 1.1-beta-1 version uses the current working dir as the
starting point for the <executable> path.
In my humble opinion, verison 1.0.2 did the right thing: use the working dir of
the maven project at hand as the starting point.
I hope I made my point clear; if any questions remain, feel free to e-mail me
at maartenbrugman at-sign gmail ddott com.
By the way, thanks for donating this useful plugin to the community!
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
