Broadleaf Commerce Discussion Forums

Hi All,

I'm interested in running the demo app against the develop branch of the BroadleafCommerce framework:
https://github.com/BroadleafCommerce/Br ... ee/develop

Being a Java/Eclipse newb, I was wondering if there are any instructions for building and importing the framework code into the demo site? I've got the framework repo cloned and imported into Eclipse (via the demo Getting Started instructions), but I'm stuck there. Any help is greatly appreciated.

Thanks!
Jeff

Generally, you shouldn't be modifying code in the Broadleaf project. Instead, you should be extending the functionality by creating your own classes in the DemoSite.

Furthermore, the develop branch is very unstable right now as we're going through a major refactoring.

To expand upon Andre's answer, this is really taken care of by Maven's dependency management. If you look at the root pom.xml for DemoSite (located in the root of the file structure) you will see this section:



Changing the blc.version property will change which version of Broadleaf the DemoSite is targeting. For instance, currently on the develop branch of Broadleaf its pom.xml is at 2.2.0-SNAPSHOT (https://github.com/BroadleafCommerce/Br ... op/pom.xml and the 'version' xml element near the top).

As Andre mentioned, we're in the middle of a pretty large refactoring of the develop branch of Broadleaf (the 2.2 version) so just a warning. I would also say that you might consider checking out from the develop branch of the DemoSite project (https://github.com/BroadleafCommerce/De ... ee/develop) since that is already targeting the 2.2.0-SNAPSHOT version of Broadleaf and it also has whatever changes are needed from an implementation perspective between 2.0 and 2.2 of Broadleaf.

That was a slightly drawn out answer, but hopefully that helps some as you're a little new to the ecosystem in general. For more info about Maven there is a host of information on Google and it has pretty much become the de-facto standard for Java dependency management. For more info about how we at Broadleaf do versioning, check out a blog by our CTO at http://broadleafnut.blogspot.com/2012/0 ... oning.html

@aazzolini, thanks for your response. I got ya, I wasn't intending to modify any code in the framework; rather I was interested in having the most up-to-date version in terms of feature set, at the cost of some stability, as we are still in framework evaluation mode.

@phillipuniverse, thanks for the background on Maven, and for pointing me to the develop branch of the DemoSite repo, I was able to get it up and running. I noticed the Working Sets a la the stable version are missing, but I recreated them.

Thanks again to you both for your help!