First issue is, Without Jrebel is it not possible to view the changes without the restart of jetty. Im trying to make a code change in a template and view it just by refreshing the browser, it worked only after restarting jetty.
This is endemic to every single Java application ever. Sorry. One thing that you can do just for the view layer is re-copy all of your template files into the exploded war directory in target, since Jetty uses this for all of its information. You can just go into the site application and do a 'mvn install' to update those directories with the new template files. You are kinda SOL for Java classes though unless you use Jrebel or maybe spring-loaded (haven't really tested this with Broadleaf though).
The second issue is, it takes nearly 15 to 20 minutes each to start jetty for admin jetty-demo and site jetty-demo. Can you please help me resolve this. Thanks.
Wow, that really sucks. What platform are you on? Windows, Linux, OSX? Currently, this is taking longer than it should and one thing that we are going to be doing soon is switch to the Tomcat embedded plugin rather than Jetty (it doesn't seem like anybody is deploying Jetty to production anyway). I have noticed
significant improvements by using the Tomcat plugin over Jetty but we just haven't gotten this setup with the demo site yet.