Re: Read Sling resources remotely

[Dishara Wijewardana]

Hi all,
Thanks for the links and references. I looked in to the integration tests
since eventually that is the place I should be adding the Cassandra
Provider.
I looked inside the Test classes and base tests. The integration tests
calls to HTTP REST endpoints. So there should be a place that I should be
writing something like JAX-RS using sling APIs . (ResourceProviders and
etc) ? Or am I missing something in understanding this?
Hi Ian,
Since my next step is to test this within sling runtime, what is the best
way to access my provider and read resources ? Apparently what I should be
writing is something similar to PlanetsResourceProviderTest.

On Fri, Aug 9, 2013 at 12:53 PM, Bertrand Delacretaz  wrote:

> Hi,
>
> On Fri, Aug 9, 2013 at 5:28 AM, Dishara Wijewardana
>  wrote:
> > ...Can we access sling resources from a java client ? Is there any
> > sample/links to refer ?..
>
> Besides the POST servlets docs mentioned by Shashank, this has the basics:
>
> http://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html
>
> > This is just to test the Cassandra impl on Sling...
>
> Most of our integration tests under launchpad/integration-tests use
> HTTP requests to test a Sling instance, that's probably what you want.
>
> However, in the meantime we have a more modern test framework that's
> demonstrated at testing/samples/integration-tests, you might want to
> have a look as well. Radu has been using that in his validation module
> (it-http module in org.apache.sling.validation-2.zip  patch in
> SLING-2803), I like how that makes integration tests local to a single
> module or small group of modules, that's probably a good choice in
> your case.
>
> See also
> http://sling.apache.org/documentation/tutorials-how-tos/testing-sling-based-applications.html
> for thoughts and best practices about testing.
>
> HTH,
> -Bertrand
>



-- 
Thanks
/Dishara

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1805

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1805

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.6 #1805

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #181

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Event Support #181

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #181

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 #181

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2973) [Tooling] Align Eclipse tooling to proposed structure

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735345#comment-13735345
 ] 

Robert Munteanu commented on SLING-2973:


[~kwin] - I've refreshed the p2 update site, now that SLING-2267 is fixed. You 
can open a console view ( named 'Sling console' ) which will output the 
operations in more detail. Let me know how that works for you.

That being said, I don't expect this to be usable with CQ right now, because:

* we don't yet interoperate with VLT
* we don't yet interpret .content.xml files properly

What _might_ works is defining a filters.txt file in the directory below 
jcr_root and whitelisting files you want to sync.

> [Tooling] Align Eclipse tooling to proposed structure
> -
>
> Key: SLING-2973
> URL: https://issues.apache.org/jira/browse/SLING-2973
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The current IDE tooling needs to be aligned to the structure defined at [1] . 
> We should be careful to preserve existing behaviour, but regressions in the 
> short run are acceptable since we will move to the WST framework, which is a 
> different beast altogether.
> [1]: https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (SLING-2973) [Tooling] Align Eclipse tooling to proposed structure

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735345#comment-13735345
 ] 

Robert Munteanu edited comment on SLING-2973 at 8/9/13 9:39 PM:


[~kwin] - I've refreshed the p2 update site, now that SLING-2267 is fixed. You 
can open a console view ( named 'Sling console' ) which will output the 
operations in more detail. Let me know how that works for you.

That being said, I don't expect this to be usable with CQ right now, because:

* we don't yet interoperate with VLT
* we don't yet interpret .content.xml files properly

What _might_ work is defining a filters.txt file in the directory below 
jcr_root and whitelisting files you want to sync.

(Edit: typo)

  was (Author: rombert):
[~kwin] - I've refreshed the p2 update site, now that SLING-2267 is fixed. 
You can open a console view ( named 'Sling console' ) which will output the 
operations in more detail. Let me know how that works for you.

That being said, I don't expect this to be usable with CQ right now, because:

* we don't yet interoperate with VLT
* we don't yet interpret .content.xml files properly

What _might_ works is defining a filters.txt file in the directory below 
jcr_root and whitelisting files you want to sync.
  
> [Tooling] Align Eclipse tooling to proposed structure
> -
>
> Key: SLING-2973
> URL: https://issues.apache.org/jira/browse/SLING-2973
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The current IDE tooling needs to be aligned to the structure defined at [1] . 
> We should be careful to preserve existing behaviour, but regressions in the 
> short run are acceptable since we will move to the WST framework, which is a 
> different beast altogether.
> [1]: https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2667) [Tooling] create text-only console that exposes the operations performed and their results

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2667.


Resolution: Fixed

Added 'Sling console' in 
http://svn.apache.org/viewvc?view=revision&revision=1512502 .

Updated the tracer to use the EventAdmin in 
http://svn.apache.org/viewvc?view=revision&revision=1512503

> [Tooling] create text-only console that exposes the operations performed and 
> their results
> --
>
> Key: SLING-2667
> URL: https://issues.apache.org/jira/browse/SLING-2667
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> As for SLING-2634 the operations performed and their results are tracked in 
> .metadata/trace.log .
> It would be nice having a text-only console showing those information as well.
> See also [0]
> [0] 
> https://issues.apache.org/jira/browse/SLING-2634?focusedCommentId=13484860&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13484860

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.6 #1804

[Apache Jenkins Server]

See 

Changes:

[bdelacretaz] SLING-3006 - use SlingRequestPathInfo to decompose URLs for 
webconsole plugin

[cziegeler] Add new jmx provider

[cziegeler] Use latest get servlet

[cziegeler] SLING-3008 :  Render resource type (and super type) if resource 
can't be adapted to a map in JSON

[cziegeler] SLING-3007 :  NPE in JSON Rendering if value map contains a null 
value

[cziegeler] SLING-2999 : JMX Resource Provider

[cziegeler] SLING-2999 : JMX Resource Provider

--
[...truncated 13499 lines...]
09.08.2013 16:23:27.862 *INFO* [main] 
PAXEXAM-PROBE-021850d6-4098-4053-bdcf-31bad695edf7 BundleEvent RESOLVED
09.08.2013 16:23:27.862 *INFO* [main] 
PAXEXAM-PROBE-021850d6-4098-4053-bdcf-31bad695edf7 BundleEvent STARTING
09.08.2013 16:23:27.862 *INFO* [main] 
PAXEXAM-PROBE-021850d6-4098-4053-bdcf-31bad695edf7 BundleEvent STARTED
09.08.2013 16:23:27.871 *INFO* [BundleWatcher: 1] 
PAXEXAM-PROBE-021850d6-4098-4053-bdcf-31bad695edf7 Service [81] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.872 *INFO* [BundleWatcher: 1] 
PAXEXAM-PROBE-021850d6-4098-4053-bdcf-31bad695edf7 Service [82] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.905 *INFO* [main] 
org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner running 
testFailedClassloading in reactor
09.08.2013 16:23:27.920 *INFO* [main] 
org.apache.sling.settings.impl.SlingSettingsServiceImpl No run modes active
09.08.2013 16:23:27.930 *INFO* [main] 
org.apache.sling.commons.threads.impl.DefaultThreadPool Initializing thread 
pool [ThreadPool-2712c52d-a319-407f-942f-e018b304c23b (Apache Sling Eventing 
Thread Pool)]  ...
09.08.2013 16:23:27.930 *INFO* [main] 
org.apache.sling.commons.threads.impl.DefaultThreadPool Thread pool 
[ThreadPool-2712c52d-a319-407f-942f-e018b304c23b (Apache Sling Eventing Thread 
Pool)] initialized.
09.08.2013 16:23:27.944 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.dea.DistributedEventReceiver,87] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.946 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.dea.DistributedEventSender,88] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.949 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.DistributingEventHandler,86] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.952 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.timed.TimedEventReceiver,90] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.968 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.timed.TimedEventSender,91] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.981 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.timed.TimedEventConfiguration,89] 
ServiceEvent REGISTERED
09.08.2013 16:23:27.984 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,93] ServiceEvent 
REGISTERED
09.08.2013 16:23:27.987 *INFO* [main] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,94] 
ServiceEvent REGISTERED
09.08.2013 16:23:32.998 *WARN* [Apche Sling JCR Resource Event Queue Processor 
for path '/'] org.apache.felix.eventadmin EventAdmin: Blacklisting 
ServiceReference [[org.apache.sling.event.jobs.JobManager, 
org.osgi.service.event.EventHandler, 
org.apache.sling.discovery.TopologyEventListener, java.lang.Runnable] | 
Bundle(org.apache.sling.event [66])] due to timeout!
Build timed out (after 150 minutes). Marking the build as failed.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: 
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Reactor Summary:
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: 
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JAR Resource Bundle .. SUCCESS [16.238s]
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling (Parent) . SUCCESS [5.075s]
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Sling Adapter Annotations . SUCCESS [3.636s]
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Maven Plugin to create Jackrabbit OCM descriptors  SUCCESS 
[4.649s]
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Maven Plugin for Compiling JSP Sources into Bundles  SUCCESS 
[4.035s]
Aug 9, 2013 6:44:24 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache

