Patch: failIfNoClass adds the ability to disable failing if no class was found,
as well as a better error message
-----------------------------------------------------------------------------------------------------------------
Key: MEXEC-43
URL: http://jira.codehaus.org/browse/MEXEC-43
Project: Maven 2.x Exec Plugin
Issue Type: New Feature
Affects Versions: 1.1-beta-1
Reporter: Joshua Pollak
Attachments: failIfNoClass.patch
exec:java is pretty much useless to execute main classes in multi-module
projects (without first installing) because the exec:java command can't be run
from the top level pom because it will fail with class not found, and when run
from the correct module it will fail because it can't locate the dependancies.
This patch adds the ability to disable the 'fail if class not found' behavior
via the 'failIfNoClass' property. If set to false the plugin will NOT fail if
the Java class specified is not found. This is useful in a multi-module project
where you might want to exec a class in one module which won't be found in
other modules.
The default value of failIfNoClass is TRUE, which preserves the current
behavior.
This patch also adds a constructive error in the case where failIfNoClass is
true, and no class is found. In the past, just the string "null" was displayed.
--
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
