Page 1 of 1

Demosite project structure in eclipse

Posted: Tue Mar 19, 2013 1:30 pm
by pam
Hi all,

My demosite project structure in eclipse looks like this,

Maven parents
|---DemoSite
|-----admin
|-----combined
|-----core etc
My Broadleafsite
|------admin
|------comined
|------core
|------site

Why both structures are required. Which project structure should I work on? ie extending entities, modifying xmls and presentation.

Look forward for your responses. Thank you.

~ Thanks

Re: Demosite project structure in eclipse

Posted: Tue Mar 19, 2013 2:15 pm
by phillipuniverse
Each structure represents a working set: http://www.javalobby.org/forums/thread. ... adID=15162. The reason that we did this is so that when you do cmd+shift+r (open a resource) you only get a single resource rather than a bunch of different options (which also include generated .class files). This makes it much easier and faster to look for files; only within the 'My Brodleafsite' working set that has all of your Java class files and resources. This also has to do with how Eclipse handles multi-module Maven projects. It splits each module into it's own project; working sets combine them together.

The exception to this is when you need to modify the root pom.xml. The only way to do this is via the 'Maven Parents -> DemoSite' tree, as this represents the root Maven module. You will not be able to get to this pom.xml by using the "Open Resource" dialog (cmd+shift+r) as that dialog is using only the 'My Broadleafsite' working set (as it should).

Re: Demosite project structure in eclipse

Posted: Wed Mar 20, 2013 2:18 pm
by pam
Thanks for your response phillipuniverse!