ansaurus

Question

Code compiling in eclipse but not on command line

Answer 1

A:

Hard to say from what's provided, but guesses are

Different JVM in Eclipse than command line.
Bad classpath settings in command line.

What are the compile errors?

Can you isolate the problem in a dummy class for demonstration?

Joe Skora 2008-09-22 15:53:37

Answer 2

+2 A:

Hard to tell why you have command line compilation errors, but ...

Since you have an awful lot of "magic numbers", there may be a better approach than hardcoding an array literal.

Consider

Using a static initializer block to initialize an List
Reading an XML file that will have your numbers, and using your class that reads the XML to return the datatype you want (be it a List or byte[]

Alan 2008-09-22 15:59:03

Answer 3

+3 A:

What you have seems to compile.

If possible, I would suggest trying to embed the resource in the Jar and using ClassLoader.getResourceAsStream().

Steve g 2008-09-22 16:05:24

Answer 4

+1 A:

Providing the exact error message would help us to help you too...
And I wonder why you hard-code an image (icon) in the source, instead of using some form of resource.

PhiLho 2008-09-22 16:05:49

Answer 5

A:

if you are on windows write

set JAVA_HOME=C:\Program Files.... path to JDK the path should be the jdk path not jre on my PC is C:\Program Files\Java\jdk1.6.0_07

WARNING : THE PATH SHOULD NOT BE NOT SURROUNDED BY QUOTES (") cmd's autocompletions puts them !

on unix like systems use

export JAVA_HOME=PATH TO JDK (quotes are tolerated)

andreasmk2 2008-09-22 16:13:48

Answer 6

+3 A:

Taking from this forum on Sun's support site, no method can be more than 64 KB long:

When you have code (pseudo) like the following...

class MyClass
{
  private String[] s = { "a", "b", "c"}

  public MyClass()
  {
  }

The compiler ends up producing code that basically looks like the following.

class MyClass
{
  private String[] s;

  private void FunnyName$Method()
  {
    s[0] = "a";
    s[1] = "b";
    s[2] = "c";
  }
  public MyClass()
  {
    FunnyName$Method();
  }

And as noted java limits all methods to 64k, even the ones the compiler creates.

It may be that Eclipse is doing something sneaky to get around this, but I assure you this is still possible in Eclipse because I have seen the same error message. A better solution is to just read from a static file, like this:

public class Icons
{
  public static final byte[] compileIcon;
  static
  {
    compileIcon = readFileToBytes("compileIcon.gif");
  }
  //... (I assume there are several other icons)
  private static byte[] readFileToBytes(String filename)
  {
    try {
      File file = new File(filename);
      byte[] bytes = new byte[(int)file.length()];
      FileInputStream fin = new FileInputStream(file);
      fin.read(bytes);
      fin.close();
    }
    catch (Exception e) {
      e.printStackTrace();
      System.exit(1);
    }
  }
}

Kip 2008-09-22 17:15:14

Answer 7

A:

Are you sure your commandline and eclipse are using same version of Java compiler and same compile setting? To find you what version of Java you are using in command line type: Java -version

Alvin 2008-10-01 01:32:53

Answer 8

+3 A:

Eclipse has it's own compiler. The Eclipse JDT compiler seems to handle your array differently than javac.

ILikeCoffee 2008-10-05 14:04:37

ansaurus

tags:

views:

answers:

Code compiling in eclipse but not on command line

related questions