Build failed in Jenkins: sling-healthcheck-1.6 #82

[Apache Jenkins Server]

See 

--
[...truncated 402 lines...]
INFO: 
Aug 9, 2013 6:31:01 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
org.apache.sling.hc.samples ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
org.apache.sling.hc.samples ---
[INFO] No sources to compile
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-surefire-plugin:2.12.4:test (default-test) @ 
org.apache.sling.hc.samples ---
[JENKINS] Recording test resultsAug 9, 2013 6:31:02 PM 
org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- animal-sniffer-maven-plugin:1.9:check (default) @ 
org.apache.sling.hc.samples ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0

Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:02 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-antrun-plugin:1.7:run 
(set-bundle-required-execution-environment) @ org.apache.sling.hc.samples ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
Aug 9, 2013 6:31:03 PM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-source-plugin:2.2.1:jar (attach-sources) @ 
org.apache.sling.hc.samples ---
[INFO] Building jar: 

Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ 
org.apache.sling.hc.samples ---
[INFO] Checking legal files in: org.apache.sling.hc.samples-0.0.2-SNAPSHOT.jar
[INFO] Checking legal files in: 
org.apache.sling.hc.samples-0.0.2-SNAPSHOT-sources.jar
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-install-plugin:2.3.1:install (default-install) @ 
org.apache.sling.hc.samples ---
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT.jar
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT-sources.jar
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 6:31:03 PM org.apache.maven.cli.

Jenkins build became unstable: sling-trunk-1.7 #180

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #180

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #180

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 #179

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Installer Integration Tests #179

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-contrib-1.6 #1036

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-contrib-1.6 » Apache Sling Launchpad Contrib Testing #1036

[Apache Jenkins Server]

See 

[jira] [Comment Edited] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734944#comment-13734944
 ] 

Bertrand Delacretaz edited comment on SLING-3006 at 8/9/13 4:11 PM:


Fixed in http://svn.apache.org/r1512369 by using the SlingRequestPathInfo class 
that's used in request processing in the webconsole plugin.

The plugin can still potentially get out of sync with the actual request 
processing code as I'm embedding that class in the resolver bundle instead of 
using it via a service, but using the "official" URL decomposition code gives 
it a much better chance of being correct.

  was (Author: bdelacretaz):
Fixed in http://svn.apache.org/r1512369 by using the SlingRequestPathInfo 
class that's used in request processing in the webconsole plugin.

The plugin can still potentially get out of sync with the actual request 
processing code as I'm embedding that class in the resolver bundle, but using 
the "official" URL decomposition code gives it a much better chance of being 
correct.
  
> SlingServletResolver webconsole plugin uses custom URL decomposition code 
> that can be wrong
> ---
>
> Key: SLING-3006
> URL: https://issues.apache.org/jira/browse/SLING-3006
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.2.4
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Servlets Resolver 2.2.6
>
>
> Entering 
> http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml
>  in the /system/console/servletresolver webconsole plugin does not produce 
> the correct results as per the testDotsAroundSuffix() at [1]
> This is due to the plugin using its own DecomposedURL class which is a 
> simplified version of the SlingRequestPathInfo class.
> For now, I'll add a warning to the plugin.
> [1] 
> http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong

[Bertrand Delacretaz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz resolved SLING-3006.


   Resolution: Fixed
Fix Version/s: Servlets Resolver 2.2.6
 Assignee: Bertrand Delacretaz

Fixed in http://svn.apache.org/r1512369 by using the SlingRequestPathInfo class 
that's used in request processing in the webconsole plugin.

The plugin can still potentially get out of sync with the actual request 
processing code as I'm embedding that class in the resolver bundle, but using 
the "official" URL decomposition code gives it a much better chance of being 
correct.

> SlingServletResolver webconsole plugin uses custom URL decomposition code 
> that can be wrong
> ---
>
> Key: SLING-3006
> URL: https://issues.apache.org/jira/browse/SLING-3006
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.2.4
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Servlets Resolver 2.2.6
>
>
> Entering 
> http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml
>  in the /system/console/servletresolver webconsole plugin does not produce 
> the correct results as per the testDotsAroundSuffix() at [1]
> This is due to the plugin using its own DecomposedURL class which is a 
> simplified version of the SlingRequestPathInfo class.
> For now, I'll add a warning to the plugin.
> [1] 
> http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-3008) Render resource type (and super type) if resource can't be adapted to a map in JSON

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-3008.
-

Resolution: Fixed

Added the two values to json rendering if the resource can't be adapted to a map

> Render resource type (and super type) if resource can't be adapted to a map 
> in JSON
> ---
>
> Key: SLING-3008
> URL: https://issues.apache.org/jira/browse/SLING-3008
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Get 2.1.6
>
>
> If the resource can't be adapted to a (value) map, at least resource type and 
> resource super type (if not null) should be rendered in the json output

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3008) Render resource type (and super type) if resource can't be adapted to a map in JSON

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-3008:
---

 Summary: Render resource type (and super type) if resource can't 
be adapted to a map in JSON
 Key: SLING-3008
 URL: https://issues.apache.org/jira/browse/SLING-3008
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Get 2.1.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Servlets Get 2.1.6


If the resource can't be adapted to a (value) map, at least resource type and 
resource super type (if not null) should be rendered in the json output

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-3007) NPE in JSON Rendering if value map contains a null value

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-3007.
-

Resolution: Fixed

Added an extra null check

> NPE in JSON Rendering if value map contains a null value
> 
>
> Key: SLING-3007
> URL: https://issues.apache.org/jira/browse/SLING-3007
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Get 2.1.6
>
>
> If the value map contains a null value for a key, this fails with a NPE 
> during JSON rendering as the ResourceTraversor does not handle this case

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3007) NPE in JSON Rendering if value map contains a null value

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-3007:
---

 Summary: NPE in JSON Rendering if value map contains a null value
 Key: SLING-3007
 URL: https://issues.apache.org/jira/browse/SLING-3007
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Get 2.1.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Servlets Get 2.1.6


If the value map contains a null value for a key, this fails with a NPE during 
JSON rendering as the ResourceTraversor does not handle this case

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Event Support #1803

[Apache Jenkins Server]

See 

Jenkins build is back to normal : sling-trunk-1.6 #1803

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2999) JMX Resource Provider

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734904#comment-13734904
 ] 

Carsten Ziegeler commented on SLING-2999:
-

I've added a stub for the implementation in rev 1512336

> JMX Resource Provider
> -
>
> Key: SLING-2999
> URL: https://issues.apache.org/jira/browse/SLING-2999
> Project: Sling
>  Issue Type: New Feature
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>
> For easier rendering of JMX mbeans within Sling,  a special resource provider 
> should make the JMX information available at 
> */system/sling/monitoring/mbeans* (Configurable)
> /system/sling/monitoring/mbeans  - resource type = sling:mbeans
>  + resource sub tree with all mbeans 
> An MBean has an object name which has
> * a domain
> * properties where type and name are very common
> The domain is converted into a sub path and the properties are converted to a 
> resource name. For example: _org.apache.sling:name=test,type=hello_ creates a 
> resource _org/apache/sling/name=test,type=hello_. The name can be obtained by 
> calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might 
> need escaping (for the values and the = character) in order to create valid 
> resource names.
> Each MBean resource has at least:
> ||Property name ||Description|
> |sling:resourceType|object name of the MBean|
> |sling:resourceSuperType| sling:mbean|
> |mbean:description|The description of the MBean (optional)|
> |mbean:className|MBean class name|
> |mbean:objectName|MBean object name|
> |mbean properties|separate property for each property of the object name|
> And a child resource named _mbean:attributes_ if the MBean has attributes. 
> For each attribute a child resource of _mbean:attributes_ is created where 
> the name of the resource is the name of the attribute and:
> ||Property name ||Description|
> |sling:resourceType|Type of the attribute|
> |sling:resourceSuperType| sling:mbeanattribute|
> |mbean:description|The description of the attribute (optional)|
> |mbean:value|String representation of the value or a string array for multi 
> values|

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Launchpad Testing #178

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Installer Integration Tests #178

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.7 #178

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2987) Simplified health check services

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734873#comment-13734873
 ] 

Carsten Ziegeler commented on SLING-2987:
-

For the ResultLog:

Right now, the caller passed in a result log instance and forces the HC service 
to call appropriate log messages, finally depending if a message with a 
specific log level arrived, the result is either ok or fail.

