[ http://jira.codehaus.org/browse/MECLIPSE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158463#action_158463 ]
Richard van Nieuwenhoven commented on MECLIPSE-415: --------------------------------------------------- This request was on a far to short notice, and at the moment i do not have the time to check if the trunk still has this behavior. Please make sure in your test to use a multi module hierarchical project, they are the ones with the most problems ;-) And also please look into my note for Arnaud to remove unreachable codes, the plugin is complicated as it is. > settings stored in wrong project directory > ------------------------------------------- > > Key: MECLIPSE-415 > URL: http://jira.codehaus.org/browse/MECLIPSE-415 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath), Core : Workspace settings > Affects Versions: 2.5, 2.5.1 > Environment: all > Reporter: Richard van Nieuwenhoven > Assignee: Barrie Treloar > Fix For: 2.6 > > Attachments: executedProject.patch, pom.xml > > > When i store my projects in a directory which isn't my eclipse workspace. > If I define the workspace attribute to be able to read its settings, > when I call eclipse:eclipse, my projects settings are written in the > workspace and not in each project's directory. > this problem seems to be connected to the wrongly used executedProject > parameter and maven 2.0.9.. > the wrong directory problem can be solved by giving the eclipseProjectDir a > default value ${basedir} . > Arnaud: i think you can safely remove much of the code in > EclipsePlugin.validate method where the eclipseProjectDir does not exist or > !eclipseProjectDir.equals( project.getBasedir() ) these cases will almoust > never work anymore (only for very very simple eclipse projects), and it is > certainly discouraged. > in the attached patch i have included the removal of the executedProject > parameter but not the code mentioned above, the strange thing i did not have > the time to solve is that "testProject11" now fails (it survived the default > value but not the removal of the executedProject parameter) -- 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