Js errors in concat responses should appear in comments (issue3711041)

Reviewers: dev-remai...@shindig.apache.org, dev@shindig.apache.org Description: If ConcatProxyServlet gets an error in fetching one of the JS files, it currently writes the error in the served out file as it is. This error should be included as a comment so that the rest of the concatenated js ca

Build failed in Hudson: Shindig #2062

See Changes: [hsaputra] change the path in the common container to point to working gadget.xml url for sample -- [...truncated 535 lines...] Running org.apache.shindig.common.cache.SoftExpiringCa

Build failed in Hudson: Shindig » A pache Shindig Gadget Renderer #2062

See -- [INFO] [INFO] Building Apache Shindig Gadget Renderer [INFO]task-segment: [clean, ins

Build failed in Hudson: Shindig #2061

See -- [...truncated 536 lines...] Running org.apache.shindig.common.cache.SoftExpiringCacheTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.apache.shindig.common.

Build failed in Hudson: Shindig » A pache Shindig Gadget Renderer #2061

See -- [INFO] [INFO] Building Apache Shindig Gadget Renderer [INFO]task-segment: [clean, ins

Build failed in Hudson: Shindig #2060

See Changes: [hsaputra] Add new line to JavaScript file for easy read. Mostly it will be minified in production env anyway. -- [...truncated 537 lines...] Running org.apache.shindig.common.cache.

Build failed in Hudson: Shindig » A pache Shindig Gadget Renderer #2060

See -- [INFO] [INFO] Building Apache Shindig Gadget Renderer [INFO]task-segment: [clean, ins

Feature shindig.container-1.0

hi I'm using shindig in my application for the year. Version 2.0.0 release. I'm using 'shindig.container' feature with my small hacks for my needs. Few days ago I've found 'shindig.container-1.0' feature which referenced to 'container' feature. After the first look on JS code and SHINDIG JIRA i

hudson shutdown?

Hudson said it was going to shutdown when I logged on... but it didn't after a while, and I didn't see anyone logged into the server, so I cancelled it (since it wouldn't build in that state) If I broke someone - lemme know.