[jira] Assigned: (SLING-1545) ScripteEngineManagerFactory is not thread safe

[ https://issues.apache.org/jira/browse/SLING-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1545: --- Assignee: Carsten Ziegeler ScripteEngineManagerFactory is not thread safe

Re: Debugging JavaScript esp files

Hi Sandro, On 19.10.2010 02:39, Sandro Boehme wrote: Hi Felix, after diving into the topic I got the following understanding. Please correct me if I'm wrong. o In the Eclipse preferences one needs to map *.esp files to the JavaScript content type. Yes. Likewise for *.ecma. Though I have

[jira] Resolved: (SLING-1842) IllegalStateException in DefaultErrorHandlerServlet when HttpServletResponse.getOutputStream() already called

[ https://issues.apache.org/jira/browse/SLING-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1842. -- Resolution: Fixed Thanks for the feedback. Thus I think this can be resolved.

[jira] Resolved: (SLING-1545) ScripteEngineManagerFactory is not thread safe

[ https://issues.apache.org/jira/browse/SLING-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1545. - Resolution: Fixed I changed the lists to sets and refactored the code. The old script

[VOTE] Apache Sling Scripting Core 2.0.12, Scripting JSP 2.0.10, Scripting JavaScript 2.0.8, and Scripting JSP Taglib 2.1.0

Hi, this is the release vote for our scripting stuff for SLING-6. This vote is for the release of: Apache Sling Scripting Core 2.0.12 Apache Sling Scripting JavaScript 2.0.8 Apache Sling Scripting JSP 2.0.10 Apache Sling Scripting JSP-Taglib 2.1.0 Changes in these releases: Apache Sling

Re: [VOTE] Apache Sling Scripting Core 2.0.12, Scripting JSP 2.0.10, Scripting JavaScript 2.0.8, and Scripting JSP Taglib 2.1.0

+1 Approve the release Apache Sling Scripting Core 2.0.12 Apache Sling Scripting JavaScript 2.0.8 Apache Sling Scripting JSP 2.0.10 Apache Sling Scripting JSP-Taglib 2.1.0 Carsten -- Carsten Ziegeler cziege...@apache.org

Build failed in Hudson: sling-trunk-1.5 » Apache Sling Launchpad Maven Plugin #930

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$maven-launchpad-plugin/930/ -- [INFO] [INFO] Building Apache Sling Launchpad Maven Plugin [INFO]

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

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/930/changes Changes: [cziegeler] Go back to parent pom 10-snapshot and use latest snapshots for launchpad [cziegeler] Go back to parent pom 10-snapshot and use latest snapshots for launchpad [cziegeler] [maven-release-plugin] prepare

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #616

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/616/

Hudson build is still unstable: sling-trunk-1.6 #616

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes

Re: Debugging JavaScript esp files

Hi Felix, Am 19.10.10 08:48, schrieb Felix Meschberger: o In the Eclipse preferences one needs to map *.esp files to the JavaScript content type. Yes. Likewise for *.ecma. Though I have issues setting breakpoints on *.esp files because on my box Eclipse tells it cannot resolve the line

Re: Debugging JavaScript esp files

Hi, On 19.10.2010 13:20, Sandro Boehme wrote: Hi Felix, Am 19.10.10 08:48, schrieb Felix Meschberger: o In the Eclipse preferences one needs to map *.esp files to the JavaScript content type. Yes. Likewise for *.ecma. Though I have issues setting breakpoints on *.esp files because on my

Re: Debugging JavaScript esp files

Am 19.10.10 13:41, schrieb Felix Meschberger: Hi, I cannot easily find out if the trigger to load the JavaScript files is already there somewhere. I guess we only need to trigger the handleCompilationDone() methode somewhere in Sling but I don't know enough about Sling to decide where that

Re: Debugging JavaScript esp files

Hi, On 19.10.2010 14:21, Sandro Boehme wrote: Am 19.10.10 13:41, schrieb Felix Meschberger: Hi, I cannot easily find out if the trigger to load the JavaScript files is already there somewhere. I guess we only need to trigger the handleCompilationDone() methode somewhere in Sling but I

Re: [VOTE] Initial Content and Servlet Archetypes 1.0.0

+1 On Fri, Oct 15, 2010 at 10:45 AM, Justin Edelson jus...@apache.org wrote: Hi, This vote is for: Sling Initial Content Archetype 1.0.0 Sling Servlet Archetype 1.0.0 This is the initial version of each. Staging repository:

[RESULT] [VOTE] Release Apache Sling Initial Content and Servlet Archetypes 1.0.0

Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Felix Meschberger, Mike Muller, Ian Boston, Justin Edelson +1 (non-binding): Eric Norman I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Justin

[jira] Closed: (SLING-1844) rename resources archetype to initial-content

[ https://issues.apache.org/jira/browse/SLING-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson closed SLING-1844. - rename resources archetype to initial-content ---

[jira] Updated: (SLING-1054) Maven archetypes

[ https://issues.apache.org/jira/browse/SLING-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1054: -- Fix Version/s: Launchpad Standalone Archetype 1.0.0 Launchpad Webapp

Re: [VOTE] Apache Sling Scripting Core 2.0.12, Scripting JSP 2.0.10, Scripting JavaScript 2.0.8, and Scripting JSP Taglib 2.1.0

+1 Thanks On 10/19/10 4:49 AM, Carsten Ziegeler wrote: Hi, this is the release vote for our scripting stuff for SLING-6. This vote is for the release of: Apache Sling Scripting Core 2.0.12 Apache Sling Scripting JavaScript 2.0.8 Apache Sling Scripting JSP 2.0.10 Apache Sling

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #617

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/617/

Hudson build is still unstable: sling-trunk-1.6 #617

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes

Build failed in Hudson: sling-trun k-1.5 » Apache Sling (Parent) #931

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$sling/931/ -- ===[HUDSON REMOTING CAPACITY]===channel started Executing Maven: -B -f /home/hudson/hudson-slave/workspace/sling-trunk-1.5/trunk/pom.xml -DobrRepository=false

Making emma stuff optional?

Hi, can we make the emma stuff optional? Currently the file coverage.em is created in the root of each module (which is not in svn:ignore atm - no problem with that we can just add it) and an additional artifact -emma is created, which we don't want to release/deploy. So I think this should be

Re: Debugging JavaScript esp files

Hi Felix, Am 19.10.10 15:28, schrieb Felix Meschberger: Hi, On 19.10.2010 14:21, Sandro Boehme wrote: Am 19.10.10 13:41, schrieb Felix Meschberger: Hi, I cannot easily find out if the trigger to load the JavaScript files is already there somewhere. I guess we only need to trigger the

cannot run the launchpad

Hello, since quite some time I'm trying to get the launchpad running in Jetty. I build sling on a clean checkout from SVN without errors but the launchpad doesn't start as it is missing the Emma classes at runtime (see output below). Can you tell me where I have to add the dependency to emma?

[jira] Commented: (SLING-1803) add coverage reporting of integration tests

[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922627#action_12922627 ] Justin Edelson commented on SLING-1803: --- in r1024330, disabled instrumentation

Re: Making emma stuff optional?

done in r1024330. Justin On 10/19/10 11:43 AM, Carsten Ziegeler wrote: Hi, can we make the emma stuff optional? Currently the file coverage.em is created in the root of each module (which is not in svn:ignore atm - no problem with that we can just add it) and an additional artifact -emma

Re: Making emma stuff optional?

Thanks a lot Justin! It also fixes the problem I wrote about in the other mail. I can now run the launchpad again. Best, Sandro Am 19.10.10 19:28, schrieb Justin Edelson: done in r1024330. Justin On 10/19/10 11:43 AM, Carsten Ziegeler wrote: Hi, can we make the emma stuff optional?

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #618

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/618/

Hudson build is still unstable: sling-trunk-1.6 #618

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes

Hudson build is back to normal : sling -trunk-1.5 » Apache Sling (Parent) #932

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$sling/932/changes

Hudson build is unstable: sling-trunk-1.5 #932

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/932/changes

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

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/933/changes Changes: [justin] SLING-1803 - forgot to also move the extra execution of the bundle plugin to the emma profile -- [...truncated 11264 lines...] [INFO] Copying bundle from

Hudson build is still unstable: sling-trunk-1.6 #619

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #619

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/619/