Eclipse compile errors [0.4.0]

[Ward Harold <wk...@gmail.com>]

Abdera 0.4.0 builds fine on my Mac with the latest version of Maven. When I
import it into Eclipse, however, I get two compile errors in the
abdera-parser project. In FOMElement.java I get:

The return type is incompatible with Element.setText(String),
OMElementImpl.setText(String)


and in FOMProcessingInstruction I get:


The return type is incompatible with
ProcessingInstruction.setTarget(String),
OMProcessingInstructionImpl.setTarget(String)


It appears that the source of the problem is that setText/setTarget are
defined in different ways in the one of the super classes and an interface
being implemented. The batch compiler may be letting something go that the
Eclipse compiler objects to - I've always understood that differing return
types isn't enough to distinguish two methods.

-- 
... WkH

Re: Eclipse compile errors [0.4.0]

[David Calavera <da...@gmail.com>]

mmm I thought I was fixed it, I'll take a look tonight, thank you.

On Tue, Jan 13, 2009 at 1:54 AM, Ward Harold <wk...@gmail.com> wrote:

> Abdera 0.4.0 builds fine on my Mac with the latest version of Maven. When I
> import it into Eclipse, however, I get two compile errors in the
> abdera-parser project. In FOMElement.java I get:
>
> The return type is incompatible with Element.setText(String),
> OMElementImpl.setText(String)
>
>
> and in FOMProcessingInstruction I get:
>
>
> The return type is incompatible with
> ProcessingInstruction.setTarget(String),
> OMProcessingInstructionImpl.setTarget(String)
>
>
> It appears that the source of the problem is that setText/setTarget are
> defined in different ways in the one of the super classes and an interface
> being implemented. The batch compiler may be letting something go that the
> Eclipse compiler objects to - I've always understood that differing return
> types isn't enough to distinguish two methods.
>
> --
> ... WkH
>



-- 
David Calavera
http://www.thinkincode.net