I think, when calling the check method of the HC service, this method doesn't 
take any argument, but just returns a result object - this result object has at 
least two methods, so something like:
- (boolean)success(); (though I would prefer an enum)
- (String[]) getMessages(); // can also be a list etc.

And that's it - how the HC service does the check and how it determines whether 
it passes or not is up to the service.

I'm not sure if the messages should be structured like a log message in 
general, I would expect that we have different messages: information messages 
telling what has been tested, result messages showing and explaining the 
result, and maybe advice messages suggesting how to fix the problem, what to 
check etc. But I think this doesn't directly map to typical log levels.


Now, for scripted tests, using the log approach might be useful. So you can 
define a hc scripting api containing the ResultLog class and defining that this 
is set when a HC script is called and for this case the level of the log 
messages coming from the script is evaluated like today.



> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Data model for HealthCheck results: pass/fail or value based?

[Carsten Ziegeler]

Hi,

I've added some comments to the issue about the current api :) I think we
should not relying on log messages as the communication between a HC and
the result. The HC should create a proper result object, and the status
should be a field in that object.

I think a boolean value (failed/ok) might bot be sufficient, so I think an
enum with more values inbetween (like Jörg's API has) is better.

For the range stuff, I think we don't need this.

If we make the Result a class with setter methods, we can later on add
additional stuff if required without breaking anything.

Carsten


2013/8/9 Bertrand Delacretaz 

> Hi,
>
> Following up on SLING-2987 I'm wondering about the best way to
> represent the results of health checks.
>
> Right now the health check Result just provides a boolean isOk()
> method, along with a getStatus() that's similar to a log level (ok,
> warn, error etc.).
>
> I haven't been using the status so far, so for now it's just a
> pass/fail (along with a mini-log that provides unstructured details).
>
> Another model that might be more useful (or YAGNI...hence this
> question) would be:
>
>   public interface ResultThatHasAValue {
> // The output value of this health check
> public object getValue();
>
> // The acceptable range of our value
> public String getRange();
>
> // True if our value is in range
> public boolean isInRange();
>
>// + logs as now
> }
>
> The advantage of this value-based result is that it can also be used
> to aggregate values that might be analyzed in a finer way by external
> JMX tools (as the healthcheck results are now available via JMX).
>
> The range can be a simple mini-language with ranges like "true",
> "between 12 and 41", "> 16", "some.*Regexp", etc.
>
> WDYT, does anyone have a concrete use case for ResultThatHasAValue?
> Otherwise I'll stick with the current pass/fail (+logs) results.
>
> Note that the docs at [1] are out of date now, but if you want to play
> with the health check just build and install the two bundles found
> under contrib/extensions/healthcheck and open
> /system/console/healthcheck
>
> -Bertrand
>
> [1]
> http://sling.apache.org/documentation/bundles/sling-health-check-tool.html
>



-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Commented] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong

[Felix Meschberger (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734864#comment-13734864
 ] 

Felix Meschberger commented on SLING-3006:
--

The goal of the plugin form is to show mapping rules applied. This does very 
rudimentary string operation which is sufficient for the purpose.

Maybe your message should read something like "don't add a suffix".

> SlingServletResolver webconsole plugin uses custom URL decomposition code 
> that can be wrong
> ---
>
> Key: SLING-3006
> URL: https://issues.apache.org/jira/browse/SLING-3006
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.2.4
>Reporter: Bertrand Delacretaz
>Priority: Minor
>
> Entering 
> http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml
>  in the /system/console/servletresolver webconsole plugin does not produce 
> the correct results as per the testDotsAroundSuffix() at [1]
> This is due to the plugin using its own DecomposedURL class which is a 
> simplified version of the SlingRequestPathInfo class.
> For now, I'll add a warning to the plugin.
> [1] 
> http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734861#comment-13734861
 ] 

Bertrand Delacretaz commented on SLING-3006:


The workaround, to find out about the actual selectors, suffix and extension is 
to execute the request in question and then look at the 
/system/console/requests plugin, which displays the SlingRequestPathInfo values.

> SlingServletResolver webconsole plugin uses custom URL decomposition code 
> that can be wrong
> ---
>
> Key: SLING-3006
> URL: https://issues.apache.org/jira/browse/SLING-3006
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.2.4
>Reporter: Bertrand Delacretaz
>Priority: Minor
>
> Entering 
> http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml
>  in the /system/console/servletresolver webconsole plugin does not produce 
> the correct results as per the testDotsAroundSuffix() at [1]
> This is due to the plugin using its own DecomposedURL class which is a 
> simplified version of the SlingRequestPathInfo class.
> For now, I'll add a warning to the plugin.
> [1] 
> http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong

[Bertrand Delacretaz (JIRA)]

Bertrand Delacretaz created SLING-3006:
--

 Summary: SlingServletResolver webconsole plugin uses custom URL 
decomposition code that can be wrong
 Key: SLING-3006
 URL: https://issues.apache.org/jira/browse/SLING-3006
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Resolver 2.2.4
Reporter: Bertrand Delacretaz
Priority: Minor


Entering 
http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml
 in the /system/console/servletresolver webconsole plugin does not produce the 
correct results as per the testDotsAroundSuffix() at [1]

This is due to the plugin using its own DecomposedURL class which is a 
simplified version of the SlingRequestPathInfo class.

For now, I'll add a warning to the plugin.

[1] 
http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2999) JMX Resource Provider

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734854#comment-13734854
 ] 

Carsten Ziegeler commented on SLING-2999:
-

On the other hand, is there a problem with using "mbeans:" ? As this is not a 
jcr backed resource provider, we don't need to register the namespace in the 
repository

> JMX Resource Provider
> -
>
> Key: SLING-2999
> URL: https://issues.apache.org/jira/browse/SLING-2999
> Project: Sling
>  Issue Type: New Feature
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>
> For easier rendering of JMX mbeans within Sling,  a special resource provider 
> should make the JMX information available at 
> */system/sling/monitoring/mbeans* (Configurable)
> /system/sling/monitoring/mbeans  - resource type = sling:mbeans
>  + resource sub tree with all mbeans 
> An MBean has an object name which has
> * a domain
> * properties where type and name are very common
> The domain is converted into a sub path and the properties are converted to a 
> resource name. For example: _org.apache.sling:name=test,type=hello_ creates a 
> resource _org/apache/sling/name=test,type=hello_. The name can be obtained by 
> calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might 
> need escaping (for the values and the = character) in order to create valid 
> resource names.
> Each MBean resource has at least:
> ||Property name ||Description|
> |sling:resourceType|object name of the MBean|
> |sling:resourceSuperType| sling:mbean|
> |mbean:description|The description of the MBean (optional)|
> |mbean:className|MBean class name|
> |mbean:objectName|MBean object name|
> |mbean properties|separate property for each property of the object name|
> And a child resource named _mbean:attributes_ if the MBean has attributes. 
> For each attribute a child resource of _mbean:attributes_ is created where 
> the name of the resource is the name of the attribute and:
> ||Property name ||Description|
> |sling:resourceType|Type of the attribute|
> |sling:resourceSuperType| sling:mbeanattribute|
> |mbean:description|The description of the attribute (optional)|
> |mbean:value|String representation of the value or a string array for multi 
> values|

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.6 #1802

[Apache Jenkins Server]

See 

Changes:

[bdelacretaz] SLING-2987 - avoid com.sun dependency

