[
https://issues.apache.org/jira/browse/EASYANT-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Enderling updated EASYANT-53:
---------------------------------
Attachment: EASYANT-53-Easyant-batch-file-shell-script-will-allo.patch
The attached patch is based on the current trunk (SVN revision 1480665).
It addresses the issue by the following changes:
* Adding the property {{easyant.home}} to {{EASYANT_OPTS}} instead of
{{EASYANT_ARGS}} (similar to what is done with ANT_HOME) so it is available as
Java System property (and it can be read before the project has been
intialized).
* Removing of passing in a {{-configfile}} option in the shell/batch script.
* In EasyAntMain use the {{configfile}} option, if given, otherwise fall back
to {{<easyant.home>/easyant-conf.xml}}, if it exists to find an EasyAnt config
file to load (or load none if neither of the two applies).
> Option -configfile ignored when starting EasyAnt through easyant.bat/easyant
> shell-script
> -----------------------------------------------------------------------------------------
>
> Key: EASYANT-53
> URL: https://issues.apache.org/jira/browse/EASYANT-53
> Project: EasyAnt
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9
> Reporter: Tim Enderling
> Attachments:
> EASYANT-53-Easyant-batch-file-shell-script-will-allo.patch
>
>
> Both easyant.bat and the easyant shell script add a {{-configfile}} option
> pointing to {{<EASYANT_HOME>/easyant-conf.xml}} to {{EASYANT_ARGS}} and pass
> it to {{EasyAntMain}}.
> This way it is impossible for someone calling the batch file/shell script to
> pass a custom {{-configfile}} option (the value
> {{<EASYANT_HOME>/easyant-conf.xml}} will always win. This is a major drawback
> when using different {{easyant-conf.xml}} (like with different sets of system
> plugins) as the only workarounds are to either copy/link
> {{<EASYANT_HOME>/easyant-conf.xml}} from these different files or write a
> custom batch file/shell script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
