[ 
http://jira.codehaus.org/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227236#action_227236
 ] 

prateek commented on MECLIPSE-661:
----------------------------------

Benjamin, I have tried the option that you told. I first clean the project to 
make sure the compile errors get resolved. But its not solving the problem. The 
problem is solved only when the JRE is being pushed to the top of the chart 
manually. The reason for being JRE at the bottom of the build path is the 
.classpath generated by the maven project. If we can have tweak there in class 
path we can resolve the issue

> Build Path getting corrupted after maven clean install
> ------------------------------------------------------
>
>                 Key: MECLIPSE-661
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-661
>             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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to