Hi,
wicket-examples 2.0 (trunk) module fails to compile using maven and standard
javac compiler (however, eclipse compiler doesn't complain):
[INFO]
[ERROR] BUILD FAILURE
[INFO]
thx fix it.
strange that compilers are that different. should be a setting then
somewhere in eclipse.
johan
On 12/18/06, Martin Benda [EMAIL PROTECTED] wrote:
Hi,
wicket-examples 2.0 (trunk) module fails to compile using maven and
standard
javac compiler (however, eclipse compiler doesn't
Yes, the Eclipse and Sun compiler differ quite annoyingly in how they
treat casts that have a generic component. Unfortunately this is not a
setting.
There are more differences. For example JRockit behaves weird around
warnings for deprecated methods.
Regards,
Erik.
Johan Compagner
18.12.2006 14:15
An: wicket-dev@incubator.apache.org
Betreff: Re: wicket-examples compilation failure
On 12/18/06, Martin Benda [EMAIL PROTECTED] wrote:
Hi,
wicket-examples 2.0 (trunk) module fails to compile using maven and standard
javac compiler (however, eclipse compiler doesn't complain):
Hello
Agh! Two typos! I mean Java 1.5.0_10.
Von: Stefan Lindner [mailto:[EMAIL PROTECTED]
Gesendet: Mo 18.12.2006 14:39
An: wicket-dev@incubator.apache.org; wicket-dev@incubator.apache.org
Betreff: AW: wicket-examples compilation failure
Maybe you should use
Hi!
This is strange - I don't get any compilation error in the wicket module,
nor do I see any error in WebPage.java:169 or Loop.java:167:
WebPage:
public final HeaderContainer getHeaderContainer()
{
return (HeaderContainer)get(HtmlHeaderSectionHandler.HEADER_ID);
}
Loop:
// Get item
On 12/18/06, Stefan Lindner [EMAIL PROTECTED] wrote:
Agh! Two typos! I mean Java 1.5.0_10.
Yes... I had 1.5.0_06, and it didn't work; now I'm using the latest
release (1.5.0_10-b3) and it's building correctly.
Thanks everybody
--
filippo
