Re: cannot run the launchpad
Hi,
In fact, today I observed 80 failed tests after fully rebuilding sling.
Is that reported?
Cheers,
Jos
On 10/19/2010 07:06 PM, Sandro Boehme wrote:
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?
Best,
Sandro
Sandros-MacBook:builder sboehme$ mvn jetty:run
Listening for transport dt_socket at address: 30303
[INFO] Scanning for projects...
[INFO]
[INFO] Building Apache Sling Launchpad Application Builder
[INFO]task-segment: [jetty:run]
[INFO]
[INFO] Preparing jetty:run
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [groovy:execute {execution: save-bundle-metadata}]
[INFO] [launchpad:prepare-package {execution: prepare-package-war}]
[INFO] [launchpad:prepare-package {execution: prepare-package-jar}]
[INFO] Unpacking
/Users/sboehme/maven_local_repo/org/apache/sling/org.apache.sling.launchpad.base/2.2.1-SNAPSHOT/org.apache.sling.launchpad.base-2.2.1-SNAPSHOT-app.jar
to
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/classes
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/src/main/resources
[INFO] Copying 3 resources
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] WARNING (SLING-443/SLING-1782)
**
[echo] On most platforms, you'll get OutOfMemoryErrors when
building unless you set
[echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M
-XX:MaxPermSize=256M, see SLING-443
[echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M
-XX:MaxPermSize=512M, see SLING-1782
[echo]
**
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [jetty:run {execution: default-cli}]
[INFO] Configuring Jetty for project: Apache Sling Launchpad
Application Builder
[INFO] Webapp source directory =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT
[INFO] Reload Mechanic: automatic
[INFO] Classes =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/classes
2010-10-19 18:33:02.452::INFO: Logging to STDERR via
org.mortbay.log.StdErrLog
[INFO] Context path = /
[INFO] Tmp directory = determined at runtime
[INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml
[INFO] Web overrides = none
[INFO] Adding overlay:
jar:file:/Users/sboehme/maven_local_repo/org/apache/sling/org.apache.sling.launchpad.base/2.2.1-SNAPSHOT/org.apache.sling.launchpad.base-2.2.1-SNAPSHOT-webapp.war!/
[INFO] web.xml file =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT/WEB-INF/web.xml
[INFO] Webapp directory =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT
[INFO] Starting jetty 6.1.20 ...
2010-10-19 18:33:02.476::INFO: jetty-6.1.20
2010-10-19 18:33:02.673::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
2010-10-19 18:33:03.162::WARN: failed sling:
java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT
2010-10-19 18:33:03.162::WARN: failed
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@9946e0{/,file:/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT/;jar:file:/Users/sboehme/maven_local_repo/org/apache/sling/org.apache.sling.launchpad.base/2.2.1-SNAPSHOT/org.apache.sling.launchpad.base-2.2.1-SNAPSHOT-webapp.war!/;}:
java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT
2010-10-19 18:33:03.162::WARN: failed contexthandlercollect...@8be01:
Re: cannot run the launchpad
I believe that's the same script resolution problem Sandro reported
yesterday (and not related to Emma). I'm seeing 70 failures; Hudson
reported 76 IIRC.
Can you confirm that all of the failed tests are script related
(should be pretty obvious from the names).
Justin
On Wed, Oct 20, 2010 at 8:22 AM, Jos Snellings jos.snelli...@pandora.be wrote:
Hi,
In fact, today I observed 80 failed tests after fully rebuilding sling.
Is that reported?
Cheers,
Jos
On 10/19/2010 07:06 PM, Sandro Boehme wrote:
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?
Best,
Sandro
Sandros-MacBook:builder sboehme$ mvn jetty:run
Listening for transport dt_socket at address: 30303
[INFO] Scanning for projects...
[INFO]
[INFO] Building Apache Sling Launchpad Application Builder
[INFO] task-segment: [jetty:run]
[INFO]
[INFO] Preparing jetty:run
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [groovy:execute {execution: save-bundle-metadata}]
[INFO] [launchpad:prepare-package {execution: prepare-package-war}]
[INFO] [launchpad:prepare-package {execution: prepare-package-jar}]
[INFO] Unpacking
/Users/sboehme/maven_local_repo/org/apache/sling/org.apache.sling.launchpad.base/2.2.1-SNAPSHOT/org.apache.sling.launchpad.base-2.2.1-SNAPSHOT-app.jar
to
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/classes
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/src/main/resources
[INFO] Copying 3 resources
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] WARNING (SLING-443/SLING-1782)
**
[echo] On most platforms, you'll get OutOfMemoryErrors when building
unless you set
[echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M,
see SLING-443
[echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M,
see SLING-1782
[echo]
**
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [jetty:run {execution: default-cli}]
[INFO] Configuring Jetty for project: Apache Sling Launchpad Application
Builder
[INFO] Webapp source directory =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT
[INFO] Reload Mechanic: automatic
[INFO] Classes =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/classes
2010-10-19 18:33:02.452::INFO: Logging to STDERR via
org.mortbay.log.StdErrLog
[INFO] Context path = /
[INFO] Tmp directory = determined at runtime
[INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml
[INFO] Web overrides = none
[INFO] Adding overlay:
jar:file:/Users/sboehme/maven_local_repo/org/apache/sling/org.apache.sling.launchpad.base/2.2.1-SNAPSHOT/org.apache.sling.launchpad.base-2.2.1-SNAPSHOT-webapp.war!/
[INFO] web.xml file =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT/WEB-INF/web.xml
[INFO] Webapp directory =
/Users/sboehme/Documents/workspaces/slingtrunk/launchpad/builder/target/org.apache.sling.launchpad-6-SNAPSHOT
[INFO] Starting jetty 6.1.20 ...
2010-10-19 18:33:02.476::INFO: jetty-6.1.20
2010-10-19 18:33:02.673::INFO: No Transaction manager found - if your
webapp requires one, please configure one.
2010-10-19 18:33:03.162::WARN: failed sling:
java.lang.NoClassDefFoundError: com/vladium/emma/rt/RT
2010-10-19 18:33:03.162::WARN: failed
exhaustive list
Please find the exhaustive list below: testEscapedErrorMessages(org.apache.sling.launchpad.webapp.integrationtest.issues.SLING760Test) testRequestAttribute(org.apache.sling.launchpad.webapp.integrationtest.RequestAttributeTest) testWithExactUrl(org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest) testGETScript(org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest) testWithExtraPathA(org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest) testCallFooHtml(org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test) testCallHtml(org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test) testGenericProvider(org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest) testGroovyProvider(org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest) testJSPProvider(org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest) testJSPProviderEL(org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest) testCanAddUser(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanAddGroup(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanUpdateUserProperties(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanUpdateGroupProperties(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanRemoveUser(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanRemoveGroup(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testCanUpdateGroupMembers(org.apache.sling.launchpad.webapp.integrationtest.userManager.PrivilegesInfoTest) testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest) testForcedResourceType(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest) testWithoutInclude(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest) testWithInclude(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest) testWithIncludeAndExtension(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest) testWithoutForward(org.apache.sling.launchpad.webapp.integrationtest.ForwardTest) testWithForward(org.apache.sling.launchpad.webapp.integrationtest.ForwardTest) testWithForwardAndExtension(org.apache.sling.launchpad.webapp.integrationtest.ForwardTest) testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.ForwardTest) testForcedResourceType(org.apache.sling.launchpad.webapp.integrationtest.ForwardTest) testRecursiveDump(org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest) testWithoutForward(org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest) testWithForward(org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest) testWithForwardAndExtension(org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest) testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest) testForcedResourceType(org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest) testSuperTypeOnResource(org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest) testSuperTypeOnScriptFolder(org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest) testEspScript(org.apache.sling.launchpad.webapp.integrationtest.ExecuteScriptTest) testJspScript(org.apache.sling.launchpad.webapp.integrationtest.ExecuteScriptTest) testNestedInclude(org.apache.sling.launchpad.webapp.integrationtest.EspLoadTest) testNonExistentInclude(org.apache.sling.launchpad.webapp.integrationtest.EspLoadTest) testJSONGroovyBuilder(org.apache.sling.launchpad.webapp.integrationtest.JSONGroovyBuilderIntegrationTest) testJSONGroovyBuilder2(org.apache.sling.launchpad.webapp.integrationtest.JSONGroovyBuilderIntegrationTest) testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testForcedResourceType(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testWithoutInclude(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testWithInclude(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testWithIncludeAndExtension(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testMaxCallsDetection(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest) testEspHtml(org.apache.sling.launchpad.webapp.integrationtest.SlingResourceTypeRenderingTest) testGspHtml(org.apache.sling.launchpad.webapp.integrationtest.SlingResourceTypeRenderingTest) testEspJavaCode(org.apache.sling.launchpad.webapp.integrationtest.SlingResourceTypeRenderingTest) testGspJavaCode(org.apache.sling.launchpad.webapp.integrationtest.SlingResourceTypeRenderingTest)
[jira] Commented: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923121#action_12923121 ] Justin Edelson commented on SLING-1848: --- done in r1025692. registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.12 ScriptEngineManagerFactory.refreshScriptEngineManager() handles the registration of an OSGi service of the ScriptEngineManager. This is used, amongst other places, by SlingScriptAdapterFactory. However, refreshScriptEngineManager() is *only* called from activate() and getScriptEngineManager() (and in the latter case, only if the scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) null out scriptEngineManager, they do not call refreshScriptEngineManager(). As a result, new ScriptEngineFactory services are not effective with this call sequence: 1) activate() 2) bindScriptEngineManager() 3) try adapting a script to a javax.servlet.Servlet This can be worked around (albeit poorly IMHO) by going to the Configuration Status page in the web console because this causes getScriptEngineManager() to be called when scriptEngineManager is null, thus causing refreshScriptEngineManager() to be called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923126#action_12923126 ] Felix Meschberger commented on SLING-1848: -- I think this is fix is not along the intent of SLING- 1545 n but is probably ok for the short-term. The problem with the SLING-1545 implementation is that the maneger is dropped but the registered service (which is dropped) is not unregistered I think it is about time to consider something completely different for the ScriptManager: We create our own implementation which allows us to unregister ScriptEngineFactory instances - something which is not foreseen in the standard ScriptManager. Thus we could setup the ScriptEngineManager once and for all and just add/remove ScriptEngineFactories as they come and go. Another option would be to register a Proxy object as the service which in the back end accesses the real ScriptEngineManager on-demand thus forcing the ScriptEngineManager to be recreated should it be removed. registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.12 ScriptEngineManagerFactory.refreshScriptEngineManager() handles the registration of an OSGi service of the ScriptEngineManager. This is used, amongst other places, by SlingScriptAdapterFactory. However, refreshScriptEngineManager() is *only* called from activate() and getScriptEngineManager() (and in the latter case, only if the scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) null out scriptEngineManager, they do not call refreshScriptEngineManager(). As a result, new ScriptEngineFactory services are not effective with this call sequence: 1) activate() 2) bindScriptEngineManager() 3) try adapting a script to a javax.servlet.Servlet This can be worked around (albeit poorly IMHO) by going to the Configuration Status page in the web console because this causes getScriptEngineManager() to be called when scriptEngineManager is null, thus causing refreshScriptEngineManager() to be called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1848) registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered
[ https://issues.apache.org/jira/browse/SLING-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923129#action_12923129 ] Justin Edelson commented on SLING-1848: --- in r1025700, added a similar change which impacts bundleChanged() registration (or unregistration) of a ScriptEngineFactory doesn't cause the ScriptEngineManager service to be re-registered --- Key: SLING-1848 URL: https://issues.apache.org/jira/browse/SLING-1848 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Assignee: Justin Edelson Priority: Blocker Fix For: Scripting Core 2.0.12 ScriptEngineManagerFactory.refreshScriptEngineManager() handles the registration of an OSGi service of the ScriptEngineManager. This is used, amongst other places, by SlingScriptAdapterFactory. However, refreshScriptEngineManager() is *only* called from activate() and getScriptEngineManager() (and in the latter case, only if the scriptEngineManager is null). Although bindScriptEngineManager() (and unbind) null out scriptEngineManager, they do not call refreshScriptEngineManager(). As a result, new ScriptEngineFactory services are not effective with this call sequence: 1) activate() 2) bindScriptEngineManager() 3) try adapting a script to a javax.servlet.Servlet This can be worked around (albeit poorly IMHO) by going to the Configuration Status page in the web console because this causes getScriptEngineManager() to be called when scriptEngineManager is null, thus causing refreshScriptEngineManager() to be called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1843) add a goal to maven-launchpad-plugin similar to versions:display-dependency-updates
[ https://issues.apache.org/jira/browse/SLING-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1843. --- Resolution: Fixed Fix Version/s: Maven Launchpad Plugin 2.0.8 Assignee: Justin Edelson done in r1025711 add a goal to maven-launchpad-plugin similar to versions:display-dependency-updates --- Key: SLING-1843 URL: https://issues.apache.org/jira/browse/SLING-1843 Project: Sling Issue Type: New Feature Components: Maven Plugins and Archetypes Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 2.0.8 see http://mojo.codehaus.org/versions-maven-plugin/examples/display-dependency-updates.html running mvn launchpad:display-bundle-updates should show a list of bundles in the bundle list for which newer versions exist. Similar to the versions-maven-plugin goal, -DallowSnapshots should default to false, but be usable to display snapshot upgrades. Important note - only the current project's bundle list (i.e. src/main/bundles/list.xml) will be analyzed, not the fully resolved bundle list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #620
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/620/
Hudson build is still unstable: sling-trunk-1.6 #620
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes
Re: script resolving doesn't work
This looks like a different problem (which I and Hudson are both now
seeing). I think this is related changes made in SLING-1842.
Felix - can you take a look at this? Thanks.
On 10/20/10 4:27 PM, Sandro Boehme wrote:
Hi Justin,
I get the two test failures:
testMaxCallsDetection(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest)
testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.IncludeTest)
Attached you find more detailed information and logs.
Best,
Sandro
Am 20.10.10 21:34, schrieb Justin Edelson:
Sandro-
If you get a chance, please try out trunk now. I just committed a fix
which seems to be working for me, but it'll be a while before Hudson
confirms.
Thanks,
Justin
On 10/20/10 3:21 PM, Sandro Boehme wrote:
I'm glad it was not a user error ;-). The problem simply was, that I
checked out the trunk while it was not yet working properly.
I should have had a look at the hudson build before updating from trunk.
Using git (git://git.apache.org/sling.git) now to be able to easily
revert my local experiments to the last working version of the trunk
(right now this should be commit 129f4d btw).
Best,
Sandro
Am 20.10.10 01:23, schrieb Sandro Boehme:
Hello,
mvn clean install of sling on a fresh checkout from trunk did not show
any errors. Also running Jetty works and all bundles are active. But
the
scripts of the Sling Explorer don't get executed and the
HtmlRendererServlet is show like that:
=
Resource dumped by HtmlRendererServlet
Resource path: */index.html*
Resource metadata: *{sling.creationTime=1287529282337,
sling.contentType=text/html, sling.resolutionPathInfo=.explorer.html,
sling.modificationTime=1287528833921, sling.contentLength=5898,
sling.resolutionPath=/index.html}*
Resource type: *nt:file*
Resource super type: *-*
Resource properties
jcr:createdBy: *admin*
jcr:created:
*java.util.GregorianCalendar[time=1287529282337,areFieldsSet=true,areAllFieldsSet=true,lenient=false,zone=sun.util.calendar.ZoneInfo[id=GMT+02:00,offset=720,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2010,MONTH=9,WEEK_OF_YEAR=43,WEEK_OF_MONTH=4,DAY_OF_MONTH=20,DAY_OF_YEAR=293,DAY_OF_WEEK=4,DAY_OF_WEEK_IN_MONTH=3,AM_PM=0,HOUR=1,HOUR_OF_DAY=1,MINUTE=1,SECOND=22,MILLISECOND=337,ZONE_OFFSET=720,DST_OFFSET=0]*
jcr:primaryType: *nt:file
*
=
*The bundle of the Sling Explorer is marked active in the console.
*
Also the simple script from the 15min tutorial that renders the title
property does not get executed. Instead the HtmlRendererServlet dumps
the Resource like that:
=
Resource dumped by HtmlRendererServlet
Resource path: */content/mynode*
Resource metadata: *{sling.resolutionPathInfo=.html,
sling.resolutionPath=/content/mynode}*
Resource type: *foo/bar*
Resource super type: *-*
Resource properties
title: *some title*
sling:resourceType: *foo/bar*
jcr:primaryType: *nt:unstructured
*=
The curl commands that create the WebDAV folders and upload the script
are executed successfully. And via WebDAV I can see that the script is
there (/apps/foo/bar/html.esp).
I debugged some resolver classes, searched at Google and tried to
find a
solution to that for quite some time now. But I have no idea left.
Does somebody have a hint what I could try to get it working?
Best,
Sandro
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
Justin Edelson wrote Can I change my vote to a -1 due to SLING-1848? Sure, you can change your vote at anytime during the voting period. Please state, if you vote -1 for all releases or just the scripting core. Thanks Carsten On Tue, Oct 19, 2010 at 10:39 AM, Justin Edelson justinedel...@gmail.com wrote: +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 Scripting JSP-Taglib 2.1.0 Changes in these releases: Apache Sling Scripting Core 2.0.12 https://issues.apache.org/jira/browse/SLING/fixforversion/12314797 Apache Sling Scripting JavaScript 2.0.8 https://issues.apache.org/jira/browse/SLING/fixforversion/12314406 Apache Sling Scripting JSP 2.0.10 https://issues.apache.org/jira/browse/SLING/fixforversion/12314407 Apache Sling Scripting JSP-Taglib 2.1.0 https://issues.apache.org/jira/browse/SLING/fixforversion/12314408 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-004/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 004 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards Carsten -- Carsten Ziegeler cziege...@apache.org
Hudson build is back to normal : sling-trunk-1.5 » Apache Sling Launchpad Application Builder #934
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad/934/
Hudson build is unstable: sling-trunk-1.5 #934
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/934/changes
Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #621
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/621/
Hudson build is still unstable: sling-trunk-1.6 #621
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes
Re: Debugging JavaScript esp files
Hi Felix, Am 19.10.10 13:41, schrieb Felix Meschberger: 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 box Eclipse tells it cannot resolve the line number to set the breakpoint on. I had the same problem first. But after adding *.esp to the JavaScript content type and then opening the esp file with the JavaScript editor it worked without problems. 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 would fit in or what to configure to make it fit. Maybe it could be triggered during ...scripting.javascript.internal.RhinoJavaScriptEngine.eval(). Do you have an idea? Actually from my traces I see, that the Eclipse rhino.debugger bundle in facts replies to the compilationDone event and informs the Eclipse debugger about this. This sounds good. What did you do to trigger the compilationDone event? If that works I get some example scripts from the server and can then try to find a mapping for the paths. I wrote a simple /apps/nt/folder/html.esp script and then requested a folder from Sling. This causes the html.esp script to be loaded and thus the compilationDone event is sent and handled. I did not have to do anything else. I tried to load the script with and without the org.apache.sling.scripting.javascript.debug property being enabled (though this should not make a difference). But the compilationDone event is not triggered. Do you have an idea what might be different in your environment? Best, Sandro Regards Felix Then the Eclipse debugger is probably supposed to send back breakpoints for the script but fails to do so because of script path issues: Sling reports script paths as they exist in Sling, e.g. /apps/sling/nt/folder.html. Eclipse on the other hand (I am creating a folder linking to a WebDAV mount of Sling) reports the script path as the project IPath, that is prefixed with the project name and path to the linked script folder. In the end the Eclipse debugger is not able to match the script reported from rhino.debugger in Sling with the script in Eclipse ... I once debugged this and hacked the correct path into and in fact was able to break a script and step through it. But we probably really need some way of mapping the script paths ... I just didn't find out how to, for example, set a prefix to cut off to get the actual script path from the project's path. Thanks for the details. Best, Sandro
Re: Debugging JavaScript esp files
Hi Felix, Am 17.10.10 20:28, schrieb Felix Meschberger: Hi, On 17.10.2010 16:05, Sandro Boehme wrote: Hi Felix, thanks for the feedback. The Swing debugger GUI doesn't seem to work in this case as it cannot open e.g. the explorer.esp file. It says: Syntax error (.../explorer.esp#83) This refers to the line containing only form action=# which is correct in my opinion. I would expect the line to be correct, but I must admit to not have used this for quite some time, so ... this may really not properly work (unfortunately). it does actually work in my environment too. I was just expecting that I have to open the esp file using the menu of the Swing client and then have to set a breakpoint there. But that results in the error I described above. I didn't know that the script loads automatically into the Swing GUI as soon as it is accessed and loaded on the webserver. Best, Sandro Am 16.10.10 20:22, schrieb Felix Meschberger: Hi Sandro, The best solution (which I once considered working on a long time ago but never got around to implement) is to have Rhino debugging support in Eclipse. But for now, you may set the org.apache.sling.scripting.javascript.debug framework property (e.g. in the sling.properties file) to true. When this property is set to true Rhino will launch the Swing debugger GUI (on the server system) once the Rhino ScriptEngineFactory is started. Regards Felix On 16.10.2010 15:36, Sandro Boehme wrote: Hello, I'm trying to get into the Sling Explorer and I'm wondering how (or if) you guys debug these esp scripts? While the Eclipse debugger stops in jsp files it doesn't stop in esp files as they don't contain Java code. Is there a special JSR-223 debugger plugin or some trick I don't know of? Best, Sandro
