This forum is in readonly mode and serves as an archive of old information. All posting, registration and commenting abilities have been turned off. To get help, the Broadleaf team reguarly monitors the broadleaf-commerce tag on Stack Overflow so please ask your questions there.

But you still might run into compilation errors because of things that have changed in our DemoSite to deal with changes in the Broadleaf framework. In this scenario, the diff between BETA2 and BETA3 can be found via this link:

We are tagging commits in DemoSite for new versions of the Broadleaf 3.0 BETA so that this process is as easy as possible.

The Broadleaf forums are being retired as a readonly archive of questions. For active discussions and questions, check out the broadleaf-commerce tag on Stack Overflow which is actively monitored by the Broadleaf team.

This is not something we would recommend. We recommend all sites use DemoSite as a starting point since it contains configurations that most (if not all) Broadleaf sites will need.

We do not currently have any documentation for starting a new site completely from scratch. The DemoSite heat clinic is actually the replacement for the old Maven archetype.

The Broadleaf forums are being retired as a readonly archive of questions. For active discussions and questions, check out the broadleaf-commerce tag on Stack Overflow which is actively monitored by the Broadleaf team.

1. What modules are you trying to integrate? We still have work to do to bring over many of the 2.x modules and are prioritizing them based on immediate needs.

2. We are working on a way to have users contribute documentation. It's actually a really clever idea from a couple of our developers that will leverage GitHub. You'll here more about it soon.

3. Also, I'll amend what Phillip said as far as us "recommending" that projects use the DemoSite. We believe it is the best place to start as you are learning and prototyping the system. We will also keep it up to date and provide module documentation going forward that shows how a module can be added to the DemoSite. That being said, I personally would remove most DemoSite specific code, assets, etc. from my actual production code. This shouldn't be a terribly difficult exercise and we will continue to work on improving the documentation in this area.

Hello thereI have a serious problem with broadleaf-3.1.0-ALPHA1.it couldn't make WAR file I found why it couldn't but I don't know how to fix it.during broadleaf-3.1.0-ALPHA1 in admin modul you see 3 sub modul for making WAR file via maven we need one of this sub modul has a pakage for making war file but all of these pakages are jar and ther is no pakage to make a war file I don't know how to fix it and how to make a war fileI look forward to hearing from youthanks