[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function

[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1594: Attachment: (was: Code Implement.js) Support CommonJS Modules i.e. the require

[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function

[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1594: Attachment: (was: Sytem Upgrade 1.js) Support CommonJS Modules i.e. the require

[jira] Created: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

Scala Scripting: Upgrade to Scala 2.8 - Key: SLING-1856 URL: https://issues.apache.org/jira/browse/SLING-1856 Project: Sling Issue Type: Improvement Components: Scripting Reporter:

[jira] Updated: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[ https://issues.apache.org/jira/browse/SLING-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated SLING-1856: - Attachment: SLING-1856.patch Patch for upgrading to Scala 2.8 Scala Scripting: Upgrade to

[jira] Assigned: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[ https://issues.apache.org/jira/browse/SLING-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1856: --- Assignee: Carsten Ziegeler Scala Scripting: Upgrade to Scala 2.8

[jira] Resolved: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[ https://issues.apache.org/jira/browse/SLING-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1856. - Resolution: Fixed Fix Version/s: Scripting Scala 1.0.0 Thanks Michael for your

Bootloader not updating jars

Hi, I might have missed a change in the launchpad/bootloader When re rebuild the standalone jar with additional bundles or updatede bundles and restart and existing Sling instance, the new or updated bundles are not updated. The only way to update jars appears to be via one of the other

[jira] Resolved: (SLING-1249) Commons Threads should be an optional dependency

[ https://issues.apache.org/jira/browse/SLING-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1249. - Resolution: Won't Fix Rethinking this, it doesn't really make sense - using the thread

RE: [VOTE] Apache Sling Explorer 1.0.0

+1 from me of course ;-)) best regards mike -Original Message- From: Mike Müller [mailto:mike...@mysign.ch] Sent: Monday, October 25, 2010 11:56 AM To: 'dev@sling.apache.org' Subject: [VOTE] Apache Sling Explorer 1.0.0 Hi, I tried to get out my first release, so be prepared,

[RESULT] [VOTE] Apache Sling Explorer 1.0.0

Hi, The vote has passed with the following result : 5 +1 (all binding): Felix Meschberger, Ian Boston, Carsten Ziegler, Bertrand Delacretaz, Mike Müller Thanks for voting - I'll release the artifacts asap, maybe I come back seeking some help... best regards mike

Re: Bootloader not updating jars

Hi, IIRC we just discussed to remove this functionality from the launchpad and replace it with an extension to the OSGi Installer. But I do not exactly know where are standing here Maybe Carsten and/or Justin know more. Regards Felix Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian

release managment help

Hi Okay, here we are - I need some help to promote the sling explorer release 1.0.0: 1) Which of the files I do have to copy to /x1/www/www.apache.org/dist/sling on people.apache.org? All files which are under [1]? If yes, which is the most efficient way to download them all from there (locally

[jira] Closed: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[ https://issues.apache.org/jira/browse/SLING-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig closed SLING-1856. Thanks Crasten, works great. Scala Scripting: Upgrade to Scala 2.8

Re: Bootloader not updating jars

Ok, thanks We will have to find a work around, using one of the other techniques, I will talk to the production teams, they were building new jars as part of the deployment strategy and wondering why nothing was updating. Ian On 28 Oct 2010, at 10:57, Felix Meschberger wrote: Hi, IIRC we

Re: Bootloader not updating jars

I don't think that's happened yet. What might be happening is that the bundles aren't reloaded unless the timestamp of the launchpad base JAR has changed. Ian- try running a debugger and you should be able to see where in BootstapInstaller the decision is made to skip installation/upgrade.

Re: Bootloader not updating jars

On 28 Oct 2010, at 12:29, Justin Edelson wrote: I don't think that's happened yet. What might be happening is that the bundles aren't reloaded unless the timestamp of the launchpad base JAR has changed. Checked that, Recreated the jar, and the bundle jars inside with all the timestamps

Build failed in Hudson: sling-trunk-1.5 » Apache Sling Bundle Resource Provider #945

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.bundleresource.impl/945/ -- [INFO] [INFO] Building Apache Sling Bundle Resource Provider

Build failed in Hudson: sling-trunk-1.5 #945

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/945/changes Changes: [justin] adding some debug logging during bootstrapping -- [...truncated 5325 lines...] [INFO] [resources:testResources {execution: default-testResources}] [INFO] Using 'UTF-8'