wrote:
On 2012-04-23, Lokesh Jain wrote:
On 4/23/2012 1:53 PM, Stefan Bodewig wrote:
On 2012-04-21, Lokesh Jain wrote:
But on a CentOS box, the same property is read by the task program
along with some junk unicode chars. Consequently, the strings do not
match which affects some of the intern
On 4/23/2012 1:53 PM, Stefan Bodewig wrote:
On 2012-04-21, Lokesh Jain wrote:
But on a CentOS box, the same property is read by the task program
along with some junk unicode chars. Consequently, the strings do not
match which affects some of the internal logic of the ant task.
What is &quo
I doubly checked, the build.properties file is encoded in ISO 8859-1 for
both Windows and Linux installations. For a consistent check, I used
Mozilla Firefox -> View Page Info option.
-Lokesh
On 4/22/2012 10:26 PM, Stefan Bodewig wrote:
On 2012-04-21, Lokesh Jain wrote:
Thank you for y
ded in ISO 8859-1 character encoding.
Characters that cannot be directly represented in this encoding can be
written using Unicode escapes as defined in section 3.3 of The
Java^(TM) Language Specification;
Jarek
W dniu 04/21/2012 10:01 AM, Lokesh Jain pisze:
Hi,
I have a custom ant task whic
Forgot to mention...
If instead of using build.properties file, I directly add the property
like -DAPPLICATION_GUID=HELLOÀÁÂ, it works even in the CentOS box.
However, I would still like to be able to do this with the properties
file for obvious reasons.
-Lokesh
On 4/21/2012 1:31 PM, Lokesh
Hi,
I have a custom ant task which reads certain properties from
build.properties and exports applications based on that.
name="exportApplication" classpathref="proj.lib"/>
applicationVersion="${APPLICATION_VERSION}"
exportLocation="${APPLICATION_EXPORT_DIR}"/>
Th