--
[...truncated 29328 lines...]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JCR ClassLoader .. SUCCESS [2.327s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Initial Content Loader ... SUCCESS [4.785s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Jackrabbit Embedded Repository ... SUCCESS [5.368s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Jackrabbit UserManager Support ... SUCCESS [2.908s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[3.494s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [1.960s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Object Content Mapping ... SUCCESS [3.906s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JCR Resource Resolver  SUCCESS [1:16.156s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JCR Repository Registration .. SUCCESS [4.808s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Simple WebDAV Access to repositories . SUCCESS [3.271s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling DavEx Access to repositories . SUCCESS [3.582s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JCR WebConsole Bundle  SUCCESS [2.453s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Servlet Resolver . SUCCESS [3.905s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Default GET Servlets . SUCCESS [3.435s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Default POST Servlets  SUCCESS [4.429s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Compat Servlets .. SUCCESS [3.143s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Scripting Implementation API . SUCCESS [2.376s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Scripting Core implementation  SUCCESS [3.415s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Scripting JavaScript Support . SUCCESS [31.297s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Scripting JSP Support  SUCCESS [8.650s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JSP Tag Library .. SUCCESS [7.099s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling JSP Standard Tag Library . SUCCESS [2.956s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Adapter Manager Implementation ... SUCCESS [3.122s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Bundle Resource Provider . SUCCESS [2.319s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Discovery API  SUCCESS [2.012s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Resource-Based Discovery Service . SUCCESS [3:09.067s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Settings . SUCCESS [5.195s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Discovery Support Bundle . SUCCESS [2.380s]
Aug 9, 2013 2:22:56 PM org.apache.maven.cli.event.ExecutionEventLogger 
logReactorSummary
INFO: Apache Sling Discovery Standalone Implementation .. SUCCESS [

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1802

[Apache Jenkins Server]

See 


--
[...truncated 9348 lines...]
09.08.2013 14:22:55.867 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [90] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.868 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [91] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.868 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [92] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.868 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [93] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.869 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [94] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.869 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [95] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.869 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [96] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.870 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [97] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.870 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb Service [98] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.870 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb BundleEvent STOPPED
09.08.2013 14:22:55.871 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb BundleEvent UNRESOLVED
09.08.2013 14:22:55.872 *INFO* [main] 
PAXEXAM-PROBE-5f30f70a-dfd9-4e21-94ed-46f427e258eb BundleEvent UNINSTALLED
09.08.2013 14:22:55.873 *INFO* [FelixShutdown] org.apache.felix.framework 
BundleEvent STOPPING
09.08.2013 14:22:55.873 *INFO* [FelixDispatchQueue] org.apache.felix.framework 
FrameworkEvent PACKAGES REFRESHED
09.08.2013 14:22:55.874 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPING
09.08.2013 14:22:55.874 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit Service [81] ServiceEvent UNREGISTERING
09.08.2013 14:22:55.874 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPED
09.08.2013 14:22:55.874 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPING
09.08.2013 14:22:55.875 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPED
09.08.2013 14:22:55.876 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,108] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.877 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.InventoryPlugin,110] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.877 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,109] 
ServiceEvent UNREGISTERING
09.08.2013 14:22:55.877 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean,112] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.878 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: 
09.08.2013 14:22:55.878 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@385405,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@385405]
09.08.2013 14:22:55.879 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge,113] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.879 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge Apache Sling Job 
Event Bridge stopped on instance 83ec2c2e-56e1-4512-ad6b-f7629cbc80e3
09.08.2013 14:22:55.880 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jcr.PersistenceHandler,107] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.881 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Apache Sling Job Manager 
stopping on instance 83ec2c2e-56e1-4512-ad6b-f7629cbc80e3
09.08.2013 14:22:55.881 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Apache Sling Job Manager 
stopped on instance 83ec2c2e-56e1-4512-ad6b-f7629cbc80e3
09.08.2013 14:22:55.882 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[111] ServiceEvent UNREGISTERING
09.08.2013 14:22:55.883 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.JobConsumerManager,76] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.883 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.dea.DistributedEventSender,103] ServiceEvent 
UNREGISTERING
09.08.2013 14:22:55.884 *INF

[jira] [Commented] (SLING-2788) Sling running using Apache OAK

[Felix Meschberger (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734821#comment-13734821
 ] 

Felix Meschberger commented on SLING-2788:
--

[~bdelacretaz]

> bundles/oak/oak-server

I suggest you use bundles/jcr/oak-server, which would align nicely with 
bundles/jcr/jackrabbit-server

> Sling running using Apache OAK
> --
>
> Key: SLING-2788
> URL: https://issues.apache.org/jira/browse/SLING-2788
> Project: Sling
>  Issue Type: Wish
>  Components: General
>Reporter: Antonio Sanso
>Assignee: Ian Boston
>
>  It would be nice to have a runMode of Sling that runs on top of Apache OAK 
> [0]
> [0] http://jackrabbit.apache.org/oak/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.7 #177

[Apache Jenkins Server]

See 

Changes:

[bdelacretaz] SLING-2987 - avoid com.sun dependency

--
[...truncated 32471 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.FileUploadTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.SlingResourceTypeRenderingTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JspScriptingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JsonRenderingTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.IncludeTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.scripting.SlingJSPTaglibTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.scripting.StandaloneScriptExecutionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.PropertyRenderingTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.WebdavUploadTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.resourceprovider.PlanetsResourceProviderTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.RangeStreamingTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.HttpPingTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.NodeTypeBasedRenderingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.auth.AuthenticationResponseCodeTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ValueFromTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ContentLoaderMiscPropertyTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.GetAclTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.ModifyAceTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ExportedPackagesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.RequestAttributeTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest
http://localhost:34589/JspIncludeTest/1376057776169/text_b_1376057776183_6
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.UploadFileTest
Tests run: 4, Failures: 0

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Testing #177

[Apache Jenkins Server]

See 


--
[...truncated 591 lines...]
INFO: Startup progress 105/109
INFO: Startup progress 106/109
INFO: Startup finished.
[INFO] Surefire report directory: 


---
 T E S T S
---
Running org.apache.sling.launchpad.testing.TestAll
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2094Test
Checking if the required Sling services are started (timeout 300 seconds)...
(base URLs=http://localhost:34589 and http://localhost:34589; servlet context=)
Sling services seem to be started, continuing with integration tests.
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2085Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2617Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2522Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2082Test
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING760Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostToRootTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCopyTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletNopTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.ReferenceTypeHintTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletVersionableTest
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletMoveTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostStatusTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletDeleteTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtMoveTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtDeleteTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletImportTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletPatchTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingAutoPropertiesTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.CustomPostOperationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDateValuesTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostResponseCreatorTest
Tests

Re: [NOTE] Expect IT failures in the Sling Event bundle

[Felix Meschberger]

Hi

Just for completeness: Jackrabbit Server 2.1.2 has been released and Carsten 
(thanks) updated the reference in the Event IT bundle (to actually cut a 
release).

So the IT tests should pass again as well as the launchpad IT tests.

Regards
Felix

Am 05.08.2013 um 14:53 schrieb Felix Meschberger:

> Hi
> 
> The Sling Event bundle was depending on the Jackrabbit Server 2.1.1-SNAPSHOT 
> bundle, which caused me some grieves applying my patches for Service 
> Authentication (SLING-2944).
> 
> To fix this issue but also (and maybe more importantly) to have a clean state 
> before applying those fixes, I have started a 
> vote for the Jackrabbit Server 2.1.2 release. Until the vote has passed and 
> the binary hits the Maven Repository, we expect the Sling Event bundle 
> integration tests to fail. Sorry for the inconvenience.
> 
> (Work around would be to also update the JCR API and JCR Base dependencies to 
> the latest SNAPSHOTs and to add the Service User Mapper bundle to the 
> integration test. I don't think we should do that, though, and thus we just 
> go through these transient failures).
> 
> Regards
> Felix

Build failed in Jenkins: sling-healthcheck-1.6 #81

[Apache Jenkins Server]

See 

Changes:

[bdelacretaz] SLING-2987 - avoid com.sun dependency

--
[...truncated 319 lines...]
INFO: 
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
org.apache.sling.hc.samples ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
org.apache.sling.hc.samples ---
[INFO] No sources to compile
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-surefire-plugin:2.12.4:test (default-test) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 2:14:07 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
[JENKINS] Recording test resultsAug 9, 2013 2:14:07 PM 
org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
INFO: --- animal-sniffer-maven-plugin:1.9:check (default) @ 
org.apache.sling.hc.samples ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0

Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-antrun-plugin:1.7:run 
(set-bundle-required-execution-environment) @ org.apache.sling.hc.samples ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
Aug 9, 2013 2:14:08 PM hudson.maven.ExecutedMojo 
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-source-plugin:2.2.1:jar (attach-sources) @ 
org.apache.sling.hc.samples ---
[INFO] Building jar: 

Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ 
org.apache.sling.hc.samples ---
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ 
org.apache.sling.hc.samples ---
[INFO] Checking legal files in: org.apache.sling.hc.samples-0.0.2-SNAPSHOT.jar
[INFO] Checking legal files in: 
org.apache.sling.hc.samples-0.0.2-SNAPSHOT-sources.jar
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: 
Aug 9, 2013 2:14:08 PM org.apache.maven.cli.event.ExecutionEventLogger 
mojoStarted
INFO: --- maven-install-plugin:2.3.1:install (default-install) @ 
org.apache.sling.hc.samples ---
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT.jar
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT.pom
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.hc.samples/0.0.2-SNAPSHOT/org.apache.sling.hc.samples-0.0.2-SNAPSHOT-sources.jar
Aug 9, 2013 2:14:09 PM org.apache.maven.cli.event.ExecutionEventL

[jira] [Commented] (SLING-2987) Simplified health check services

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734813#comment-13734813
 ] 

Bertrand Delacretaz commented on SLING-2987:


Thanks for you review!

> - we don't need a ResultLog, the result can have a string (array/list) of 
> messages
> The log could maybe be part of a scripting api for hcs

Not sure what you mean - we could use a list of String for the messages, where 
by convention each one starts with the log level, like "DEBUG this is a 
message", is that what you mean? I'm not sure why you think it's better than 
what we have now - selecting logs by level is useful in the webconsole and 
maybe other places - but of course that would also work with a "structured 
string".

> - the result should not be based on the level of a log message, but have a 
> level to be set (so we need an enum for that)

You mean setting a specific level by configuration, and any logs at or above 
that are considered failures? That would work, and we can keep the current WARN 
level as the default value. See also my discussion of a different 
ResultThatHasAValue model on the dev list, having a more generic value/range 
model might be useful, in addition to the logs triggering failures.

> - the result should not hold the service, it should be a plain data object

makes sense, currently that's only used to access the info() map

> - I assume the info props of the HealthCheck are also OSGi service props?

that's a partial copy for now, might make sense to just copy all service 
properties

> - not sure if we need the HealthCheckSelector, it rather looks like an 
> utility method

Yes, it's mostly that - what do you suggest, putting that class in a util 
package and clients bundles can embed it as needed?


> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Data model for HealthCheck results: pass/fail or value based?

[Bertrand Delacretaz]

Hi,

Following up on SLING-2987 I'm wondering about the best way to
represent the results of health checks.

Right now the health check Result just provides a boolean isOk()
method, along with a getStatus() that's similar to a log level (ok,
warn, error etc.).

I haven't been using the status so far, so for now it's just a
pass/fail (along with a mini-log that provides unstructured details).

Another model that might be more useful (or YAGNI...hence this
question) would be:

  public interface ResultThatHasAValue {
// The output value of this health check
public object getValue();

// The acceptable range of our value
public String getRange();

// True if our value is in range
public boolean isInRange();

   // + logs as now
}

The advantage of this value-based result is that it can also be used
to aggregate values that might be analyzed in a finer way by external
JMX tools (as the healthcheck results are now available via JMX).

The range can be a simple mini-language with ranges like "true",
"between 12 and 41", "> 16", "some.*Regexp", etc.

WDYT, does anyone have a concrete use case for ResultThatHasAValue?
Otherwise I'll stick with the current pass/fail (+logs) results.

Note that the docs at [1] are out of date now, but if you want to play
with the health check just build and install the two bundles found
under contrib/extensions/healthcheck and open
/system/console/healthcheck

-Bertrand

[1] http://sling.apache.org/documentation/bundles/sling-health-check-tool.html

[jira] [Closed] (SLING-2742) Expose RepositoryStatistics as a JMX Bean

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2742.



Closing after release of Jackrabbit Server 2.1.2 bundle

> Expose RepositoryStatistics as a JMX Bean 
> --
>
> Key: SLING-2742
> URL: https://issues.apache.org/jira/browse/SLING-2742
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
>Reporter: Ian Boston
>Assignee: Ian Boston
> Fix For: JCR Jackrabbit Server 2.1.2
>
> Attachments: SLING-2742.patch
>
>
> Jackrabbit comes with reasonably extensive stats which should be exposed via 
> JMX for monitoring. Searching the current code base indicates that this has 
> not been done already.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2352) Move out the repository RegistrationSupport support logic to a different bundle

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2352.



Closing after release of Jackrabbit Server 2.1.2 bundle

> Move out the repository RegistrationSupport support logic to a different 
> bundle
> ---
>
> Key: SLING-2352
> URL: https://issues.apache.org/jira/browse/SLING-2352
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
>Reporter: Chetan Mehrotra
>Assignee: Felix Meschberger
>Priority: Minor
> Fix For: JCR Registration 1.0.0, JCR Jackrabbit Server 2.1.2
>
> Attachments: repository-registrar.patch
>
>
> We have a usecase where we want to embed the Sling based war within an 
> existing ear. In that mode we want to expose the repository instance 
> registered by a different bundle (other than 
> org.apache.sling.jcr.jackrabbit.server bundle) into the JNDI so that code 
> within the ear can access the repository in InVM mode
> Currently the Repository registration support logic is part of 
> org.apache.sling.jcr.jackrabbit.server bundle. However this bundle is also 
> responsible for creating and registering the Jackrabbit repository instance.
> Attached is a patch which refactors the registration logic into a different 
> bundle. 
> Points to note regarding patch
> 1. The RmiRegistrationSupport has been retained in the Jackrabbit Server 
> Bundle due to its dependency on the Jackrabbit classes
> 2. The AbstractRegistrationSupport has been moved to a different package and 
> part of exported package now and is now imported by JR Server bundle. This is 
> done to support #1 above
> 3. The component names have been retained for backward compatibility support 
> for configuration

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2923.



Closing after release of Jackrabbit Server 2.1.2 bundle

> release org.apache.sling.jcr.jackrabbit.server 2.1.1
> 
>
> Key: SLING-2923
> URL: https://issues.apache.org/jira/browse/SLING-2923
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
> Environment: Apache Karaf 3.0.0.RC1
>Reporter: Oliver Lietz
>Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.1.2
>
> Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log
>
>
> There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
> (Caused by: java.lang.ClassNotFoundException: 
> org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
> Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
> 2.1.1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2303) The default PersistanceManager used by sling launchpad is deprecated

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2303.



Closing after release of Jackrabbit Server 2.1.2 bundle

> The default PersistanceManager used by sling launchpad is deprecated
> 
>
> Key: SLING-2303
> URL: https://issues.apache.org/jira/browse/SLING-2303
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Minor
> Fix For: JCR Jackrabbit Server 2.1.2
>
> Attachments: SLING-2303.patch
>
>
> The derby persistance manager class in the repository.xml file has been 
> deprecated.
> It should be replaced with 
> org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2013) When creating the initial configuration use relative path names for the repository configuration and home

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2013.



Closing after release of Jackrabbit Server 2.1.2 bundle

> When creating the initial configuration use relative path names for the 
> repository configuration and home
> -
>
> Key: SLING-2013
> URL: https://issues.apache.org/jira/browse/SLING-2013
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
>Reporter: Felix Meschberger
>Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.1.2
>
>
> The Jackrabbit server creates a configuration on initial startup if none is 
> available from the Configuration Admin service. This configuration will 
> contain absolute path names to the repository configuration file as well as 
> the repository home directory. This makes it hard to relocate the Sling Home 
> folder because the configuration will still point to the old location.
> Instead the default configuration (unless overwritten by some framework 
> property) should use relative path names to be resolved against sling.home 
> once the repository is started/created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (SLING-2501) Expose DataStore GarbageCollector to be able to clean deleted filed from the Repository

[Felix Meschberger (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Meschberger closed SLING-2501.



Closing after release of Jackrabbit Server 2.1.2 bundle

> Expose DataStore GarbageCollector to be able to clean deleted filed from the 
> Repository
> ---
>
> Key: SLING-2501
> URL: https://issues.apache.org/jira/browse/SLING-2501
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
>Reporter: Dragos Dascalita Haut
>Assignee: Felix Meschberger
>  Labels: patch
> Fix For: JCR Jackrabbit Server 2.1.2
>
> Attachments: 
> exposing_GC_from_SlingServerRepository_to_be_able_to_clean_JCR_DataStore.patch
>
>
> Currently Sling is not exposing any mean to be able to perform GC operations 
> on a JCR Repository. In this way, a repository managing larger docs, images, 
> and especially videos, may grow in size rapidly and there is no way to clean 
> the disk when files are deleted. 
> It would be nice to have the RepositoryManager exposed through 
> SlingServerRepository, and thus be able to create a Date Store Garbage 
> Collector and clean the repository. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to stable : sling-contrib-1.6 #1034

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-contrib-1.6 » Apache Sling Launchpad Contrib Testing #1034

[Apache Jenkins Server]

See 

Re: [VOTE] Release Discovery Modules, Settings and Eventing

[Felix Meschberger]

+1

Regards
Felix

Am 09.08.2013 um 09:51 schrieb Carsten Ziegeler:

> Hi,
> 
> this vote is primarily about doing the first release of our discovery
> implementation modules (we already released the api some time ago). The
> implementation proofed to be stable/usable. In addition, we need to release
> a dependency, Sling Settigns 1.3.0 and I've also included the Sling Events
> as this makes heavy use of the discovery stuff.
> 
> So please vote for the release of
> 
> Sling Settings 1.3.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12323581
> 
> Sing Discovery Support 1.0.0
> Sling Discovery Standalone 1.0.0
> Sling Discovery Impl 1.0.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324346
> 
> Sling Eventing 3.2.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12321291
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-079/
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh079 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ]  0 Don't care
> [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> Carsten
> -- 
> Carsten Ziegeler
> cziege...@apache.org

Re: [VOTE] Release Discovery Modules, Settings and Eventing

[Daniel Klco]

+1

Dan


On Fri, Aug 9, 2013 at 6:00 AM, Mike Müller  wrote:

> +1
> best regards
> mike
>
> > -Original Message-
> > From: Carsten Ziegeler [mailto:cziege...@apache.org]
> > Sent: Friday, August 09, 2013 9:52 AM
> > To: dev@sling.apache.org
> > Subject: [VOTE] Release Discovery Modules, Settings and Eventing
> >
> > Hi,
> >
> > this vote is primarily about doing the first release of our discovery
> > implementation modules (we already released the api some time ago). The
> > implementation proofed to be stable/usable. In addition, we need to
> release
> > a dependency, Sling Settigns 1.3.0 and I've also included the Sling
> Events
> > as this makes heavy use of the discovery stuff.
> >
> > So please vote for the release of
> >
> > Sling Settings 1.3.0
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12323581
> >
> > Sing Discovery Support 1.0.0
> > Sling Discovery Standalone 1.0.0
> > Sling Discovery Impl 1.0.0
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12324346
> >
> > Sling Eventing 3.2.0
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12321291
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-079/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh079 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> >  [ ] +1 Approve the release
> >  [ ]  0 Don't care
> >  [ ] -1 Don't release, because ...
> >
> > This vote will be open for 72 hours.
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > cziege...@apache.org
>

Jenkins build is back to stable : sling-trunk-1.6 #1801

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Sample Integration Tests #1801

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #1801

[Apache Jenkins Server]

See 

[jira] [Assigned] (SLING-2667) [Tooling] create text-only console that exposes the operations performed and their results

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reassigned SLING-2667:
--

Assignee: Robert Munteanu

> [Tooling] create text-only console that exposes the operations performed and 
> their results
> --
>
> Key: SLING-2667
> URL: https://issues.apache.org/jira/browse/SLING-2667
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> As for SLING-2634 the operations performed and their results are tracked in 
> .metadata/trace.log .
> It would be nice having a text-only console showing those information as well.
> See also [0]
> [0] 
> https://issues.apache.org/jira/browse/SLING-2634?focusedCommentId=13484860&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13484860

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2989) [Tooling] integrate with vlt once available

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2989:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] integrate with vlt once available
> ---
>
> Key: SLING-2989
> URL: https://issues.apache.org/jira/browse/SLING-2989
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Integrate the eclipse tooling with vault, once available open source

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-healthcheck-1.6 #80

[Apache Jenkins Server]

See 

Changes:

[bdelacretaz] SLING-2987 - move SLING-2987 branch back under 
contrib/extensions, old code is tagged at 
https://svn.apache.org/repos/asf/sling/tags/healthcheck-before-SLING-2987

[bdelacretaz] SLING-2987 - DefaultLoginsHealthCheckTest checks multiple logins

[bdelacretaz] SLING-2987 - optionally use a different (shorter) name for the 
MBeans that we create

[bdelacretaz] SLING-2987 - fix integration tests

[bdelacretaz] SLING-2987 - reorganize modules

[bdelacretaz] SLING-2987 - reorganize modules

[bdelacretaz] SLING-2987 - reorganize modules

[bdelacretaz] SLING-2987 - remove unneeded modules

[bdelacretaz] SLING-2987 - SlingRequestStatusHealthCheck added

[bdelacretaz] SLING-2987 - fix integration tests and remove obsolete modules 
from pom

[bdelacretaz] SLING-2987 - DefaultLoginsHealthCheck added

[bdelacretaz] SLING-2987 - bindings tests

[bdelacretaz] SLING-2987 - add metatype + reorganize packages

[bdelacretaz] SLING-2987 - improved webconsole plugin

[bdelacretaz] SLING-2987 - improved webconsole plugin

[bdelacretaz] SLING-2987 - improved webconsole plugin

[bdelacretaz] SLING-2987 - remove old demo content

[bdelacretaz] SLING-2987 - test whitespace

[bdelacretaz] SLING-2987 - webconsole plugin, work in progress

[bdelacretaz] SLING-2987 - more tests

[bdelacretaz] SLING-2987 - HealthCheckSelector added

[bdelacretaz] SLING-2987 - HealthCheckMBean and OsgiScriptBinding added

[bdelacretaz] SLING-2987 - ScriptableHealthCheck added

[bdelacretaz] SLING-2987 - JmxAttributeHealthCheck added

[bdelacretaz] SLING-2987 - removing tons of code ;-)

[bdelacretaz] SLING-2987 - bump up version numbers

[bdelacretaz] SLING-2987 - simplified healthcheck services, starting redesign 
on a branch

--
[...truncated 25 lines...]
AU
samples/src/main/resources/SLING-CONTENT/apps/hc/demo/install/org.apache.sling.hc.ScriptableHealthCheck-1.json
AU
samples/src/main/resources/SLING-CONTENT/apps/hc/demo/install/org.apache.sling.hc.ScriptableHealthCheck-2.json
A 
samples/src/main/resources/SLING-CONTENT/apps/hc/demo/install/org.apache.sling.hc.SlingRequestStatusHealthCheck-1.json
A 
samples/src/main/resources/SLING-CONTENT/apps/hc/demo/install/org.apache.sling.hc.DefaultLoginsHealthCheck-1.json
A core
A core/pom.xml
A core/src
A core/src/main
A core/src/main/java
A core/src/main/java/org
A core/src/main/java/org/apache
A core/src/main/java/org/apache/sling
A core/src/main/java/org/apache/sling/hc
A core/src/main/java/org/apache/sling/hc/util
AU
core/src/main/java/org/apache/sling/hc/util/SimpleConstraintChecker.java
A core/src/main/java/org/apache/sling/hc/impl
A 
core/src/main/java/org/apache/sling/hc/impl/HealthCheckWebconsolePlugin.java
A core/src/main/java/org/apache/sling/hc/impl/HealthCheckMBean.java
AU
core/src/main/java/org/apache/sling/hc/impl/HealthCheckMBeanCreator.java
A 
core/src/main/java/org/apache/sling/hc/impl/HealthCheckSelectorImpl.java
A core/src/main/java/org/apache/sling/hc/impl/healthchecks
A 
core/src/main/java/org/apache/sling/hc/impl/healthchecks/DefaultLoginsHealthCheck.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/InternalRequest.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/JmxAttributeHealthCheck.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/InternalResponse.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/ScriptableHealthCheck.java
A 
core/src/main/java/org/apache/sling/hc/impl/healthchecks/SlingRequestStatusHealthCheck.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/JmxScriptBinding.java
AU
core/src/main/java/org/apache/sling/hc/impl/healthchecks/OsgiScriptBinding.java
A core/src/main/java/org/apache/sling/hc/impl/WebConsoleHelper.java
A core/src/main/java/org/apache/sling/hc/api
AUcore/src/main/java/org/apache/sling/hc/api/Constants.java
AUcore/src/main/java/org/apache/sling/hc/api/Result.java
AUcore/src/main/java/org/apache/sling/hc/api/ResultLog.java
AUcore/src/main/java/org/apache/sling/hc/api/HealthCheck.java
A core/src/main/java/org/apache/sling/hc/api/HealthCheckSelector.java
A core/src/main/resources
A core/src/main/resources/OSGI-INF
A core/src/main/resources/OSGI-INF/metatype
A core/src/main/resources/OSGI-INF/metatype/metatype.properties
A core/src/main/resources/res
A core/src/main/resources/res/ui
A core/src/main/resources/res/ui/healthcheck.css
A core/src/test
A core/src/test/java
A core/src/test/java/org
A core/src/test/java/org/apache
A core/src/test/java/org/apache/sling
A core/sr

[jira] [Updated] (SLING-2628) [Tooling] Eclipse plugins/features for Sling-based development

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2628:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Eclipse plugins/features for Sling-based development
> --
>
> Key: SLING-2628
> URL: https://issues.apache.org/jira/browse/SLING-2628
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> see discussion in [0]
> [0] http://sling.markmail.org/message/wvvimvqoljhmywox

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2666) [Tooling] Checking out resources fails if the DefaultGetServlet does not serve the content

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2666:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Checking out resources fails if the DefaultGetServlet does not 
> serve the content
> --
>
> Key: SLING-2666
> URL: https://issues.apache.org/jira/browse/SLING-2666
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> see discussion at [0]
> [0] http://sling.markmail.org/message/rsmysnx6ombk4u4s

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2629) [Tooling] Add tycho build to Slingclipse

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2629:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Add tycho build to Slingclipse
> 
>
> Key: SLING-2629
> URL: https://issues.apache.org/jira/browse/SLING-2629
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2629-tycho-build-1.diff, 
> SLING-2629-tycho-build-2.txt, SLING-2629-tycho-build.diff
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2651) [Tooling] manually trigger sync on files/directories

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2651:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] manually trigger sync on files/directories 
> -
>
> Key: SLING-2651
> URL: https://issues.apache.org/jira/browse/SLING-2651
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2646) [Tooling] adding support for .content.xml files on save

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2646:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] adding support for .content.xml files on save
> ---
>
> Key: SLING-2646
> URL: https://issues.apache.org/jira/browse/SLING-2646
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2680) [Tooling] Usability improvements for the Slingclipse import wizard

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2680:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Usability improvements for the Slingclipse import wizard
> --
>
> Key: SLING-2680
> URL: https://issues.apache.org/jira/browse/SLING-2680
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2680.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> The wizard can be improved a little in terms of usability.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2655) [Tooling] Slingclipse import wizard should notify the user in case of errors

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2655:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Slingclipse import wizard should notify the user in case of errors
> 
>
> Key: SLING-2655
> URL: https://issues.apache.org/jira/browse/SLING-2655
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2655.diff, SLING-2655.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> I'll provide a patch for this once all other patches are processed to 
> minimise conflicts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2653) [Tooling] Slingclipse import wizard should use the Eclipse APIs to create resources

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2653:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Slingclipse import wizard should use the Eclipse APIs to create 
> resources
> ---
>
> Key: SLING-2653
> URL: https://issues.apache.org/jira/browse/SLING-2653
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2653.diff, SLING-2653.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Since the ImportWizard use the java.io. APIs to create files and directories 
> these are not known to Eclipse and require a manual refresh. 
> This also means that the disabling of automatic sync during import does not 
> have any efect, since when I manually refresh the folder to see the results 
> the recently created resources will be re-imported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2985) [Tooling] show content of .content.xml in project explorer

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2985:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] show content of .content.xml in project explorer
> --
>
> Key: SLING-2985
> URL: https://issues.apache.org/jira/browse/SLING-2985
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Irrespective of the chosen serialization the content of .content.xml should 
> be shown in the tree structure of the project explorer. This can be achieved 
> using a Navigator Content Extension (NCE) (which is part of the Common 
> Navigator Framework (CNF) of eclipse).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2647) Track Import Progress

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2647:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> Track Import Progress
> -
>
> Key: SLING-2647
> URL: https://issues.apache.org/jira/browse/SLING-2647
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Dan Klco
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2647-Track-Progress.diff
>
>
> We should track the progress of imports by using Jobs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2636) [Tooling] Add ability to Import from Sling Repository

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2636:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Add ability to Import from Sling Repository
> -
>
> Key: SLING-2636
> URL: https://issues.apache.org/jira/browse/SLING-2636
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Dan Klco
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2636-Import-IN-PROGRESS.diff, 
> SLING-2636-Import-Wizard.diff
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2667) [Tooling] create text-only console that exposes the operations performed and their results

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2667:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] create text-only console that exposes the operations performed and 
> their results
> --
>
> Key: SLING-2667
> URL: https://issues.apache.org/jira/browse/SLING-2667
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> As for SLING-2634 the operations performed and their results are tracked in 
> .metadata/trace.log .
> It would be nice having a text-only console showing those information as well.
> See also [0]
> [0] 
> https://issues.apache.org/jira/browse/SLING-2634?focusedCommentId=13484860&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13484860

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2973) [Tooling] Align Eclipse tooling to proposed structure

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2973:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Align Eclipse tooling to proposed structure
> -
>
> Key: SLING-2973
> URL: https://issues.apache.org/jira/browse/SLING-2973
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The current IDE tooling needs to be aligned to the structure defined at [1] . 
> We should be careful to preserve existing behaviour, but regressions in the 
> short run are acceptable since we will move to the WST framework, which is a 
> different beast altogether.
> [1]: https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2660) [Tooling] Add a Sling project nature to control projects being synchronized

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2660:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Add a Sling project nature to control projects being synchronized
> ---
>
> Key: SLING-2660
> URL: https://issues.apache.org/jira/browse/SLING-2660
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2660.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> From a usability point of view it's better to have a Sling project nature 
> which allows users to opt-in to their resources being synchronized and also 
> could allow defining repositories per project, as opposed to global projects.
> I'll try and look into this in the coming days.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2654) [Tooling] Target platform definition should include sources if possible

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2654:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Target platform definition should include sources if possible
> ---
>
> Key: SLING-2654
> URL: https://issues.apache.org/jira/browse/SLING-2654
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2654.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> This got lost with some recent changes, probably due to an older target 
> platform editor. At least in Eclipse Juno this allows sources to be attached 
> to all plugin dependencies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2634) [Tooling] Slingclipse should expose the operations it performs and their results

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2634:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Slingclipse should expose the operations it performs and their 
> results
> 
>
> Key: SLING-2634
> URL: https://issues.apache.org/jira/browse/SLING-2634
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2634-1.diff, SLING-2634-2.diff, 
> SLING-2634-proof-of-design.diff
>
>
> I think that it's important for the user to know what Slingclipse is doing, 
> especially since it uses some heuristics to detect Sling-based projects.
> My first thoughts would be: 
> * from a UI point of view start with something simple like a text-only 
> console . The subclipse console is a good starting point, we can simply log 
> things like
> ADD $SLING_URL $PROJECT/$RESOURCE 200 OK
> REMOVE $SLING_URL $PROJECT/$RESOURCE 500 Internal Server Error
> * from an implementation point of view we could use something like a command 
> pattern ( SaveResource command, DeleteResourceCommand ) . This would have the 
> benefit of allowing this logging easily + encapsulating the operations for 
> batching, handling of offline operations, redo etc.
> Thoughts? I'm willing to look into this, at least for a first iteration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2635) [Tooling] Logging framework for Slingclipse

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2635:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Logging framework for Slingclipse
> ---
>
> Key: SLING-2635
> URL: https://issues.apache.org/jira/browse/SLING-2635
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2635.diff
>
>
> We need a Logging framework for Slingclipse.
> I see two options at the moment:
> - using a log framework as SLF4J logger or other similar
> - using the embedded Eclipse logging framework 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2637) [Tooling] Ignore Build Output & Eclipse Metadata

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2637:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] Ignore Build Output & Eclipse Metadata
> 
>
> Key: SLING-2637
> URL: https://issues.apache.org/jira/browse/SLING-2637
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Dan Klco
>Assignee: Antonio Sanso
>Priority: Trivial
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2637-Ignore-Pattern.diff
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> I prefer to ignore the following patters:
> .project
> .classpath
> target
> .settings
> They can all be rebuilt from the Maven POM

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2984) [Tooling] improve import-content wizard

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2984:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] improve import-content wizard
> ---
>
> Key: SLING-2984
> URL: https://issues.apache.org/jira/browse/SLING-2984
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The import content wizard currently assumes that the project is added to a 
> server and that the project has a sync folder configured. The wizard should 
> allow to set those things automatically.
> More improvements likely to come and will be added to this ticket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2631) [Tooling] SlingclipseListener incorrectly calculates parent paths

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2631:
---

  Component/s: (was: Extensions)
   IDE
