If features, javascript etc had poms, mvn eclipse:eclipse might
generate project files, or it is possible to exclude items from
classpath.
Ian
On 25 Apr 2008, at 02:34, David Primmer wrote:
I agree that with our current pom's, there's no way you can configure
this to work in eclipse and have it be portable. Those maven commands
will not create an eclipse project rooted in trunk/ it will make
projects for
/trunk/java/gadgets
/trunk/java/social-api
/trunk/java/common
The issue with the gadgets project is that eclipse cannot have a
source reference that is below it's root project folder. you can't
tell it../../. And to fix it, you have to create an external folder
link with a absolute path in your filesystem. As brian has done. This
is all because the javascript and other stuff is two levels below the
root of the eclipse project.
The only way to solve this that I can see would be to alter our pom's
so that a root eclipse project is created by the mvn eclipse:m2eclipse
in trunk/ and from what i've read of the docs, that will automatically
find the child projects and add them as sub projects in eclipse. All
deps happy. no manual linking on every new workspace. Anybody know how
to do that?
davep
On Thu, Apr 24, 2008 at 5:55 PM, Brian Eaton <[EMAIL PROTECTED]>
wrote:
That cut the number of errors from around 100 to 9:
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/config' gadgets Build path
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/features' gadgets Build path
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/javascript' gadgets Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/config' shindig-server
Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/features' shindig-server
Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/javascript' shindig-server
Build path
The project cannot be built until build path errors are
resolved gadgets
The project cannot be built until build path errors are
resolved shindig-server
The project was not built since it depends on gadgets, which has
build
path errors social-api
I don't have a strong preference for my approach to getting things
working in eclipse, or mvn eclipse:eclipse, or mvn
eclipse:m2eclipse,
except that mine is the only way I can get to work. =)
Cheers,
Brian
On Tue, Apr 22, 2008 at 1:40 PM, Ian Boston <[EMAIL PROTECTED]> wrote:
Ahh, M2_REPO not defined ?
you need to got to goto
Preferences -> Java -> Apperance -> Build Path -> Classpath
variables
and then create a new variable M2_REPO pointing to
the folder ~/.m2/repository
Thats on Unix, I am not certain where the local Maven 2 repo is
on Windows.
Ian
On 22 Apr 2008, at 17:16, Brian Eaton wrote:
On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <[EMAIL PROTECTED]> wrote:
Have you tried
cd shindig/java
mvn eclipse:eclipse
and then import the projects into eclipse ?
Yes. It doesn't work. I get bunches of 'Unbound classpath' and
'Project X is missing required java project Y' errors.
