[
https://issues.apache.org/jira/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-661.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Build Path getting corrupted after maven clean install
> ------------------------------------------------------
>
> Key: MECLIPSE-661
> URL: https://issues.apache.org/jira/browse/MECLIPSE-661
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
