maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Gniza (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-661) Build Path getting corrupted after maven clean install
Date Sat, 03 Jul 2010 11:50:33 GMT


Benjamin Gniza commented on MECLIPSE-661:

*Note: I am not involved in this plugin, I am also only a user.*

AFAIK this problem doesn't have to do anything with the position of the JRE. The problem is
that Eclipse doesn't like you to touch the generated classes outside of the IDE. Usually it
helps to just clean the project to get Eclipse running again. From the Menu select "Project"->"Clean",
select your project and press "Ok".
Changing the position of the JRE causes a recompile to, but the position of the JRE is not
the cause for this problem..

> Build Path getting corrupted after maven clean install
> ------------------------------------------------------
>                 Key: MECLIPSE-661
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: Core : Dependencies resolution and build path (.classpath)
>         Environment: Production
>            Reporter: prateek
>            Priority: Critical
> After doing the maven clean install on the project,
> In the Eclipse Build Path for the project, the JRE System Library is pushed down to the
Bottom and due to which we are getting compile time errors. After manually pushing the JRE
to in the Build Path / Order and Export Tab.
> The compile issues are getting resolved.
> I have done lot of research to look for a way to make sure the JRE Library Stays on Top,
> But i vain. Can somebody help me out

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message