Fix Version/s: Sling Eclipse IDE 1.0.0

> [Tooling] SlingclipseListener incorrectly calculates parent paths
> -
>
> Key: SLING-2631
> URL: https://issues.apache.org/jira/browse/SLING-2631
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2631.diff, SLING-2631.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> I get lots of such exceptions when I start Eclipse. I disabled sync after 
> every save for now.
> !ENTRY org.eclipse.core.resources 4 2 2012-10-25 23:30:31.945
> !MESSAGE Problems occurred when invoking code from plug-in: 
> "org.eclipse.core.resources".
> !STACK 0
> java.lang.IllegalArgumentException: Invalid uri 
> 'http://localhost:8080metrixx-commons-core/target/classes/META-INF': 
> invalid port number
>   at 
> org.apache.commons.httpclient.HttpMethodBase.(HttpMethodBase.java:222)
>   at 
> org.apache.commons.httpclient.methods.ExpectContinueMethod.(ExpectContinueMethod.java:93)
>   at 
> org.apache.commons.httpclient.methods.EntityEnclosingMethod.(EntityEnclosingMethod.java:119)
>   at 
> org.apache.commons.httpclient.methods.PostMethod.(PostMethod.java:106)
>   at 
> org.apache.sling.slingclipse.http.impl.RepositoryImpl.addNode(RepositoryImpl.java:37)
>   at 
> org.apache.sling.slingclipse.SlingclipseListener$1.visit(SlingclipseListener.java:91)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
>   at 
> org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
>   at 
> org.apache.sling.slingclipse.SlingclipseListener.resourceChanged(SlingclipseListener.java:42)
>   at 
> org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at 
> org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
>   at 
> org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
>   at 
> org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
>   at 
> org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
>   at 
> org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1712)
>   at 
> org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:167)
>   at 
> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] Components and version for IDE tooling

