Thanks, In fact my use case is a good one. I have a team of 20 developers on the same project, same eclispe workspace configuration ( ie same code style setup), and the workspace configuration is at the sameplace for all developers ( which is at the root pom level).
This works out great. ( no argument where to put the workspace ). Thank you for putting lots of works this plugin. -D On Jan 31, 2008 1:12 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > I didn't see this usage to have the eclipse workspace in the root directory > of your project. But why not ;-) > Effectively, in your case you call configure-workspace only in this > directory and not in sub-modules. > In all cases it's not normal that a bad workspace directory break the > eclipse:eclipse goal. It should work like it did before. > I thought also to add a switch parameter to say to the eclipse:eclipse goal > if it should read the workspace to find others projects or not. > I reopened the issue : http://jira.codehaus.org/browse/MECLIPSE-344 > > Arnaud > > > On Jan 31, 2008 9:57 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > On Jan 31, 2008 12:30 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > There's something I don't understand. > > > The workspace parameter used in eclipse:configure-workspace and in > > > eclipse:add-maven-repo (which now deprecated by configure-workspace) has > > to > > > point to your workspace directory of eclipse. Not your project directory > > ? > > > > I mean ${workspace} should point to directory where you want > > eclipse:configure-workspace to create eclipse's workspace directory > > (ie .metadata) It workout nicely for my team to point ${workspace} to > > ${basedir} since configure-workspace goal only works > > at the top level. > > > > > > > Generally this parameter is defined in command line or with a property > > set > > > in the user's settings (or hardcoded if all your team has the same > > > directories layout). > > > And this is the same directory that we need in eclipse:eclipse, that why > > I > > > renamed it to have the same parameter name. > > > > > > Arnaud > > > > > > > > > On Jan 31, 2008 9:14 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > > > > > I have <workspace>${basedir}</workspace> to point to the top directory > > > > of my multi module project. > > > > This element used to be recognizable ONLY by > > > > add-maven-repo/configure-workspace mojos. > > > > > > > > however, in 2.5 eclipse goal now also recorgizes it at well. Perhaps > > > > eclipse:eclipse goal should have a different mojo's field name for > > > > its own's workspace configuration? ( ie projectWorkspace ) > > > > > > > > Thanks > > > > > > > > > > > > -D > > > > > > > > > > > > On Jan 31, 2008 10:32 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > > > > > We have to document it. It's due to the workspace configuration > > > > parameter. > > > > > workspace is now recognized by the eclipse:eclipse goal to find > > others > > > > > projects : > > > > > http://jira.codehaus.org/browse/MECLIPSE-344 > > > > > it should define where is your eclipse workspace. > > > > > Why did you use it with ${basedir}? > > > > > I'll see why the goal fails if the workspace parameter is wrong. It > > > > should > > > > > warn us and ignore it. > > > > > > > > > > Arnaud > > > > > > > > > > > > > > > > > > > > > > > > > On Jan 31, 2008 6:41 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > I ran into problem during eclipse:eclipse > > > > > > > > > > > > here is my configuration > > > > > > > > > > > > <plugin> > > > > > > <artifactId>maven-eclipse-plugin</artifactId> > > > > > > <version>2.5-SNAPSHOT</version> > > > > > > <configuration> > > > > > > <workspace>${basedir}</workspace> > > > > > > <wtpversion>1.5</wtpversion> > > > > > > <workspaceCodeStylesURL> > > > > > > > > > > > > > > > > > > http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/optional/eclipse-config/maven-styles.xml > > > > > > </workspaceCodeStylesURL> > > > > > > </configuration> > > > > > > </plugin> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ======================================================================= > > > > > > here is stack trace in one of my module > > > > > > > > > > > > [INFO] Building ipl-migrate > > > > > > [INFO] task-segment: [eclipse:eclipse] > > > > > > [INFO] > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > [INFO] Preparing eclipse:eclipse > > > > > > [INFO] No goals needed for project - skipping > > > > > > [INFO] [eclipse:eclipse] > > > > > > [INFO] Adding support for WTP version 1.5. > > > > > > [ERROR] Could not read workspace JRE preferences > > > > > > java.io.FileNotFoundException: > > > > > > C:\dev\iplocks\va\ipl-migrate\.metadata\.plugins\ > > > > > > org.eclipse.core.runtime\.settings\org.eclipse.jdt.launching.prefs > > (The > > > > > > system c > > > > > > annot find the path specified) > > > > > > at java.io.FileInputStream.open(Native Method) > > > > > > at java.io.FileInputStream.<init>(FileInputStream.java:106) > > > > > > at > > > > > > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.readAva > > > > > > ilableJREs(ReadWorkspaceLocations.java:424) > > > > > > at > > > > > > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.detectD > > > > > > efaultJREContaigner(ReadWorkspaceLocations.java:191) > > > > > > at > > > > > > org.apache.maven.plugin.eclipse.reader.ReadWorkspaceLocations.init > > (Re > > > > > > adWorkspaceLocations.java:89) > > > > > > at > > > > > > > > org.apache.maven.plugin.eclipse.EclipsePlugin.getWorkspaceConfigurati > > > > > > on(EclipsePlugin.java:1343) > > > > > > at > > > > > > > > org.apache.maven.plugin.eclipse.EclipsePlugin.fillDefaultClasspathCon > > > > > > tainers(EclipsePlugin.java:1092) > > > > > > at org.apache.maven.plugin.eclipse.EclipsePlugin.setup( > > > > > > EclipsePlugin.jav > > > > > > a:662) > > > > > > at > > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute > > > > > > (AbstractId > > > > > > eSupportMojo.java:502) > > > > > > at org.apache.maven.plugin.DefaultPluginManager.executeMojo > > > > > > (DefaultPlugi > > > > > > nManager.java:447) > > > > > > at > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals > > > > > > (Defa > > > > > > ultLifecycleExecutor.java:539) > > > > > > at > > > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > > > > > > Goal(DefaultLifecycleExecutor.java:493) > > > > > > at > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > > > > > > (Defau > > > > > > ltLifecycleExecutor.java:463) > > > > > > at > > > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > > > > > > dleFailures(DefaultLifecycleExecutor.java:311) > > > > > > at > > > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > > > > > > ts(DefaultLifecycleExecutor.java:278) > > > > > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > > > > > > (DefaultLi > > > > > > fecycleExecutor.java:143) > > > > > > at org.apache.maven.DefaultMaven.doExecute( > > DefaultMaven.java > > > > :333) > > > > > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java > > :126) > > > > > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke > > > > > > (NativeMethodAccessorImpl. > > > > > > java:39) > > > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke > > > > > > (DelegatingMethodAcces > > > > > > sorImpl.java:25) > > > > > > at java.lang.reflect.Method.invoke(Method.java:585) > > > > > > at org.codehaus.classworlds.Launcher.launchEnhanced( > > > > Launcher.java > > > > > > :315) > > > > > > at org.codehaus.classworlds.Launcher.launch(Launcher.java > > :255) > > > > > > at org.codehaus.classworlds.Launcher.mainWithExitCode( > > > > Launcher.java > > > > > > :430) > > > > > > > > > > > > at org.codehaus.classworlds.Launcher.main(Launcher.java > > :375) > > > > > > [ERROR] Could not read workspace wtp server runtimes preferences : > > > > > > C:\dev\iplock > > > > > > > > > > > > > > > > > > s\va\ipl-migrate\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclip > > > > > > se.wst.server.core.prefs (The system cannot find the path > > specified) > > > > > > [INFO] Using as WTP server : null > > > > > > [INFO] Adding default classpath contaigner: > > > > > > org.eclipse.jdt.launching.JRE_CONTAI > > > > > > > > NER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5 > > > > > > [INFO] Using source status cache: C:\dev\iplocks\va\target\mvn- > > > > > > eclipse-cache.pro > > > > > > perties > > > > > > [INFO] Wrote settings to > > > > > > C:\dev\iplocks\va\ipl-migrate\.settings\org.eclipse.jdt > > > > > > .core.prefs > > > > > > [INFO] Wrote Eclipse project for "ipl-migrate" to > > > > > > C:\dev\iplocks\va\ipl-migrate. > > > > > > > > > > > > On Jan 31, 2008 7:27 AM, Arnaud HERITIER <[EMAIL PROTECTED]> > > wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > We fixed a lot of issues for the version 2.5 of the eclipse > > plugin > > > > and > > > > > > > we'll launch the vote to release it in few days. > > > > > > > In this version we improved a lot the support for RAD 6 / RAD 7 > > and > > > > we > > > > > > > added new features like WTP 2.0 support, MyEclipse support, > > > > > > dependencies > > > > > > > to projects in your projects, ... and more. > > > > > > > You can find the complete change log here : > > > > > > > > > > > > > > > > > > > http://jira.codehaus.org/browse/MECLIPSE?report=com.atlassian.jira.plugin.system.project:roadmap-panel > > > > > > > If you want to test it before the launch of the vote you have > > to > > > > define > > > > > > > and activate this profile : > > > > > > > > > > > > > > <profile> > > > > > > > <id>apache.snapshots</id> > > > > > > > <repositories> > > > > > > > <repository> > > > > > > > <releases> > > > > > > > <enabled>false</enabled> > > > > > > > </releases> > > > > > > > <snapshots/> > > > > > > > <id>apache.snapshots</id> > > > > > > > <name>Maven Snapshots</name> > > > > > > > <url>http://people.apache.org/maven-snapshot-repository > > > > </url> > > > > > > > </repository> > > > > > > > </repositories> > > > > > > > <pluginRepositories> > > > > > > > <pluginRepository> > > > > > > > <releases> > > > > > > > <enabled>false</enabled> > > > > > > > </releases> > > > > > > > <snapshots/> > > > > > > > <id>apache.plugin.snapshots</id> > > > > > > > <name>Maven Plugin Snapshots</name> > > > > > > > <url>http://people.apache.org/maven-snapshot-repository > > > > </url> > > > > > > > </pluginRepository> > > > > > > > </pluginRepositories> > > > > > > > </profile> > > > > > > > > > > > > > > And then you can call this command : > > > > > > > > > > > > > > mvn > > > > org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse > > > > > > > > > > > > > > (or another mojo). > > > > > > > > > > > > > > The documentation of the 2.5 was previously deployed by error, > > thus > > > > I > > > > > > just > > > > > > > updated it to give you the new version. > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > Arnaud > > > > > > > > > > > > > > -- > > > > > > > .......................................................... > > > > > > > Arnaud HERITIER > > > > > > > .......................................................... > > > > > > > OCTO Technology - aheritier AT octo DOT com > > > > > > > www.octo.com | blog.octo.com > > > > > > > .......................................................... > > > > > > > ASF - aheritier AT apache DOT org > > > > > > > www.apache.org | maven.apache.org > > > > > > > ........................................................... > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > .......................................................... > > > > > Arnaud HERITIER > > > > > .......................................................... > > > > > OCTO Technology - aheritier AT octo DOT com > > > > > www.octo.com | blog.octo.com > > > > > .......................................................... > > > > > ASF - aheritier AT apache DOT org > > > > > www.apache.org | maven.apache.org > > > > > ........................................................... > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > .......................................................... > > > Arnaud HERITIER > > > .......................................................... > > > OCTO Technology - aheritier AT octo DOT com > > > www.octo.com | blog.octo.com > > > .......................................................... > > > ASF - aheritier AT apache DOT org > > > www.apache.org | maven.apache.org > > > ........................................................... > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .......................................................... > Arnaud HERITIER > .......................................................... > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .......................................................... > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ........................................................... > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
