[
http://jira.codehaus.org/browse/MECLIPSE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar updated MECLIPSE-415:
------------------------------------
Attachment: pom.xml
Here are the steps I followed (I am using Eclipse 3.2.2) and show that I can't
replicate what I think the problem is:
# Create a new workspace
** File > Switch Workspace...
** Browse
** Make new Folder C:\MECLIPSE-415-workspace
** Select and click Ok
# Configure the eclipse workspace
** set the M2_REPO variable
** set the Java > Compiler > Compiler compliance level to 1.4
# Checkout maven-eclipse-plugin trunk
** Window > Open Perspective > Other
** select SVN Repository Exploring
** right click in the SVN Repository view and select New > Repository
Location...
** Use Url
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
** Click finish
** Right click the new location and select Checkout...
** Select "Check out as a project in the workspace"
** Use default "maven-eclipse-plugin" as Project Name
** Click Finish
# Build maven-eclipse-plugin
** Open a command shell in C:\MECLIPSE-415-workspace\maven-eclipse-plugin
** run mvn install
** run mvn eclipse:eclipse
** Switch to the Java perspective
** Refresh the maven-eclipse-plugin project (it should now be a Java project)
# Create the test project
** From windows explorer create the directory C:\MECLIPSE-415
** Copy the attached pom.xml into the directory.
** Run mvn eclipse:eclipse (note the console output [INFO] Wrote settings to
C:\MECLIPSE-415\.settings\org.eclipse.jdt.core.prefs)
# Import the test project into eclipse
** File > Import
** General > Existing Projects into Workspace
** Select C:\MECLIPSE-415 as root directory
** Ensure MECLIPSE-415 is selected as a project to import
** Click Finish
# Verify settings have been imported
** Right click the MECLIPSE-415 project and select properties
** Select Java Compiler
** Verify that Compiler compliance level is 5.0 (different to workspace)
> 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: Arnaud Heritier
> 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
