[
https://jira.codehaus.org/browse/MEXEC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MEXEC-92.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.2.1
Assignee: Robert Scholte
Fixed in [rev. 14647|http://fisheye.codehaus.org/changelog/mojo/?cs=14647]
> The plugin behaves unexpected when a file or a directory exist in the top
> level directory that has the same name as the given executable
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MEXEC-92
> URL: https://jira.codehaus.org/browse/MEXEC-92
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Components: exec
> Affects Versions: 1.2
> Environment: n/a
> Reporter: Gerhard Dünnebeil
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 1.2.1
>
>
> The exec plugin -- when confronted with an executable that has no path --
> tries to resolve this as a first attempt by looking into the root directory
> of the maven project.
> If a file exists, ie. if a java File object constructed upon that name gives
> back true for the "exists" method, that path is used to start the executable.
> The following issues arise with that:
> 1. This is not compatible with the documentation which gives NO hint at all
> to that behavior
> 2. If the file is not executable (e.g. it is a directory) you will get an
> error message.
> 3. This might not be the behavior you want
> The following solution(s) are proposed:
> 1. Change that behavior so that an explicit path of ./<name> is required for
> a local executable
> 2. Check whether the file is executable before choosing it
> 3. Add debug output (to be visible with mvn -X) to make that behavior visible
> and to make troubleshooting a bit easier
> 4. Add an explicit hint to that behavior in the documentation
--
This message is automatically generated by JIRA.
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
