[jira] [Commented] (SLING-3213) Resource hasChildren Convenience Method
[ https://issues.apache.org/jira/browse/SLING-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807759#comment-13807759 ] Carsten Ziegeler commented on SLING-3213: - I think the api.resource package version does not need to be updated in this case, as we already have changes in there which caused the version to be updated. A resource by itself can't tell if it has children - this needs to go through the resource resolver and providers. For example, if there is a node at /bin in the repository without any children, but a resource provider mounts resources at /bin/foo the jcr resource can't tell whether it has children. So if we want to have such a method, we should add it to the resource resolver (hasChildren(Resource)) make AbstractResource call this method. Resource hasChildren Convenience Method --- Key: SLING-3213 URL: https://issues.apache.org/jira/browse/SLING-3213 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.4.2 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: features, patch Attachments: has-children.diff Add a method to the Resource interface for checking if a resource has child resources. This could either invoke an underlying implementation's equivalent method or simply invoke listResources().hasNext() if the underlying implementation does not have an appropriate method. I also added an EL function since the function naming isn't JavaBean compliant. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: Health checks execution service
I'm not sure if a separate interface is a good thing - this requires the developer to choose and if we makes the wrong choice there is no way to correct this other than changing the implementation - and if we consider today that 1 minutes is the limit but decide tomorrow that it's 30 seconds this gets even more complicated (I just picked random time intervals here). So maybe, if we go with the executor service and have additional metadata (service properties) on the health checks indicating if they are long running etc. this could be handled in the executor service. Of course, this would require that a client of a health check always uses the executor service, but I think that's fine Carsten 2013/10/28 Felix Meschberger fmesc...@adobe.com Hi Apart from JMX (which is a separate biest), I agree, that we have to think about fixing the long-running check issue. How about a „LongRunningHealthCheck“ service ? Such services would be picked up by the HealthCheck infrastructure and execute as tasks (maybe the service properties could even provide scheduling properties). The HealthCheck infra would then register HealthCheck service object providing the most recent results from the LongRunningHealthCheck tasks. Regards Felix — Felix Meschberger | Principal Scientist | Adobe Am 28.10.2013 um 10:11 schrieb Bertrand Delacretaz bdelacre...@apache.org : Hi, Looking at SLING-3207 I think this deserves a bit more discussion: I don't think this is only about JMX, and providing an executor service that takes care of caching and async execution can help make the individual health checks simpler. From a client's point of view I would suggest the following behavior: 1) Executing a health check (via a new HealthCheckExecutor service that we'll add) is guaranteed to take a most T msec (configurable) 2) If an individual health check's execute() method takes longer that T, the executor returns the last result that was previously computed, or an empty result with state=NODATA if we don't have that yet. The Result contains the timestamp of when it was computed. 3) The executor service prevents concurrent execution of a given health check This is very similar to how an HTTP cache works, except that in 2) we return an old result instead of waiting. With this we can drop the execute() method must be fast requirement (within reasonable bounds) which can simplify the actual health check implementations. WDYT? -Bertrand -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-3209) Deploying files via Install bundles directly from local directory does not work properly
[ https://issues.apache.org/jira/browse/SLING-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807780#comment-13807780 ] Robert Munteanu commented on SLING-3209: Right now we expect the project to place all required data in its output directory. If data is missing, the deployment will not work properly. How do you see this improved? Deploying files via Install bundles directly from local directory does not work properly -- Key: SLING-3209 URL: https://issues.apache.org/jira/browse/SLING-3209 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Maciej Matuszewski Priority: Minor Fix For: Sling Eclipse IDE 1.0.0 If you specify how to install artifacts to the launchpad instance as Install bundles directly from local directory, application crushes. This is caused by not sending all required data e.g. OSGI-INF content. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3208) Port number from server settings is not used for sling:install
[
https://issues.apache.org/jira/browse/SLING-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3208.
Resolution: Won't Fix
Fix Version/s: (was: Sling Eclipse IDE 1.0.0)
We've moved away from using Maven for bundle deployment, so this no longer
applies.
Port number from server settings is not used for sling:install
--
Key: SLING-3208
URL: https://issues.apache.org/jira/browse/SLING-3208
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Maciej Matuszewski
Priority: Minor
Attachments: wrong_port.png
In server setting you can set Port number in Connection section, however this
port is not used for sling:install action. Maven uses default 8080. Changing
this setting is available only via maven plugin configuration e.g.
{code:xml}
plugin
groupIdorg.apache.sling/groupId
artifactIdmaven-sling-plugin/artifactId
version2.0.5-SNAPSHOT/version
configuration
useradmin/user
passwordadmin/password
slingUrl http://localhost:5502/system/console /slingUrl
/configuration
/plugin
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: Health checks execution service
On Tue, Oct 29, 2013 at 9:11 AM, Carsten Ziegeler cziege...@apache.org wrote: ...maybe, if we go with the executor service and have additional metadata (service properties) on the health checks indicating if they are long running etc. this could be handled in the executor service... While the intention is fine I don't think this can be more than a hint - a health check that calls an external service, for example, might usually execute very quickly, and take very long when TCP timeouts happen. My suggestion earlier in this thread takes the execution time into account dynamically, so no need for metadata, it's reality driven ;-) ...Of course, this would require that a client of a health check always uses the executor service, but I think that's fine... I agree with that, the alternative would be to manipulate the health checks bytecode, but that sounds complicated for not much benefits. -Bertrand
[jira] [Commented] (SLING-3209) Deploying files via Install bundles directly from local directory does not work properly
[ https://issues.apache.org/jira/browse/SLING-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807804#comment-13807804 ] Stefan Egli commented on SLING-3209: Could it be due to the maven-scr-plugin not being configured properly in the pom and/or not picked up by m2e's lifecycle mapping? [~rombert], could we try to come up with some sanity check for such a case? Wouldn't know how exactly though.. But maybe this could become a frequent case that people stumble upon.. Deploying files via Install bundles directly from local directory does not work properly -- Key: SLING-3209 URL: https://issues.apache.org/jira/browse/SLING-3209 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Maciej Matuszewski Priority: Minor Fix For: Sling Eclipse IDE 1.0.0 If you specify how to install artifacts to the launchpad instance as Install bundles directly from local directory, application crushes. This is caused by not sending all required data e.g. OSGI-INF content. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3210) Oak login fails in DavExDisabledAnonAccessTest
[ https://issues.apache.org/jira/browse/SLING-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3210. Resolution: Fixed Thanks for the clarification, I have removed the extra test in revision 1536617 - the other tests do indeed fail if I remove the dummy service registration in the org.apache.sling.jcr.davex bundle. Oak login fails in DavExDisabledAnonAccessTest -- Key: SLING-3210 URL: https://issues.apache.org/jira/browse/SLING-3210 Project: Sling Issue Type: Bug Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor The DavExIntegrationTest base class uses repository.login(default), without credentials, which is not supported by Oak as per http://jackrabbit.apache.org/oak/docs/differences.html As a result, the login correctly fails, causing the test to fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3209) Deploying files via Install bundles directly from local directory does not work properly
[
https://issues.apache.org/jira/browse/SLING-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807813#comment-13807813
]
Robert Munteanu commented on SLING-3209:
What I can think of is inspecting the MANIFEST.MF and looking for a
Service-Component header . If that header exists, ensure that it matches
something in the project output directory. Of course, things can get hairy if
we have a header which is {{OSGI-INF/*.xml}} .
I'm not sure that this is 100% correct, but that's what we can do and is
pretty much agnostic to how the application is assembled. This can be only one
of the pre-deployment rules that we have, as I think there is more to be done
in the future.
Deploying files via Install bundles directly from local directory does not
work properly
--
Key: SLING-3209
URL: https://issues.apache.org/jira/browse/SLING-3209
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Maciej Matuszewski
Priority: Minor
Fix For: Sling Eclipse IDE 1.0.0
If you specify how to install artifacts to the launchpad instance as Install
bundles directly from local directory, application crushes. This is caused by
not sending all required data e.g. OSGI-INF content.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SLING-3153) Sling project overlay conflicts with the version control overlay
[ https://issues.apache.org/jira/browse/SLING-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807818#comment-13807818 ] Robert Munteanu commented on SLING-3153: Hm, not sure. Let's leave this tentatively as 'remove decorator' until we get closer to releasing 1.0.0 and make the change then. It's an easy change and with low risk. Sling project overlay conflicts with the version control overlay Key: SLING-3153 URL: https://issues.apache.org/jira/browse/SLING-3153 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: java-faceted-project-decoration.png, screenshot.png The 'S' overlay which is present on Sling projects conflicts with the Version control overlay, as defined in the [Eclipse UI guidelines|http://wiki.eclipse.org/User_Interface_Guidelines] - search for 'Version Control'. As such , I think we should find a different way of decorating Sling projects, or even remove the decorator altogether. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3209) Deploying files via Install bundles directly from local directory does not work properly
[ https://issues.apache.org/jira/browse/SLING-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807819#comment-13807819 ] Stefan Egli commented on SLING-3209: Right. Double-checking the Service-Component property of the manifest sounds like a good first step and shouldn't have any side-effects. Deploying files via Install bundles directly from local directory does not work properly -- Key: SLING-3209 URL: https://issues.apache.org/jira/browse/SLING-3209 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Maciej Matuszewski Priority: Minor Fix For: Sling Eclipse IDE 1.0.0 If you specify how to install artifacts to the launchpad instance as Install bundles directly from local directory, application crushes. This is caused by not sending all required data e.g. OSGI-INF content. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3100) Provide a m2e project configurator for packaging content-package
[ https://issues.apache.org/jira/browse/SLING-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807829#comment-13807829 ] Robert Munteanu commented on SLING-3100: [~henzlerg] - thanks the contribution! I haven't had time to review this in depth, but it looks good overall. Right now I think this is useful, but unfortunately the manen-content-package-plugin is not Open Source, but accessible only to users of AEM. It's a bit similar to the situation we had with FileVault - we could not use it until it was released at ASF. So I think that right now this contribution should remain in a pending state, until all the bits and pieces are available in the open. Provide a m2e project configurator for packaging content-package -- Key: SLING-3100 URL: https://issues.apache.org/jira/browse/SLING-3100 Project: Sling Issue Type: New Feature Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Konrad Windszus Fix For: Sling Eclipse IDE 1.0.2 Attachments: SLING-3100-m2e-integration.patch To set up the appropriate project configuration just from the POM an according m2e project configurator is needed (http://wiki.eclipse.org/M2E_plugin_execution_not_covered#delegate_to_a_project_configurator_.28recommended.29) The m2e-war-plugin comes with a project configurator which works also for content-packages pretty well but it is currently hard to reuse for any other packaging than war (due to the delegate pattern being used internally, compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=412213). Only if the project is having the dynamic web project facet the following features in Eclipse are supported: - JSP include directives (considered for validation and supports ctrl+click to open linked file) - Tag Library Support ( http://wiki.eclipse.org/WTP_FAQ#Why_isn.27t_the_JSP_editor.2Fvalidator_finding_my_custom_tag_libraries.3F ) - probably other features as well. Apart from that a feature like overlays should be supported ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=384154 ), as often content-package projects are referencing JSPs from other projects, and the IDE needs to know those, to complete the validation. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3100) Provide a m2e project configurator for packaging content-package
[ https://issues.apache.org/jira/browse/SLING-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807848#comment-13807848 ] Konrad Windszus commented on SLING-3100: [~rombert] - do you have any information when the content-package plugin will be Open Source as well? Otherwise we would need to come up with our own custom plugin to configure content-packages correctly. Right now there is already a dependency on content-package within the source code (org.apache.sling.ide.eclipse.core.internal.ProjectHelper) .You can only convert to a sling project in case the packaging is content-package. Therefore I would prefer to have it right now included in the Sling IDE Tooling. As soon as the content-package is open source we could think about moving the configurator to a separate plugin (probably linking it in the m2e marketplace, http://wiki.eclipse.org/Submitting_M2E_marketplace_entries). What do you think? Provide a m2e project configurator for packaging content-package -- Key: SLING-3100 URL: https://issues.apache.org/jira/browse/SLING-3100 Project: Sling Issue Type: New Feature Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Konrad Windszus Fix For: Sling Eclipse IDE 1.0.2 Attachments: SLING-3100-m2e-integration.patch To set up the appropriate project configuration just from the POM an according m2e project configurator is needed (http://wiki.eclipse.org/M2E_plugin_execution_not_covered#delegate_to_a_project_configurator_.28recommended.29) The m2e-war-plugin comes with a project configurator which works also for content-packages pretty well but it is currently hard to reuse for any other packaging than war (due to the delegate pattern being used internally, compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=412213). Only if the project is having the dynamic web project facet the following features in Eclipse are supported: - JSP include directives (considered for validation and supports ctrl+click to open linked file) - Tag Library Support ( http://wiki.eclipse.org/WTP_FAQ#Why_isn.27t_the_JSP_editor.2Fvalidator_finding_my_custom_tag_libraries.3F ) - probably other features as well. Apart from that a feature like overlays should be supported ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=384154 ), as often content-package projects are referencing JSPs from other projects, and the IDE needs to know those, to complete the validation. -- This message was sent by Atlassian JIRA (v6.1#6144)
sling:match and mapping
Hi, if I read [1] right, it is possible to use backreferences to matching groups in the path for creating the URL in RR.map() Does this outdate the warning regarding usage of regular expressions on [2]? It now says Since the entries in the /etc/map are also used to reverse map any resource paths to URLs, using regular expressions in the Root Level Mappings prevent the respective entries from being used for reverse mappings. Therefor, it is strongly recommended to not use regular expression matching, unless you have a strong need. Would it make sense to change the last sentence to the following or similar? Therefore, it is strongly recommended to only use regular expression matching in sling:match if you set up corresponding entries using regular expressions in sling:internalRedirect and backreferences in sling:match to allow the resolutions enabled by regex matching to be matched back when mapping content paths to URLs [1] https://issues.apache.org/jira/browse/SLING-2560 [2] http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html Cheers Ben -- Ben Peter M: +49 151 27580088
[jira] [Commented] (SLING-3210) Oak login fails in DavExDisabledAnonAccessTest
[ https://issues.apache.org/jira/browse/SLING-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807856#comment-13807856 ] Felix Meschberger commented on SLING-3210: -- Instead of admin credentials, I suggest to use GuestCredentials which is the right way to get anonymous access to the repository. Oak login fails in DavExDisabledAnonAccessTest -- Key: SLING-3210 URL: https://issues.apache.org/jira/browse/SLING-3210 Project: Sling Issue Type: Bug Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor The DavExIntegrationTest base class uses repository.login(default), without credentials, which is not supported by Oak as per http://jackrabbit.apache.org/oak/docs/differences.html As a result, the login correctly fails, causing the test to fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3212) JUnit retry Rule, for integration tests mostly
[ https://issues.apache.org/jira/browse/SLING-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3212. Resolution: Fixed RetryRule and tests implemented in http://svn.apache.org/r1536640 JUnit retry Rule, for integration tests mostly -- Key: SLING-3212 URL: https://issues.apache.org/jira/browse/SLING-3212 Project: Sling Issue Type: New Feature Components: Testing Affects Versions: Commons Testing 2.0.14 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Testing 2.0.16 Attachments: SLING-3212-proof-of-concept.patch Some of our integration tests have been randomly failing from time to time, and with the move to Oak which has slightly different reaction times, especially in JCR observation, this is a more obvious problem. Those tests usually assume that changing things in Sling has immediate effects, and this is not always the case, while uploading or changing scripts or configurations for example. There might be slight delays which are not problematic in real use, but can make such tests fail. Retrying the tests, with a small configurable delay between retries, should take care of those problems. I'll attach a prototype JUnit Rule that enables test retries by just instantiating the Rule in the test and adding an @Rule annotation to methods that need it. My current plan is to add this Rule to our commons/testing module, and we'll also need to slightly rework our base test classes to make them usable in JUnit4-style tests, which is required to use Rules. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3212) JUnit retry Rule, for integration tests mostly
[ https://issues.apache.org/jira/browse/SLING-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3212: --- Affects Version/s: Commons Testing 2.0.14 Fix Version/s: Commons Testing 2.0.16 JUnit retry Rule, for integration tests mostly -- Key: SLING-3212 URL: https://issues.apache.org/jira/browse/SLING-3212 Project: Sling Issue Type: New Feature Components: Testing Affects Versions: Commons Testing 2.0.14 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Testing 2.0.16 Attachments: SLING-3212-proof-of-concept.patch Some of our integration tests have been randomly failing from time to time, and with the move to Oak which has slightly different reaction times, especially in JCR observation, this is a more obvious problem. Those tests usually assume that changing things in Sling has immediate effects, and this is not always the case, while uploading or changing scripts or configurations for example. There might be slight delays which are not problematic in real use, but can make such tests fail. Retrying the tests, with a small configurable delay between retries, should take care of those problems. I'll attach a prototype JUnit Rule that enables test retries by just instantiating the Rule in the test and adding an @Rule annotation to methods that need it. My current plan is to add this Rule to our commons/testing module, and we'll also need to slightly rework our base test classes to make them usable in JUnit4-style tests, which is required to use Rules. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3214) Adapt HttpTestBase to make it reusable in JUnit4-style tests
Bertrand Delacretaz created SLING-3214: -- Summary: Adapt HttpTestBase to make it reusable in JUnit4-style tests Key: SLING-3214 URL: https://issues.apache.org/jira/browse/SLING-3214 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: Commons Testing 2.0.14 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Testing 2.0.16 The HttpTestBase was created as a base class for JUnit3-style tests, but with slight changes it can also be used in JUnit4-style tests. I'll make some protected things public to make it possible to reuse the class as a utility, without requiring inheritance, and include some utility methods that are provided by derived classes in our integration tests. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3100) Provide a m2e project configurator for packaging content-package
[
https://issues.apache.org/jira/browse/SLING-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807866#comment-13807866
]
Robert Munteanu commented on SLING-3100:
{quote}Robert Munteanu - do you have any information when the content-package
plugin will be Open Source as well? {quote} Unforutunately I don't.
{quote}Right now there is already a dependency on content-package within the
source code (org.apache.sling.ide.eclipse.core.internal.ProjectHelper) .You can
only convert to a sling project in case the packaging is
content-package{quote} That's unfortunate IMO and should be removed - see
SLING-3136 .
I think this discussion is better brought to dev@sling.apache.org, as there are
implications beyond the technical level, so please feel free to make that case
over there.
Provide a m2e project configurator for packaging content-package
--
Key: SLING-3100
URL: https://issues.apache.org/jira/browse/SLING-3100
Project: Sling
Issue Type: New Feature
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Konrad Windszus
Fix For: Sling Eclipse IDE 1.0.2
Attachments: SLING-3100-m2e-integration.patch
To set up the appropriate project configuration just from the POM an
according m2e project configurator is needed
(http://wiki.eclipse.org/M2E_plugin_execution_not_covered#delegate_to_a_project_configurator_.28recommended.29)
The m2e-war-plugin comes with a project configurator which works also for
content-packages pretty well but it is currently hard to reuse for any other
packaging than war (due to the delegate pattern being used internally,
compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=412213). Only if
the project is having the dynamic web project facet the following features in
Eclipse are supported:
- JSP include directives (considered for validation and supports ctrl+click
to open linked file)
- Tag Library Support (
http://wiki.eclipse.org/WTP_FAQ#Why_isn.27t_the_JSP_editor.2Fvalidator_finding_my_custom_tag_libraries.3F
)
- probably other features as well.
Apart from that a feature like overlays should be supported (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=384154 ), as often
content-package projects are referencing JSPs from other projects, and the
IDE needs to know those, to complete the validation.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Build failed in Jenkins: sling-trunk-1.7 #389
See https://builds.apache.org/job/sling-trunk-1.7/389/changes Changes: [bdelacretaz] SLING-3210 - testDavexServletAccess not needed, the other test fails if the dummy service registration is removed in org.apache.sling.jcr.davex -- [...truncated 39820 lines...] [INFO] Checking legal files in: org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/bundleList.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-bundlelist.xml [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #389
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/389/
Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #389
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/389/ -- [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/ (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.transaction/1.0.0/org.apache.sling.fragment.transaction-1.0.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.transaction-1.0.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.javax.activation/0.1.0/org.apache.sling.javax.activation-0.1.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.javax.activation-0.1.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.ws/1.0.2/org.apache.sling.fragment.ws-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.ws-1.0.2.jar [INFO] Copying bundle from
Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #390
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/390/ -- [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/ (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.7/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.transaction/1.0.0/org.apache.sling.fragment.transaction-1.0.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.transaction-1.0.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.javax.activation/0.1.0/org.apache.sling.javax.activation-0.1.0.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.javax.activation-0.1.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.ws/1.0.2/org.apache.sling.fragment.ws-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.ws-1.0.2.jar [INFO] Copying bundle from
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #390
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/390/
Build failed in Jenkins: sling-trunk-1.7 #390
See https://builds.apache.org/job/sling-trunk-1.7/390/changes Changes: [bdelacretaz] SLING-3212 - JUnit RetryRule implementation -- [...truncated 37662 lines...] [INFO] Checking legal files in: org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing/target/bundleList.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-bundlelist.xml [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.transaction/1.0.0/org.apache.sling.fragment.transaction-1.0.0.jar to
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2022
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2022/ -- Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Sling Resource-Based Discovery Service 1.0.1-SNAPSHOT Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.discovery.impl --- Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ org.apache.sling.discovery.impl --- Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.discovery.impl --- [INFO] Executing tasks main: [INFO] Executed tasks Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:00 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ org.apache.sling.discovery.impl --- Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.discovery.impl --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.discovery.impl --- [INFO] Executing tasks main: [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 Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:compile (default-compile) @ org.apache.sling.discovery.impl --- [INFO] Compiling 30 source files to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/classes Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 11:50:01 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-scr-plugin:1.14.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.discovery.impl --- [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.discovery.impl.Config.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/org.apache.sling.discovery.impl.cluster.ClusterViewServiceImpl.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/org.apache.sling.discovery.impl.cluster.voting.VotingHandler.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.xml [INFO] Writing 1 Service Component Descriptors to
Build failed in Jenkins: sling-trunk-1.6 #2022
See https://builds.apache.org/job/sling-trunk-1.6/2022/changes Changes: [bdelacretaz] SLING-3212 - JUnit RetryRule implementation [bdelacretaz] SLING-3210 - testDavexServletAccess not needed, the other test fails if the dummy service registration is removed in org.apache.sling.jcr.davex -- [...truncated 22878 lines...] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Default GET Servlets . SUCCESS [19.985s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Default POST Servlets SUCCESS [18.292s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Compat Servlets .. SUCCESS [22.246s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting Implementation API . SUCCESS [19.842s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting Core implementation SUCCESS [23.633s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting JavaScript Support . SUCCESS [49.454s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting JSP Support SUCCESS [18.425s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSP Tag Library .. SUCCESS [15.739s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSP Standard Tag Library . SUCCESS [17.373s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Adapter Manager Implementation ... SUCCESS [18.721s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Bundle Resource Provider . SUCCESS [14.810s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery API SUCCESS [11.073s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource-Based Discovery Service . FAILURE [3:01.576s] Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery Support Bundle . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery Standalone Implementation .. SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Event Support SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Filesystem Resource Provider . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling javax.activation bundle .. SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Settings . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Dumper SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Web Console Branding . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Web Console Security Provider SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Groovy Extensions SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Explorer . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check Core SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check Samples . SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check Support Components .. SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check MBeans .. SKIPPED Oct 29, 2013 11:52:51 AM org.apache.maven.cli.event.ExecutionEventLogger
content-package-maven-plugin and tooling around it
Hi, unfortunately right now Sling only supports OSGi bundles as a deployable artifacts (however, the bundles might be extended by JCR content with the help of [0]). On the other hand there is already the content-package-maven-plugin from Adobe [1], which wraps parts of a JCR repository into a deployable artifact (leveraging the JackrabbitFileVaultFS [2]). I would like to extend the Sling IDE Tooling with a custom m2e project configurator for the packaging “content-package”. Right now the patch is not integrated because of the unclear status of the content-package-maven-plugin [3]. Is it supposed to become Open Source like FileVault as indicated in [4]? Do you think that such a m2e project configurator should become part of the Sling IDE Tooling? Thanks for your input on this topic, Konrad [0] - http://sling.apache.org/site/content-loading-jcrcontentloader.html [1] - http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html [2] - http://wiki.apache.org/jackrabbit/JackrabbitFileVaultFS [3] - https://issues.apache.org/jira/browse/SLING-3100 [4] - http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201305.mbox/%3CCAB+dfim97qLN=mv+dleddovvsh5j6puq_2nd9gbr7djo3in...@mail.gmail.com%3E
[jira] [Created] (SLING-3215) Use RetryRule in integration tests to avoid timing-related issues
Bertrand Delacretaz created SLING-3215: -- Summary: Use RetryRule in integration tests to avoid timing-related issues Key: SLING-3215 URL: https://issues.apache.org/jira/browse/SLING-3215 Project: Sling Issue Type: Improvement Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor We should use the SLING-3212 retry rule in integration tests that assume things happen instantly, as this is not always the case. Tests need to be converted to JUnit4 style for that, SLING-3214 will help make that transition. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3214) Adapt HttpTestBase to make it reusable in JUnit4-style tests
[ https://issues.apache.org/jira/browse/SLING-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3214. Resolution: Fixed Implemented in http://svn.apache.org/r1536691, verified by adapting two integration tests for SLING-3215. We might need further adaptions when we move other tests to JUnit4, but the basics are here. Adapt HttpTestBase to make it reusable in JUnit4-style tests Key: SLING-3214 URL: https://issues.apache.org/jira/browse/SLING-3214 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: Commons Testing 2.0.14 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Commons Testing 2.0.16 The HttpTestBase was created as a base class for JUnit3-style tests, but with slight changes it can also be used in JUnit4-style tests. I'll make some protected things public to make it possible to reuse the class as a utility, without requiring inheritance, and include some utility methods that are provided by derived classes in our integration tests. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3215) Use RetryRule in integration tests to avoid timing-related issues
[ https://issues.apache.org/jira/browse/SLING-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807977#comment-13807977 ] Bertrand Delacretaz commented on SLING-3215: Jsp* tests converted in http://svn.apache.org/r1536704 , @Retry added where needed Use RetryRule in integration tests to avoid timing-related issues - Key: SLING-3215 URL: https://issues.apache.org/jira/browse/SLING-3215 Project: Sling Issue Type: Improvement Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor We should use the SLING-3212 retry rule in integration tests that assume things happen instantly, as this is not always the case. Tests need to be converted to JUnit4 style for that, SLING-3214 will help make that transition. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: content-package-maven-plugin and tooling around it
Hi Konrad, On Tue, Oct 29, 2013 at 2:34 PM, Konrad Windszus konra...@gmx.de wrote: Hi, unfortunately right now Sling only supports OSGi bundles as a deployable artifacts (however, the bundles might be extended by JCR content with the help of [0]). On the other hand there is already the content-package-maven-plugin from Adobe [1], which wraps parts of a JCR repository into a deployable artifact (leveraging the JackrabbitFileVaultFS [2]). I would like to extend the Sling IDE Tooling with a custom m2e project configurator for the packaging “content-package”. Right now the patch is not integrated because of the unclear status of the content-package-maven-plugin [3]. Is it supposed to become Open Source like FileVault as indicated in [4]? Do you think that such a m2e project configurator should become part of the Sling IDE Tooling? Just to restate my opinion, I definitely think this configurator should be part of the Sling tooling. However, I'm reluctant to include it until the actual maven plugin is open-sourced. The main reason is that this will not be applicable for/testable by many users, due to its licensing/availability. Robert Thanks for your input on this topic, Konrad [0] - http://sling.apache.org/site/content-loading-jcrcontentloader.html [1] - http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html [2] - http://wiki.apache.org/jackrabbit/JackrabbitFileVaultFS [3] - https://issues.apache.org/jira/browse/SLING-3100 [4] - http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/201305.mbox/%3CCAB+dfim97qLN=mv+dleddovvsh5j6puq_2nd9gbr7djo3in...@mail.gmail.com%3E -- Sent from my (old) computer
Re: ASF Buildbot for Sling?
On Mon, Oct 28, 2013 at 10:20 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Oct 28, 2013 at 4:56 PM, Robert Munteanu rob...@lmn.ro wrote: ...FWIW, the Travis-CI service hook was enabled late last week, and Sling jobs are running at [1] ... Ah cool, sorry I forgot about that one. Are you keeping notes about that config somewhere? Something like SLING-920 is useful IMO, to have all the info in one place. Not yet, for two reasons: 1. I'm running it as an experiment, to see if building is possible 2. The change history is completely inside the travis.yml file in SVN, see [2] Robert [2]: http://svn.apache.org/viewvc/sling/trunk/.travis.yml?view=log -Bertrand [1]: https://travis-ci.org/apache/sling -- Sent from my (old) computer
Re: ASF Buildbot for Sling?
On Mon, Oct 28, 2013 at 10:23 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Oct 28, 2013 at 4:56 PM, Robert Munteanu rob...@lmn.ro wrote: FWIW, the Travis-CI service hook was enabled late last week, and Sling jobs are running at [1]... BTW it looks like those builds fail due to a timeout after 50 minutes, as per http://about.travis-ci.org/docs/user/build-configuration/#Build-Timeouts That's the exact reason for failure. I guess I need to poke it some more, and possibly split the build into multiple parts... Robert -Bertrand [1]: https://travis-ci.org/apache/sling -- Sent from my (old) computer
Build failed in Jenkins: sling-trunk-1.7 #391
See https://builds.apache.org/job/sling-trunk-1.7/391/changes
Changes:
[bdelacretaz] SLING-3215 - switch to JUnit4-style tests, to be able to use
RetryRule later
[bdelacretaz] SLING-3214 - some utility methods have moved to the new HttpTest
class
[bdelacretaz] SLING-3214 - adapt HttpTestBase and related classes for
Junit4-style tests
--
[...truncated 38480 lines...]
at java.lang.Thread.run(Thread.java:724)
/pre
h3Request Progress:/h3
pre
0 (2013-10-29 13:44:16) TIMER_START{Request Processing}
0 (2013-10-29 13:44:16) COMMENT timer_end format is {lt;elapsed
msecgt;,lt;timer namegt;} lt;optional messagegt;
0 (2013-10-29 13:44:16) LOG Method=GET,
PathInfo=/SLING457Test/1383054255756/x.foo.html
0 (2013-10-29 13:44:16) TIMER_START{ResourceResolution}
1 (2013-10-29 13:44:16) TIMER_END{1,ResourceResolution}
URI=/SLING457Test/1383054255756/x.foo.html resolves to
Resource=JcrNodeResource, type=/SLING457Test/1383054255756/b, superType=null,
path=/SLING457Test/1383054255756/x
1 (2013-10-29 13:44:16) LOG Resource Path Info: SlingRequestPathInfo:
path='/SLING457Test/1383054255756/x', selectorString='foo', extension='html',
suffix='null'
1 (2013-10-29 13:44:16) TIMER_START{ServletResolution}
1 (2013-10-29 13:44:16) TIMER_START{resolveServlet(JcrNodeResource,
type=/SLING457Test/1383054255756/b, superType=null,
path=/SLING457Test/1383054255756/x)}
9 (2013-10-29 13:44:16) TIMER_END{8,resolveServlet(JcrNodeResource,
type=/SLING457Test/1383054255756/b, superType=null,
path=/SLING457Test/1383054255756/x)} Using servlet
/SLING457Test/1383054255756/a/foo.html.jsp
9 (2013-10-29 13:44:16) TIMER_END{8,ServletResolution}
URI=/SLING457Test/1383054255756/x.foo.html handled by
Servlet=/SLING457Test/1383054255756/a/foo.html.jsp
9 (2013-10-29 13:44:16) LOG Applying Requestfilters
9 (2013-10-29 13:44:16) LOG Calling filter:
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
9 (2013-10-29 13:44:16) LOG Calling filter:
org.apache.sling.launchpad.testservices.filters.SlingFilter
9 (2013-10-29 13:44:16) LOG Calling filter:
org.apache.sling.launchpad.testservices.filters.NoPropertyFilter
9 (2013-10-29 13:44:16)
TIMER_START{/SLING457Test/1383054255756/a/foo.html.jsp#0}
830 (2013-10-29 13:44:16) LOG SCRIPT ERROR:
org.apache.sling.scripting.jsp.jasper.JasperException: Unable to compile class
for JSP
830 (2013-10-29 13:44:16)
TIMER_END{821,/SLING457Test/1383054255756/a/foo.html.jsp#0}
837 (2013-10-29 13:44:16)
TIMER_START{handleError:throwable=java.lang.NullPointerException}
843 (2013-10-29 13:44:16)
TIMER_END{6,handleError:throwable=java.lang.NullPointerException} Using handler
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
854 (2013-10-29 13:44:16) TIMER_END{854,Request Processing} Dumping
SlingRequestProgressTracker Entries
/pre
hr
addressApacheSling/2.2 (jetty/7.x.y-SNAPSHOT, Java HotSpot(TM) Server VM
1.7.0_25, Linux 3.2.0-51-generic i386)/address
/body
/html
) expected:200 but was:500
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:369)
at
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:344)
at
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:336)
at
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:331)
at
org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test.testCallFooHtml(SLING457Test.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Testing #391
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/391/ -- [...truncated 810 lines...] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) testCallFooHtml(org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test) Time elapsed: 1.284 sec FAILURE! junit.framework.AssertionFailedError: Expected status 200 for http://localhost:53063/SLING457Test/1383054255756/x.foo.html (content=!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN html head title500 Internal Server Error/title /head body h1Internal Server Error (500)/h1 pThe requested URL /SLING457Test/1383054255756/x.foo.html resulted in an error in /SLING457Test/1383054255756/a/foo.html.jsp./p h3Exception:/h3 pre java.lang.NullPointerException at org.apache.sling.jcr.classloader.internal.ClassLoaderWriterImpl.getOrCreateClassLoader(ClassLoaderWriterImpl.java:225) at org.apache.sling.jcr.classloader.internal.ClassLoaderWriterImpl.getClassLoader(ClassLoaderWriterImpl.java:551) at org.apache.sling.scripting.jsp.SlingIOProvider.getClassLoader(SlingIOProvider.java:163) at org.apache.sling.scripting.jsp.jasper.JspCompilationContext.getClassLoader(JspCompilationContext.java:134) at org.apache.sling.scripting.jsp.jasper.compiler.JDTCompiler$1.findType(JDTCompiler.java:193) at org.apache.sling.scripting.jsp.jasper.compiler.JDTCompiler$1.findType(JDTCompiler.java:163) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:97) at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:43) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveUnresolvedType(BinaryTypeBinding.java:138) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superclass(BinaryTypeBinding.java:936) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.getExactMethod(BinaryTypeBinding.java:724) at org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMethod(Scope.java:761) at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:2002) at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:384) at org.eclipse.jdt.internal.compiler.ast.Assignment.resolveType(Assignment.java:179) at org.eclipse.jdt.internal.compiler.ast.Expression.resolve(Expression.java:882) at org.eclipse.jdt.internal.compiler.ast.Block.resolveUsing(Block.java:115) at org.eclipse.jdt.internal.compiler.ast.TryStatement.resolve(TryStatement.java:751) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:432) at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:190) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:403) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1047) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1094) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:353) at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:596) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:411) at org.apache.sling.scripting.jsp.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:412) at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:312) at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:290) at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:277) at org.apache.sling.scripting.jsp.jasper.JspCompilationContext.compile(JspCompilationContext.java:501) at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.prepareServlet(JspServletWrapper.java:427) at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:486) at
[jira] [Comment Edited] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer
[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808009#comment-13808009 ] Stefan Egli edited comment on SLING-3162 at 10/29/13 2:13 PM: -- [~justinedelson], I have double-checked. The Package Explorer is not intended to be extended - ie there is no extension API for the package explorer to hook in the content browser. There might be dubious ways of hacking this in there, but I think we should rather not go there. Hence I think we have to live without the content browser in the package explorer.. was (Author: egli): [~justinedelson], I have double-checked. The Package Explorer is not intended to be extended - ie there is not extension API for the package explorer to hook in the content browser. There might be dubious ways of hacking this in there, but I think we should rather not go there. Hence I think we have to live without the content browser in the package explorer.. Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer -- Key: SLING-3162 URL: https://issues.apache.org/jira/browse/SLING-3162 Project: Sling Issue Type: Improvement Components: IDE Reporter: Justin Edelson Priority: Minor In the Java EE perspective, the default navigator view is the Project Explorer. In the Java perspective, it is the Package Explorer. Personally, I never use the Java EE perspective (and thus the Project Explorer) because Sling != JavaEE :) It seems to be OK if I just remove the Package Explorer view from the Java perspective and add the Project Explorer. But IMHO, this isn't intuitive. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer
[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3162. Resolution: Won't Fix Assignee: Stefan Egli Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer -- Key: SLING-3162 URL: https://issues.apache.org/jira/browse/SLING-3162 Project: Sling Issue Type: Improvement Components: IDE Reporter: Justin Edelson Assignee: Stefan Egli Priority: Minor In the Java EE perspective, the default navigator view is the Project Explorer. In the Java perspective, it is the Package Explorer. Personally, I never use the Java EE perspective (and thus the Project Explorer) because Sling != JavaEE :) It seems to be OK if I just remove the Package Explorer view from the Java perspective and add the Project Explorer. But IMHO, this isn't intuitive. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer
[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808009#comment-13808009 ] Stefan Egli commented on SLING-3162: [~justinedelson], I have double-checked. The Package Explorer is not intended to be extended - ie there is not extension API for the package explorer to hook in the content browser. There might be dubious ways of hacking this in there, but I think we should rather not go there. Hence I think we have to live without the content browser in the package explorer.. Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer -- Key: SLING-3162 URL: https://issues.apache.org/jira/browse/SLING-3162 Project: Sling Issue Type: Improvement Components: IDE Reporter: Justin Edelson Priority: Minor In the Java EE perspective, the default navigator view is the Project Explorer. In the Java perspective, it is the Package Explorer. Personally, I never use the Java EE perspective (and thus the Project Explorer) because Sling != JavaEE :) It seems to be OK if I just remove the Package Explorer view from the Java perspective and add the Project Explorer. But IMHO, this isn't intuitive. -- This message was sent by Atlassian JIRA (v6.1#6144)
Build failed in Jenkins: sling-trunk-1.7 #392
See https://builds.apache.org/job/sling-trunk-1.7/392/changes Changes: [bdelacretaz] SLING-2788 - more explicit fail message [bdelacretaz] Remove unused JspTestBase base class [bdelacretaz] SLING-3215 - use RetryRule in JSP integration tests [bdelacretaz] Test HTML rendering of PlanetResource -- [...truncated 11775 lines...] Oct 29, 2013 2:16:15 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.jcr.davex --- [INFO] Executing tasks main: [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 Oct 29, 2013 2:16:15 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:15 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:compile (default-compile) @ org.apache.sling.jcr.davex --- [INFO] Compiling 2 source files to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/target/classes Oct 29, 2013 2:16:15 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:15 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-scr-plugin:1.14.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.jcr.davex --- [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/target/scr-plugin-generated/OSGI-INF/org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet.xml Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.jcr.davex --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/src/test/resources [INFO] Copying 3 resources Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ org.apache.sling.jcr.davex --- [INFO] Compiling 1 source file to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/target/test-classes Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:16 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-surefire-plugin:2.12.4:test (default-test) @ org.apache.sling.jcr.davex --- [INFO] Surefire report directory: https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/jcr/davex/target/surefire-reports --- T E S T S --- Running org.apache.sling.jcr.davex.impl.servlets.AuthHttpContextTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Results : Tests run: 7, Failures: 0, Errors: 0, Skipped: 0 Oct 29, 2013 2:16:17 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:17 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- animal-sniffer-maven-plugin:1.9:check (default) @ org.apache.sling.jcr.davex --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 Oct 29, 2013 2:16:18 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:18 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-bundle-plugin:2.3.4:bundle (default-bundle) @ org.apache.sling.jcr.davex --- Oct 29, 2013 2:16:18 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:18 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ org.apache.sling.jcr.davex --- Oct 29, 2013 2:16:19 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 29, 2013 2:16:19 PM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #2023
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/2023/ -- [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/ (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.transaction/1.0.0/org.apache.sling.fragment.transaction-1.0.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.transaction-1.0.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.javax.activation/0.1.0/org.apache.sling.javax.activation-0.1.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.javax.activation-0.1.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.ws/1.0.2/org.apache.sling.fragment.ws-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.ws-1.0.2.jar [INFO] Copying bundle from
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2023
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2023/
Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2023
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2023/
Jenkins build is still unstable: sling-oak-it-1.6 #5
See https://builds.apache.org/job/sling-oak-it-1.6/changes
Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #5
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/changes
Build failed in Jenkins: sling-trunk-1.6 #2023
See https://builds.apache.org/job/sling-trunk-1.6/2023/changes Changes: [bdelacretaz] Test HTML rendering of PlanetResource [bdelacretaz] SLING-3215 - switch to JUnit4-style tests, to be able to use RetryRule later [bdelacretaz] SLING-3214 - some utility methods have moved to the new HttpTest class [bdelacretaz] SLING-3214 - adapt HttpTestBase and related classes for Junit4-style tests -- [...truncated 38153 lines...] [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/bundleList.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-bundlelist.xml [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from
[jira] [Commented] (SLING-3213) Resource hasChildren Convenience Method
[ https://issues.apache.org/jira/browse/SLING-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808052#comment-13808052 ] Justin Edelson commented on SLING-3213: --- [~cziegeler] thanks for the clarification about the package export. I missed that change. Resource hasChildren Convenience Method --- Key: SLING-3213 URL: https://issues.apache.org/jira/browse/SLING-3213 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.4.2 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: features, patch Attachments: has-children.diff Add a method to the Resource interface for checking if a resource has child resources. This could either invoke an underlying implementation's equivalent method or simply invoke listResources().hasNext() if the underlying implementation does not have an appropriate method. I also added an EL function since the function naming isn't JavaBean compliant. -- This message was sent by Atlassian JIRA (v6.1#6144)
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #2024
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/2024/ -- [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/ (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.fragment.transaction/1.0.0/org.apache.sling.fragment.transaction-1.0.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.transaction-1.0.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.javax.activation/0.1.0/org.apache.sling.javax.activation-0.1.0.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.javax.activation-0.1.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.fragment.ws/1.0.2/org.apache.sling.fragment.ws-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/ws/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.ws-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.installer/1.2.0/org.apache.sling.launchpad.installer-1.2.0.jar to
Build failed in Jenkins: sling-trunk-1.6 #2024
See https://builds.apache.org/job/sling-trunk-1.6/2024/changes Changes: [bdelacretaz] SLING-2788 - more explicit fail message [bdelacretaz] Remove unused JspTestBase base class [bdelacretaz] SLING-3215 - use RetryRule in JSP integration tests -- [...truncated 39796 lines...] [INFO] Checking legal files in: org.apache.sling.launchpad.testing-7-SNAPSHOT.jar [INFO] Checking legal files in: org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-sources.jar [INFO] Installing https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing/target/bundleList.xml to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.testing/7-SNAPSHOT/org.apache.sling.launchpad.testing-7-SNAPSHOT-bundlelist.xml [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war (includes = [derby.log, cachedir, sling, jackrabbit], excludes = []) [INFO] Executing tasks main: [INFO] Executed tasks [INFO] Using bundle list file from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/builder/target/bundleList.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/base/target/org.apache.sling.launchpad.base-2.5.1-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/slf4j-api-1.6.4.jar [INFO] Copying bundle from https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/commons/log/target/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.log-3.0.3-SNAPSHOT.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.logservice/1.0.2/org.apache.sling.commons.logservice-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.commons.logservice-1.0.2.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/jcl-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/log4j-over-slf4j-1.6.4.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.settings/1.3.0/org.apache.sling.settings-1.3.0.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.settings-1.3.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.fragment.xml/1.0.2/org.apache.sling.fragment.xml-1.0.2.jar to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/launchpad/testing-war/target/launchpad-bundles/resources/bundles/1/org.apache.sling.fragment.xml-1.0.2.jar [INFO] Copying bundle from
[jira] [Commented] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer
[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808067#comment-13808067 ] Justin Edelson commented on SLING-3162: --- [~egli] thanks a bunch for looking into this. Quite bizarre IMHO, but I agree with your conclusion. Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer -- Key: SLING-3162 URL: https://issues.apache.org/jira/browse/SLING-3162 Project: Sling Issue Type: Improvement Components: IDE Reporter: Justin Edelson Assignee: Stefan Egli Priority: Minor In the Java EE perspective, the default navigator view is the Project Explorer. In the Java perspective, it is the Package Explorer. Personally, I never use the Java EE perspective (and thus the Project Explorer) because Sling != JavaEE :) It seems to be OK if I just remove the Package Explorer view from the Java perspective and add the Project Explorer. But IMHO, this isn't intuitive. -- This message was sent by Atlassian JIRA (v6.1#6144)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2024
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2024/
[jira] [Commented] (SLING-3210) Oak login fails in DavExDisabledAnonAccessTest
[ https://issues.apache.org/jira/browse/SLING-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808071#comment-13808071 ] Justin Edelson commented on SLING-3210: --- The DavExDisabledAnonAccessTest isn't really about anonymous access to the repository. It is about when anonymous access is disabled at the Sling Auth level. A DavEx client will send one or two anonymous requests (IIRC these are PROPFIND requests to get repository descriptors) before sending authentication information. So we had to always enable anonymous acess (again at the Sling Auth level) to the DavEx servlet, otherwise these initial requests would fail. Oak login fails in DavExDisabledAnonAccessTest -- Key: SLING-3210 URL: https://issues.apache.org/jira/browse/SLING-3210 Project: Sling Issue Type: Bug Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor The DavExIntegrationTest base class uses repository.login(default), without credentials, which is not supported by Oak as per http://jackrabbit.apache.org/oak/docs/differences.html As a result, the login correctly fails, causing the test to fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3213) Resource hasChildren Convenience Method
[ https://issues.apache.org/jira/browse/SLING-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco updated SLING-3213: Attachment: (was: has-children.diff) Resource hasChildren Convenience Method --- Key: SLING-3213 URL: https://issues.apache.org/jira/browse/SLING-3213 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.4.2 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: features, patch Attachments: has-children.diff Add a method to the Resource interface for checking if a resource has child resources. This could either invoke an underlying implementation's equivalent method or simply invoke listResources().hasNext() if the underlying implementation does not have an appropriate method. I also added an EL function since the function naming isn't JavaBean compliant. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3213) Resource hasChildren Convenience Method
[ https://issues.apache.org/jira/browse/SLING-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco updated SLING-3213: Attachment: has-children.diff Carsten, Thanks for the feedback, I have made the changes you suggested. Right now, I have the resource resolver just calling listChildren(resource).hasNext(). It seems to me like the negligible performance gain from doing the check in the method would be outweighed by the cost of maintaining duplicate code. I did also leave the implementation of the method in the JcrPropertyResource since there should not be child resources of a property and listJcrChildren there already returns null. Please let me know what you think of the latest patch. Regards, Dan Resource hasChildren Convenience Method --- Key: SLING-3213 URL: https://issues.apache.org/jira/browse/SLING-3213 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.4.2 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: features, patch Attachments: has-children.diff Add a method to the Resource interface for checking if a resource has child resources. This could either invoke an underlying implementation's equivalent method or simply invoke listResources().hasNext() if the underlying implementation does not have an appropriate method. I also added an EL function since the function naming isn't JavaBean compliant. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3213) Resource hasChildren Convenience Method
[ https://issues.apache.org/jira/browse/SLING-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808444#comment-13808444 ] Carsten Ziegeler commented on SLING-3213: - Thanks for the updated patch, looks good to me Resource hasChildren Convenience Method --- Key: SLING-3213 URL: https://issues.apache.org/jira/browse/SLING-3213 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.4.2 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: features, patch Attachments: has-children.diff Add a method to the Resource interface for checking if a resource has child resources. This could either invoke an underlying implementation's equivalent method or simply invoke listResources().hasNext() if the underlying implementation does not have an appropriate method. I also added an EL function since the function naming isn't JavaBean compliant. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3216) BindingsValuesProviders do not respect service dynamics
Justin Edelson created SLING-3216: - Summary: BindingsValuesProviders do not respect service dynamics Key: SLING-3216 URL: https://issues.apache.org/jira/browse/SLING-3216 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Priority: Critical Unregistering a BindingsValuesProvider does not cause the references to it in DefaultSlingScript instances cached by the ServletResolver to be refreshed. Simiarly, registering a new BVP does not show up in cached instances. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3216) BindingsValuesProviders do not respect service dynamics
[ https://issues.apache.org/jira/browse/SLING-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3216: -- Attachment: SLING-3216.patch There's actually two different problems: 1) a change to a BVP doesn't cause the script cache to be refresh. The best solution I can come up with is to send an event. 2) unregistered BVPs aren't actually removed from the language-specific maps because the remove() call is passing in the service, not the serviceId. Attached patch handles both. However, it causes the Scripting Core ITs to fail. [~bdelacretaz] can you take a look as to why? I can't figure it out. BindingsValuesProviders do not respect service dynamics --- Key: SLING-3216 URL: https://issues.apache.org/jira/browse/SLING-3216 Project: Sling Issue Type: Bug Components: Scripting Reporter: Justin Edelson Priority: Critical Attachments: SLING-3216.patch Unregistering a BindingsValuesProvider does not cause the references to it in DefaultSlingScript instances cached by the ServletResolver to be refreshed. Simiarly, registering a new BVP does not show up in cached instances. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3216) BindingsValuesProviders do not respect service dynamics
[ https://issues.apache.org/jira/browse/SLING-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3216: -- Component/s: Servlets Affects Version/s: Servlets Resolver 2.2.4 Scripting Core 2.0.24 BindingsValuesProviders do not respect service dynamics --- Key: SLING-3216 URL: https://issues.apache.org/jira/browse/SLING-3216 Project: Sling Issue Type: Bug Components: Scripting, Servlets Affects Versions: Servlets Resolver 2.2.4, Scripting Core 2.0.24 Reporter: Justin Edelson Priority: Critical Attachments: SLING-3216.patch Unregistering a BindingsValuesProvider does not cause the references to it in DefaultSlingScript instances cached by the ServletResolver to be refreshed. Simiarly, registering a new BVP does not show up in cached instances. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3217) Automatically expose SlingBindings object through EL
Justin Edelson created SLING-3217: - Summary: Automatically expose SlingBindings object through EL Key: SLING-3217 URL: https://issues.apache.org/jira/browse/SLING-3217 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Justin Edelson JSP scripts need to use the sling:defineObjects/ (or a subclass) in order to expose the Sling Bindings objects (i.e. `resource`) for use in a JSP page. This shouldn't be necessary if we provide a custom ELResolver. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3217) Automatically expose SlingBindings object through EL
[
https://issues.apache.org/jira/browse/SLING-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-3217:
--
Attachment: SLING-3217.patch
With this patch, custom ELResolvers can be provided through OSGi services
(because that's the Sling way!)
With this patch, you still need sling:defineObjects/ to use Sling Bindings
objects in scriptlets, but not in EL expressions, so
${resource.path}
works without sling:defineObjects/
Automatically expose SlingBindings object through EL
Key: SLING-3217
URL: https://issues.apache.org/jira/browse/SLING-3217
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Justin Edelson
Attachments: SLING-3217.patch
JSP scripts need to use the sling:defineObjects/ (or a subclass) in order
to expose the Sling Bindings objects (i.e. `resource`) for use in a JSP page.
This shouldn't be necessary if we provide a custom ELResolver.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (SLING-3218) enable a list of JSP taglib prefixes to be registered automatically
Justin Edelson created SLING-3218: - Summary: enable a list of JSP taglib prefixes to be registered automatically Key: SLING-3218 URL: https://issues.apache.org/jira/browse/SLING-3218 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Justin Edelson Attachments: SLING-3218.patch To avoid boilerplate JSP code, it should be possible to configure the JSP compiler with a set of default prefixes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3218) enable a list of JSP taglib prefixes to be registered automatically
[ https://issues.apache.org/jira/browse/SLING-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3218: -- Attachment: SLING-3218.patch path exposing this through OSGi configuration enable a list of JSP taglib prefixes to be registered automatically --- Key: SLING-3218 URL: https://issues.apache.org/jira/browse/SLING-3218 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Justin Edelson Attachments: SLING-3218.patch To avoid boilerplate JSP code, it should be possible to configure the JSP compiler with a set of default prefixes. -- This message was sent by Atlassian JIRA (v6.1#6144)