[Robert Munteanu]

Great, thanks

On Fri, Aug 9, 2013 at 3:08 PM, Carsten Ziegeler  wrote:
> Ok, done  - we can rename later on if required.
>
> Carsten
>
>
> 2013/8/9 Robert Munteanu 
>
>> On Fri, 2013-08-09 at 14:00 +0200, Carsten Ziegeler wrote:
>> > I've created the component, I'm not sure about the version, wouldn't this
>> > be more specific like "Sling Eclipse IDE 1.0.0" (or whatever we pick) ?
>>
>> Sling Eclipse IDE 1.0.0 sounds fine to me, we're focusing on that
>> initially anyway.
>>
>> Robert
>>
>>
>>
>>
>
>
> --
> Carsten Ziegeler
> cziege...@apache.org

Re: [jira] Components and version for IDE tooling

[Carsten Ziegeler]

Ok, done  - we can rename later on if required.

Carsten


2013/8/9 Robert Munteanu 

> On Fri, 2013-08-09 at 14:00 +0200, Carsten Ziegeler wrote:
> > I've created the component, I'm not sure about the version, wouldn't this
> > be more specific like "Sling Eclipse IDE 1.0.0" (or whatever we pick) ?
>
> Sling Eclipse IDE 1.0.0 sounds fine to me, we're focusing on that
> initially anyway.
>
> Robert
>
>
>
>


