[ http://jira.codehaus.org/browse/MECLIPSE-145?page=all ]
Kenney Westerhof closed MECLIPSE-145.
-------------------------------------
Resolution: Won't Fix
The plugin also supports -Declipse.workspace=path/to/workspace.
The plugin will NOT create any workspaces - the directory must already exist.
Eclipse workspaces are tied to the eclipse version using them. When you upgrade
they're
automatically converted, and we can't build in support for all eclipse versions
for creating workspaces.
Just creating that directory and then running mvn eclipse:eclipse
-Declipse.workspace=DIR, then fire up eclipse
with -data DIR does exactly what you want.
For safety reasons, the eclipse plugin won't create that directory
automatically.
> Add support for building Eclipse workspaces
> -------------------------------------------
>
> Key: MECLIPSE-145
> URL: http://jira.codehaus.org/browse/MECLIPSE-145
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Reporter: Curt Cox
>
> The ability to generate Eclipse project files is very handy:
> mvn eclipse:eclipse
> After this is done, the developer launches Eclipse and imports the project
> created into the Eclipse workspace. It would be more convenient, if the
> workspace was built for the developer. Many developers are already in the
> habit of explicitly specifying a workspace to Eclipse via the -data option.
> So, the developer would use something like:
> mvn eclipse:data
> eclipse -data workspace
> This would create an Eclipse workspace with separate projects for main and
> test, then launch Eclipse.
> One of the main reasons to use the -data option to specify a workspace is so
> that one can easily switch between different Eclipse releases. Is there any
> reason why Maven can't manage Eclipse releases. After all, if the project is
> developed with Eclipse, then Eclipse is a dependency. So, then how about:
> mvn eclipse:start
> Which would start Eclipse specifying the appropriate project workspace. If
> the workspace didn't exist, it would be created.
--
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
