Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Eclipse Problems view showing old compile errors

Have you checked the maven compiler settings? By default, maven-compiler-plugin is configured for Java 1.5. If you have @override annotations on methods implementing an interface, which is valid in Java 1.6 IIRC, but the compiler in eclipse is set to 1.5, that might explain these errors.

On Mon, Feb 27, 2012 at 6:49 PM, Stein, Eric <steine@xxxxxxxxxxxx> wrote:

Yes and Yes. Hopefully that's correct.

 

Thanks,

Eric

 

 

From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Fred Bricon
Sent: Monday, February 27, 2012 12:44 PM
To: Maven Integration for Eclipse users mailing list


Subject: Re: [m2e-users] Eclipse Problems view showing old compile errors

 

Do you have Project > "Build automatically" checked?

On your projects, do you have Properties > "Resolve dependencies from workspace projects" checked?

 

Regards,

 

Fred Bricon

On Mon, Feb 27, 2012 at 6:40 PM, Stein, Eric <steine@xxxxxxxxxxxx> wrote:

I do. I've tried refreshing, cleaning, cleaning and rebuilding all,
validating, restarting eclipse, restarting the computer. I've tried mvn
-e clean package install on both projects. None of these things has
worked.

Eric


-----Original Message-----
From: Igor Fedorenko [mailto:igor@xxxxxxxxxxxxxx]
Sent: Monday, February 27, 2012 11:15 AM
To: m2e-users@xxxxxxxxxxx
Subject: Re: [m2e-users] Eclipse Problems view showing old compile
errors

Do you still get the errors after you refresh project sources from local
filesystem and do clean build?

--
Regards,
Igor

On 12-02-27 10:14 AM, Stein, Eric wrote:
> I have a couple of Maven projects in Eclipse, and I'm running m2e.
> I've noticed that sometimes compile errors last beyond when they
> should in the Eclipse Problems view. For instance, if I have an
> interface in project 1 and an implementation in project 2, if I add a
> method with @Override first to the implementation and then put the
> signature in the interface, errors pop up in Problems. I then did mvn
> -e clean package install on both projects, and they build cleanly with

> no errors. The two errors "The method XXX must override a superclass
> method" are still in the Problems view. I also tried an Eclipse clean
> and rebuild, but that did nothing.
>
> This isn't stopping me from working, but it is pretty annoying. Does
> anybody have any idea what might be causing the stale errors to
remain?
> I'm happy to provide any further information if it would help.
>
> Thanks,
> Eric
>
> _________________________________________________
> Don't gamble with your environmental information. Learn how the
world's largest on-demand environmental information management system
can help you mitigate your operating risk: www.locustec.com.
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users

_________________________________________________
Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users



 

--
"Have you tried turning it off and on again" - The IT Crowd

_________________________________________________
Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users




--
"Have you tried turning it off and on again" - The IT Crowd

Back to the top