-- 
Carsten Ziegeler
cziege...@apache.org

Re: [jira] Components and version for IDE tooling

[Robert Munteanu]

On Fri, 2013-08-09 at 14:00 +0200, Carsten Ziegeler wrote:
> I've created the component, I'm not sure about the version, wouldn't this
> be more specific like "Sling Eclipse IDE 1.0.0" (or whatever we pick) ?

Sling Eclipse IDE 1.0.0 sounds fine to me, we're focusing on that
initially anyway.

Robert

Re: [jira] Components and version for IDE tooling

[Carsten Ziegeler]

I've created the component, I'm not sure about the version, wouldn't this
be more specific like "Sling Eclipse IDE 1.0.0" (or whatever we pick) ?


2013/8/9 Robert Munteanu 

> Hi,
>
> Can someone please create an 'IDE' component and 'IDE 1.0.0' version in
> Jira?
>
> Thanks,
>
> Robert
>
>


-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Commented] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734697#comment-13734697
 ] 

Robert Munteanu commented on SLING-2923:


Updated feature.xml to refer to the recently released 
org.apache.sling.jcr.jackrabbit.server 2.1.2 bundle in 
http://svn.apache.org/viewvc?view=revision&revision=1512268 .

> release org.apache.sling.jcr.jackrabbit.server 2.1.1
> 
>
> Key: SLING-2923
> URL: https://issues.apache.org/jira/browse/SLING-2923
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
> Environment: Apache Karaf 3.0.0.RC1
>Reporter: Oliver Lietz
>Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.1.2
>
> Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log
>
>
> There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
> (Caused by: java.lang.ClassNotFoundException: 
> org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
> Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
> 2.1.1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2987) Simplified health check services

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734695#comment-13734695
 ] 

