Disruptive Push to UX Master

[Ian Boston]

or make tell the content loader to overwrite existing content?
Then you would not need to delete anything.
Ian

On 1 Sep 2010, at 13:52, Carl Hall wrote:

> Assuming this works like the search templates do, you can use the jquery explorer bundle from sling [1], you can manually delete /var/templates/* and any other content nodes that need to be reloaded then reload the UX bundle.  This is what I've done when testing out search templates that get loaded as content.
> 
> HTH,
> Carl
> 
> 1 http://home.hallwaytech.com/org.apache.sling.extensions.explorer.jquery-0.0.2-SNAPSHOT.jar
> 
> 
> On Wed, Sep 1, 2010 at 1:50 AM, Chris Roby <croby at nyu.edu> wrote:
> Hi everyone,
> 
> I just made some big changes to the UX master that require a little extra work to get working.
> 
> 1) Pull latest UX from sakaiproject/master
> 2) Build this UX (mvn clean install in the UX directory)
> 3) Delete your sling directory
> 4) Start the Nakamura server
> 5) Install/Upgrade and start the UX via the Sling console
>  - Sling console located at http://localhost:8080/system/console/bundles
>  - UX jar located in <3akai-ux directory>/target
> 6) Create a new user
> 
> The reason for this is that the templates located in /var/templates/site have been changed. As of now, this process outlined above is the easiest way to pull those changes into the JCR. Simply doing a new build of Nakamura won't pull in these changes if you already have a UX bundle built. If the Kernel developers have an easier way to do this, please let me know.
> 
> --
> Chris Roby
> 
> 
> _______________________________________________
> sakai-ui-dev mailing list
> sakai-ui-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
> 
> _______________________________________________
> sakai-ui-dev mailing list
> sakai-ui-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev