On 4/11/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
Look at how people is doing in Apache Abdera
https://svn.apache.org/repos/asf/incubator/abdera/java/trunk/BUILDING
I think you can use :
mvn -Declipse.workspace=/path/to/workspace eclipse:eclipse
On 4/11/07, Simon Laws <[EMAIL PROTECTED
Look at how people is doing in Apache Abdera
https://svn.apache.org/repos/asf/incubator/abdera/java/trunk/BUILDING
I think you can use :
mvn -Declipse.workspace=/path/to/workspace eclipse:eclipse
On 4/11/07, Simon Laws <[EMAIL PROTECTED]> wrote:
To debug the calculator sample I did a mvn -P
To debug the calculator sample I did a mvn -Peclipse eclipse:eclipse in
java/sca and imported the calculator sample project and all dependecy
projects, into eclipse. Is there a way of generating the workspace
automatically to avoid the import step? Looking at the eclipse plugin
documentation ther
Srikanth Bhattiprolu wrote:
Am seeing some issues where the classpath that gets generated after running
mvn eclipse:eclipse is getting set to a wierd path:
instead of ...
I checked the pom.xml files and they all seem to have the correct value of
"SNAPSHOT" for the version. Any particular re
Am seeing some issues where the classpath that gets generated after running
mvn eclipse:eclipse is getting set to a wierd path:
instead of ...
I checked the pom.xml files and they all seem to have the correct value of
"SNAPSHOT" for the version. Any particular reason why the classpath is
gett