Carsten Ziegeler commented on SLING-2987:
-

The log could maybe be part of a scripting api for hcs

> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2987) Simplified health check services

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734690#comment-13734690
 ] 

Carsten Ziegeler commented on SLING-2987:
-

I think we should create a third bundle, which simply registers health check 
services as JMX beans, to have everything nicely separated

> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Components and version for IDE tooling

[Robert Munteanu]

Hi,

Can someone please create an 'IDE' component and 'IDE 1.0.0' version in
Jira?

Thanks,

Robert

[jira] [Commented] (SLING-2987) Simplified health check services

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734688#comment-13734688
 ] 

Carsten Ziegeler commented on SLING-2987:
-

For the impl, I think we should separate the api from all the additional stuff 
currently in core. The only thing implementation wise would be the 
HealthCheckSelector service if we keep it

> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2987) Simplified health check services

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734686#comment-13734686
 ] 

Carsten Ziegeler commented on SLING-2987:
-

Thanks for the work, Bertrand.

For the API, I think there are some things which should be changed as well (we 
discussed these briefly in the original thread):
- we don't need a ResultLog, the result can have a string (array/list) of 
messages
- the result should not be based on the level of a log message, but have a 
level to be set (so we need an enum for that)
- the result should not hold the service, it should be a plain data object
- I assume the info props of the HealthCheck are also OSGi service props?
- not sure if we need the HealthCheckSelector, it rather looks like an utility 
method

> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-3005) Event integration tests: update bundle versions for tika

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734683#comment-13734683
 ] 

Robert Munteanu commented on SLING-3005:


Fixed in http://svn.apache.org/viewvc?view=revision&revision=1512260 .

Also removed the jackrabbit.server update from this bug since that was already 
done in http://svn.apache.org/viewvc?view=revision&revision=1512142

> Event integration tests: update bundle versions for tika
> 
>
> Key: SLING-3005
> URL: https://issues.apache.org/jira/browse/SLING-3005
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
>
> We already use tika at version 1.2.0 in the launchpad it's a good idea to 
> sync the version for the event ITs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-3005) Event integration tests: update bundle versions for tika

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-3005.


Resolution: Fixed

> Event integration tests: update bundle versions for tika
> 
>
> Key: SLING-3005
> URL: https://issues.apache.org/jira/browse/SLING-3005
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
>
> We already use tika at version 1.2.0 in the launchpad it's a good idea to 
> sync the version for the event ITs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-3005) Event integration tests: update bundle versions for tika

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-3005:
---

Description: We already use tika at version 1.2.0 in the launchpad it's a 
good idea to sync the version for the event ITs.  (was: Since  
org.apache.sling.jcr.jackrabbit.server 2.1.2 is released and we already use 
tika at version 1.2.0 in the launchpad it's a good idea to sync these versions 
for the event ITs.)
Summary: Event integration tests: update bundle versions for tika  
(was: Event integration tests: update bundle versions for jackrabbit.server, 
tika)

> Event integration tests: update bundle versions for tika
> 
>
> Key: SLING-3005
> URL: https://issues.apache.org/jira/browse/SLING-3005
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
>
> We already use tika at version 1.2.0 in the launchpad it's a good idea to 
> sync the version for the event ITs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-3004) Event ITs should use timeouts

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734682#comment-13734682
 ] 

Robert Munteanu commented on SLING-3004:


Timeouts added in http://svn.apache.org/viewvc?view=revision&revision=1512261

> Event ITs should use timeouts
> -
>
> Key: SLING-3004
> URL: https://issues.apache.org/jira/browse/SLING-3004
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Extensions Event 3.2.2
>
>
> The Event Pax-Exam tests sometimes hang for me locally with timeouts. To 
> alleviate the problem, all tests should use timeouts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-3004) Event ITs should use timeouts

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-3004.


Resolution: Fixed

> Event ITs should use timeouts
> -
>
> Key: SLING-3004
> URL: https://issues.apache.org/jira/browse/SLING-3004
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Extensions Event 3.2.2
>
>
> The Event Pax-Exam tests sometimes hang for me locally with timeouts. To 
> alleviate the problem, all tests should use timeouts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-3004) Event ITs should use timeouts

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-3004:
---

Fix Version/s: Extensions Event 3.2.2

> Event ITs should use timeouts
> -
>
> Key: SLING-3004
> URL: https://issues.apache.org/jira/browse/SLING-3004
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Extensions Event 3.2.2
>
>
> The Event Pax-Exam tests sometimes hang for me locally with timeouts. To 
> alleviate the problem, all tests should use timeouts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2987) Simplified health check services

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734679#comment-13734679
 ] 

Bertrand Delacretaz commented on SLING-2987:


The redesign is done, moved the code back under contrib/extensions/healthcheck 
in trunk, will document it at 
http://sling.apache.org/documentation/bundles/sling-health-check-tool.html

The pre-redesign code is at 
https://svn.apache.org/repos/asf/sling/tags/healthcheck-before-SLING-2987, I 
think I have brough all the functionality into the new code, except executing 
health checks via a servlet, which is probably not needed and health checks 
that runJUnit tests, which should move to our junit bundles instead.

> Simplified health check services
> 
>
> Key: SLING-2987
> URL: https://issues.apache.org/jira/browse/SLING-2987
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Attachments: webconsole-is-back.jpg
>
>
> After some prototyping, the health check tools are ready for a rewrite that 
> will make them simpler and more OSGi friendly. 
> The functionality will be similar but with much less code, more focused on 
> the actual use cases that have emerged during prototyping. 
> The new API is being discussed on list, 
> http://markmail.org/thread/i6ib7tgax4cn2sss

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira