Eclipse Community Forums: Java Development Tools (JDT) » [Eclipse Compiler] Differences IDE vs headless build

Home

Home » Language IDEs » Java Development Tools (JDT) » [Eclipse Compiler] Differences IDE vs headless build

[Eclipse Compiler] Differences IDE vs headless build [message #644398]

Fri, 10 December 2010 17:01

Eclipse User

Hi,

We have a strange issue regarding warnings that the Eclipse Java Compiler generates in the IDE and when executing a headless build. I will show you a snippet that produces the warning:

package pkg;

public interface Foo {

    @Target(ElementType.TYPE)
    @Retention(RetentionPolicy.RUNTIME)
    public static @interface Bar {
      ....
     }
}

package pkg2;
import pkg.Foo.Bar;

@Bar
public class TestClass {
}

The compiler in the IDE is not complaining about anything but during the headless build we are getting a "unused import" warning: The import pkg.Foo.Bar is never used. But thats actually not true, because the import is used and when removed causes a compile error Smile

We are using Eclipse 3.6 for development and in the nightly build, so the versions are matching. Can anybody explain the differences and what we can do to avoid the warning?

Best regards,
Michael

Re: [Eclipse Compiler] Differences IDE vs headless build [message #644555 is a reply to message #644398]

Mon, 13 December 2010 04:32

Eclipse User

I don't see any problem if I use the following command line
%java -jar c:\ecj.jar -source 5 -classpath "." pkg2\TestClass.java

Note the options 'source 5' tells to assume the source code is in 1.5 mode and by specifying the 'classpath', the compiler knows where to search for the packages.

Previous Topic:	Why does eclipse try to compile all other open projects when I run a unit test
Next Topic:	Java extension and java.g file grammar

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 02 10:31:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter