Page 1 of 1

StackStarter.jar creates separate projects

Posted: Tue Jan 08, 2013 1:51 pm
by pauldev
While going through the maven lab 2, I noticed that with the latest ldstech ide that the eclipse projects get enclosed in the parent project. But when I run StackStarter.jar, it still creates separate eclipse projects.
Is this as designed, or will it be enhanced to put all in the parent project?

Re: StackStarter.jar creates separate projects

Posted: Thu Jan 10, 2013 2:30 pm
by YoungstromMJ
I'm not sure exactly what you are referring to Paul.

Stack Starter creates a Maven project that is multiple modules. A parent with several children.

However in the lds-tech ide eclipse can only display projects in a flat structure. So when you import the root project into eclipse it will flatten the maven project out into a project for the parent and a project for each of the children. It is the same maven project with hierarchy intact it just looks flat in eclipse with a project for each maven project.

Does that help with what you are seeing? Or am I on the wrong track?

Mike

Re: StackStarter.jar creates separate projects

Posted: Thu Jan 10, 2013 2:39 pm
by pauldev
I think that in addition to creating child directories and child poms, I needed to create file to tell eclipse that these are actually separate projects, not just child directories. Maven works as expected on them though.
The important thing is that stackstarter creates the projects correctly so they get imported correctly.
All is okay!

Re: StackStarter.jar creates separate projects

Posted: Thu Jan 10, 2013 2:44 pm
by YoungstromMJ
Glad it is working. When you say:
I needed to create file to tell eclipse that these are actually separate projects
What do you mean?

Mike

Re: StackStarter.jar creates separate projects

Posted: Wed Jan 16, 2013 4:02 pm
by pauldev
I meant that for some reason eclipse did not recognise the subdirs as containing eclipse projects...
No problem though, it is now history.

Re: StackStarter.jar creates separate projects

Posted: Wed Jan 16, 2013 4:16 pm
by YoungstromMJ
Oh yeah. The trick is to do an eclipse Import->Maven->Import Existing Maven Project or something like that. That way eclipse will look for a pom.xml and use that to determine that it can import it.

Mike