Java “constant string too long” compile error. Only happens using Ant, not when using Eclipse

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP



Java “constant string too long” compile error. Only happens using Ant, not when using Eclipse



I have a few really long strings in one class for initializing user information. When I compile in Eclipse, I don't get any errors or warnings, and the resulting .jar runs fine.



Recently, I decided to create an ant build file to use. Whenever I compile the same class with ant, I get the "constant string too long" compile error. I've tried a number of ways to set the java compiler executable in ant to make sure that I'm using the exact same version as in Eclipse.



I'd rather figure out how to get the same successful compile I get in Eclipse in Ant than try to rework the code to dynamically concatenate the strings.





your string is too long, as you may realize. as a hack you can split it into multiple strings in your source code and concatenate them. this is what the eclipse java compiler is doing on your behalf.
– Ron
Feb 23 '11 at 21:54




9 Answers
9



Someone is trying to send you a message :-) In the time you've spend fiddling with compiler versions you could have loaded the data from a text file - which is probably where it belongs.



Check out:



I found I could use the apache commons lang StringUtils.join( Object ) method to solve this.


public static final String CONSTANT = org.apache.commons.lang.StringUtils.join( new String
"This string is long",
"really long...",
"really, really LONG!!!"
);





I find this a relly neat solution when I need to test something quickly
– Miki
Jun 1 '16 at 10:41





Thank you,You save my day :)
– Hamid
Nov 24 '16 at 17:49





I realised that this answer doesn't really answer the original posters question, it is only a workaround. I wouldn't recommend it for production code, only for quick and dirty testing purposes.
– mrswadge
Sep 19 '17 at 16:53



The length of a string constant in a class file is limited to 2^16 bytes in UTF-8 encoding, this should not be dependent on the compiler used. Perhaps you are using a different character set in your ant file than in eclipse, so that some characters need more bytes than before. Please check the encoding attribute of your javac task.


encoding


javac



Another trick, if I'm determined to put a long string in the source, is to avoid the compiler detecting it as a constant expression.


String dummyVar = "";
String longString = dummyVar +
"This string is longn" +
"really long...n" +
"really, really LONG!!!";



This worked for a while, but if you keep going too far the next problem is a stack overflow in the compiler. This describes the same problem and, if you're still determined, how to increase your stack - the problem seems to be the sheer size of the method now. Again this wasn't a problem in Eclipse.



Did you try this? Never tried it myself, but here is the relevant section:



Using the ant javac adapter
The Eclipse compiler can be used inside an Ant script using the javac adapter. In order to use the Eclipse compiler, you simply need to define the build.compiler property in your script. Here is a small example.


<?xml version="1.0" encoding="UTF-8"?>
<project name="compile" default="main" basedir="../.">

<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter"/>

<property name="root" value="$basedir/src"/>

<property name="destdir" value="d:/temp/bin" />

<target name="main">
<javac srcdir="$root" destdir="$destdir" debug="on" nowarn="on" extdirs="d:/extdirs" source="1.4">
<classpath>
<pathelement location="$basedir/../org.eclipse.jdt.core/bin"/>
</classpath>
</javac>
</target>
</project>



I would really consider making your classes standards compatible. I believe the official limit is 65535, and the fact that Eclipse is more lenient is something that could change on you at the most inconvenient of times, and either way constantly having to get the project compiled with Eclipse can really start to limit you in too many ways.


String theString2 = IOUtils.toString(new FileInputStream(new
File(rootDir + "/properties/filename.text")), "UTF-8");





Add some details/explanation?
– Victor Polevoy
Jul 20 '15 at 9:39



Add your string to values/strings.xml than call getResources.getString(R.string.yourstring)



Nothing of above worked for me. I have created one text file with name test.txt and read this text file using below code


String content = new String(Files.readAllBytes(Paths.get("test.txt")));



You can try this,


public static final String CONSTANT = new StringBuilder("Your really long string").toString();





This would have same problem of a string constant that is too long.
– Nicko
Aug 21 at 7:36






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Popular posts from this blog

Firebase Auth - with Email and Password - Check user already registered

Dynamically update html content plain JS

Store custom data using WC_Cart add_to_cart() method in Woocommerce 3