You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "prateek (JIRA)" <ji...@codehaus.org> on 2010/06/24 11:40:12 UTC
[jira] Created: (MECLIPSE-661) Build Path getting corrupted after
maven clean install
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
[jira] Commented: (MECLIPSE-661) Build Path getting corrupted after
maven clean install
Posted by "prateek (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MECLIPSE-661) Build Path getting
corrupted after maven clean install
Posted by "Benjamin Gniza (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227113#action_227113 ]
Benjamin Gniza edited comment on MECLIPSE-661 at 7/3/10 6:50 AM:
-----------------------------------------------------------------
*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 too, but the position of the JRE is not the cause for this problem..
was (Author: benjamin.gniza):
*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: 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
[jira] Commented: (MECLIPSE-661) Build Path getting corrupted after
maven clean install
Posted by "Benjamin Gniza (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227113#action_227113 ]
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: 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