Re: [VOTE] Release Apache Sling Authentication XING Login 0.0.2

[Carsten Ziegeler]

+1


2014-07-09 1:16 GMT+02:00 Robert Munteanu :

> +1
>
> Robert
>
> On Tue, Jul 8, 2014 at 6:07 PM, Oliver Lietz 
> wrote:
> > Hi,
> >
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12327253/
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1078/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1078 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> >   [ ] +1 Approve the release
> >   [ ]  0 Don't care
> >   [ ] -1 Don't release, because ...
> >
> > This majority vote is open for at least 72 hours.
> >
> > Regards,
> > O.
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-3736) Expose OSGi Installer state via JMX

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-3736:
-

Lgtm

> Expose OSGi Installer state via JMX
> ---
>
> Key: SLING-3736
> URL: https://issues.apache.org/jira/browse/SLING-3736
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Reporter: Chetan Mehrotra
>Priority: Minor
> Attachments: SLING-3736.patch
>
>
>  Would be helpful to have OSGi installer expose an MBean which can provide 
> information like
> * Current pending installations
> * Last OSGi installer state - Active, Suspended, Processed
> * Time of last activity
> This MBean can then be used by administrators to determine when its safe to 
> shutdown Sling or start test say after installation of a patch.
> [1] http://markmail.org/thread/w235qqafagqvzlmm



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3742) Python and Ruby language bundle throw exception with sling scripting console

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra resolved SLING-3742.


Resolution: Fixed

With Sling Script Console the request would be null so yes adding a null check 
for it makes sense

Thanks for the patch. Applied it in http://svn.apache.org/r1609022

> Python and Ruby language bundle throw exception with sling scripting console
> 
>
> Key: SLING-3742
> URL: https://issues.apache.org/jira/browse/SLING-3742
> Project: Sling
>  Issue Type: Bug
>  Components: Console, Extensions
>Reporter: Nitin Nizhawan
>Assignee: Chetan Mehrotra
> Attachments: SLING-3742.patch
>
>
> When running Ruby and Python language bundles from contrib/scripting with 
> sling scripting console I am getting following exception
> java.lang.NullPointerException
> at 
> org.apache.sling.scripting.python.PythonScriptEngine.eval(PythonScriptEngine.java:69)
> at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:361)
> at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
> at 
> org.apache.sling.scripting.console.internal.ScriptConsolePlugin.doPost(ScriptConsolePlugin.java:112)
> at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:526)
> at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:450)
> at 
> org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
> at 
> org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
> at 
> org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3747) Provide a way to signal Jcr Installer to pause and resume scanning

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra updated SLING-3747:
---

Attachment: SLING-3747-2.patch

Updated [patch|^SLING-3747-2.patch] which does not rely on observation. Instead 
a check for property value is made if any of the watched folder needs scan as 
per [~fmeschbe] suggestion

bq. What about - as Felix suggest - simply check the value of the property 
before runOneCycle() is invoked instead of relying on observation to be 
deliverd in the correct order?

Well that becomes polling and making JCR call every 500 msec. Might be better 
to check for property value only if any of the WatchedFolder.needsScan returns 
true. Then we would not be making too frequent JCR calls.

Updated patch to use that approach

bq.  but maybe a session.refresh() needs to be added as well.
When session with which ObservationListener is registerd is used to read a 
value post event delivery then as per spec its ensured that session is upto 
date. 

> Provide a way to signal Jcr Installer to pause and resume scanning
> --
>
> Key: SLING-3747
> URL: https://issues.apache.org/jira/browse/SLING-3747
> Project: Sling
>  Issue Type: New Feature
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3747-1.patch, SLING-3747-2.patch, SLING-3747.patch
>
>
> Currently Sling Installer JCR Provider would listen for observation event and 
> would perform a rescan every 500 msec upon receiving any observation event. 
> This at times cause issue when large number of bundles get updated in 
> repository say via installation of bug fixing content package. Further if 
> same content package also updates the repository bundle then it causes issues 
> as repository bundle might get updated midway while content package is still 
> being deployed
> Based on [~fmeschbe] suggestion this can be done via introducing a signalling 
> mechanism between component which installs package and JCR Installer. It 
> would work something like this
> # JCR Installer would listen to changes done to property 
> {{/system/sling/installer/jcr/pauseInstallation}}
> # Package installer would set the above flag to true before installing the 
> package and reset it back to false post installation
> # If JCR Installer detects that flag is set to true it would not scan the 
> watch folders untill it get reset back to false
> This should also address the issue in cluster deployment



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Release Apache Sling Authentication XING OAuth 0.0.2

[Carsten Ziegeler]

+1


2014-07-09 1:13 GMT+02:00 Robert Munteanu :

> +1
>
> Robert
>
> On Tue, Jul 8, 2014 at 6:08 PM, Oliver Lietz 
> wrote:
> > Hi,
> >
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12327252/
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1079/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1079 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> >   [ ] +1 Approve the release
> >   [ ]  0 Don't care
> >   [ ] -1 Don't release, because ...
> >
> > This majority vote is open for at least 72 hours.
> >
> > Regards,
> > O.
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Authentication XING API 0.0.2

[Carsten Ziegeler]

+1


2014-07-09 1:06 GMT+02:00 Robert Munteanu :

> +1
>
> Robert
>
> On Tue, Jul 8, 2014 at 6:07 PM, Oliver Lietz 
> wrote:
> > Hi,
> >
> > This is a shared API bundle for Sling Authentication XING Login and Sling
> > Authentication XING OAuth:
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12327251/
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1077/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1077 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> >   [ ] +1 Approve the release
> >   [ ]  0 Don't care
> >   [ ] -1 Don't release, because ...
> >
> > This majority vote is open for at least 72 hours.
> >
> > Regards,
> > O.
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-3747) Provide a way to signal Jcr Installer to pause and resume scanning

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-3747:
-

What about - as Felix suggest - simply check the value of the property before 
runOneCycle() is invoked instead of relying on observation to be deliverd in 
the correct order?
I haven't looked at the code in detail, but maybe a session.refresh() needs to 
be added as well.

> Provide a way to signal Jcr Installer to pause and resume scanning
> --
>
> Key: SLING-3747
> URL: https://issues.apache.org/jira/browse/SLING-3747
> Project: Sling
>  Issue Type: New Feature
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3747-1.patch, SLING-3747.patch
>
>
> Currently Sling Installer JCR Provider would listen for observation event and 
> would perform a rescan every 500 msec upon receiving any observation event. 
> This at times cause issue when large number of bundles get updated in 
> repository say via installation of bug fixing content package. Further if 
> same content package also updates the repository bundle then it causes issues 
> as repository bundle might get updated midway while content package is still 
> being deployed
> Based on [~fmeschbe] suggestion this can be done via introducing a signalling 
> mechanism between component which installs package and JCR Installer. It 
> would work something like this
> # JCR Installer would listen to changes done to property 
> {{/system/sling/installer/jcr/pauseInstallation}}
> # Package installer would set the above flag to true before installing the 
> package and reset it back to false post installation
> # If JCR Installer detects that flag is set to true it would not scan the 
> watch folders untill it get reset back to false
> This should also address the issue in cluster deployment



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Release Apache Sling Scripting Thymeleaf 0.0.2

[Carsten Ziegeler]

+1


2014-07-09 1:01 GMT+02:00 Robert Munteanu :

> On Tue, Jul 8, 2014 at 12:39 PM, Robert Munteanu  wrote:
> >
> > I'll try this again when I am able to retrieve the key.
>
> +1
>
> Retrieved the key, signatures check out fine at my end.
>
> Robert
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-3749) [OSGi Installer] Intelligently manage start level during artifact handling

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-3749:
-

Looks good to me, we definitely should make this configurable.
I might be wrong, but I think you need to check whether a bundle is using the 
default start level (=0) and ignore those.
I'm not 100% sure but maybe it makes sense to go to the start level right below 
the lowest update level, so if e.g. a bundle at level 15 is updated, go to 
level 14, update and then increase again.
In addition, an update might change the start level (see update task), 
therefore the new start level should be used.

> [OSGi Installer] Intelligently manage start level during artifact handling
> --
>
> Key: SLING-3749
> URL: https://issues.apache.org/jira/browse/SLING-3749
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3749.patch
>
>
> OSGi Installer should be made more intelligent in deciding how to handle 
> bundle updates, if multiple bundles need to be updated e.g. by lowering the 
> system start level when updating important bundles or when updating a large 
> number of bundles to reduce oscillation of the system and thus reduce update 
> time and increase stability.
> Some thoughts around this as per [~fmeschbe]:
> * Bundle installations are not problematic and don't need to be treated 
> specially
> * Bundle updates and uninstallations may cause the system to oscillated 
> because services may come and go during updates and package refreshes
> * Some bundles are more central than other bundles. For example the  bundle 
> providing the JCR Repository service is "used" by almost all of the system. 
> And bundle may be important because a certain threshold if API importing 
> bundles is reached (e.g. the Sling API bundle) or because one of the 
> registered services is used by a certain threshold of consumers.
> * When at least one important bundle is updated or uninstalled in a single 
> batch, the OSGi installer should reduce the system start level before 
> handling the batch and raise the start level after the batch again.
> * The start level to which the system is reduced is the lower of the start 
> level of the OSGi installer and its helper bundles (probably the Task 
> provides) and the start levels of the important bundle(s) handled in the 
> batch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Include ide tooling source bundle on dist.apache.org

[Carsten Ziegeler]

+1


2014-07-08 16:28 GMT+02:00 Robert Munteanu :

> Hi,
>
> As Bertrand has noticed [1], the Sling IDE Tooling 1.0.0 release does
> not include a source bundle on dist.apache.org .
>
> Following that discussion, I propose that we upload a source bundle at
> https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ . The
> source bundle is a plain SVN export from the tag used to generate the
> 1.0.0 release.
>
> The candidate source bundle is uploaded at [2] . It can be used to
> rebuild the IDE tooling with
>
>mvn clean package
>
> Please vote to approve this inclusion.
>
> Thanks,
>
> Robert
>
> [1]: http://markmail.org/thread/hgxbejjrmn4wrpsv
> [2]: https://people.apache.org/~rombert/sling/sling-ide-tooling-1.0.0/
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[VOTE] Release Apache Sling Scripting JSP 2.1.4 and Apache Sling Scripting Java 2.0.10

[Carsten Ziegeler]

Hi,

We solved two issues for each scripting bundle, especially with SLING-3724
these
bundles now provide a better experience with Java 8 as they run without
configuration
changes on Java 8 as well as previous versions.

Scripting JSP
https://issues.apache.org/jira/browse/SLING/fixforversion/12326855
Scripting Java
https://issues.apache.org/jira/browse/SLING/fixforversion/12321863

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1074

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1074 /tmp/sling-staging

Please vote to approve this release:

   [ ] +1 Approve the release
   [ ]  0 Don't care
   [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Scripting JSP 2.1.4 and Apache Sling Scripting Java 2.0.10

[Carsten Ziegeler]

+1


2014-07-09 7:36 GMT+02:00 Carsten Ziegeler :

> Hi,
>
> We solved two issues for each scripting bundle, especially with SLING-3724
> these
> bundles now provide a better experience with Java 8 as they run without
> configuration
> changes on Java 8 as well as previous versions.
>
> Scripting JSP
> https://issues.apache.org/jira/browse/SLING/fixforversion/12326855
> Scripting Java
> https://issues.apache.org/jira/browse/SLING/fixforversion/12321863
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1074
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1074 /tmp/sling-staging
>
> Please vote to approve this release:
>
>[ ] +1 Approve the release
>[ ]  0 Don't care
>[ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[VOTE CANCELLED] Release Apache Sling Scripting JSP 2.1.2 and Apache Sling Scripting Java 2.0.8

[Carsten Ziegeler]

Hi, as mentioned earlier in this thread, I cancel this vote and start a new
one for the updated artifacts/releases.

Regards
Carsten

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Changes:

[rombert] Update svn:ignore for the xing bundles

--
[...truncated 26837 lines...]
[INFO] Sling Servlet Archetype ... SUCCESS [12.378s]
[INFO] Sling Bundle Archetype  SUCCESS [15.034s]
[INFO] Sling JCRInstall Bundle Archetype . SUCCESS [12.775s]
[INFO] Sling Taglib Archetype  SUCCESS [6.196s]
[INFO] Apache Sling API .. SUCCESS [20.946s]
[INFO] Apache Sling Resource Resolver  SUCCESS [20.543s]
[INFO] Apache Sling System Bundle Extension: Java Transaction API  SUCCESS 
[7.616s]
[INFO] Apache Sling System Bundle Extension: XML APIs  SUCCESS [6.061s]
[INFO] Apache Sling System Bundle Extension: Activation API  SUCCESS [6.491s]
[INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [8.355s]
[INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [22.496s]
[INFO] Apache Sling Commons Java Compiler  SUCCESS [12.300s]
[INFO] Apache Sling JSON Library . SUCCESS [11.323s]
[INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [47.634s]
[INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [6.644s]
[INFO] Apache Sling MIME type mapping support  SUCCESS [13.344s]
[INFO] Apache Sling Commons OSGi support . SUCCESS [14.605s]
[INFO] Apache Sling Scheduler Support  SUCCESS [9.857s]
[INFO] Apache Sling Testing Utilities  SUCCESS [45.564s]
[INFO] Apache Sling Thread Dumper  SUCCESS [6.303s]
[INFO] Apache Sling Thread Support ... SUCCESS [8.596s]
[INFO] Apache Sling Authentication Service ... SUCCESS [9.525s]
[INFO] Apache Sling OpenID Authentication  SUCCESS [12.726s]
[INFO] Apache Sling Form Based Authentication Handler  SUCCESS [15.062s]
[INFO] Apache Sling Authentication Selector .. SUCCESS [8.442s]
[INFO] Apache Sling Engine Implementation  SUCCESS [36.836s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [9.060s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [12.153s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [10.243s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [14.519s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [19.134s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [13.915s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[11.125s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [7.869s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [11.528s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [2:32.477s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [9.701s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [11.712s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [11.554s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [8.645s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [10.952s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [1:16.771s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [16.988s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [17.040s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [17.577s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [9.388s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [8.373s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [20.083s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [43.389s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [24.090s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [20.658s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [6.990s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [17.531s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [9.201s]
[INFO] Apache Sling Discovery API  SUCCESS [8.739s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [5:29.319s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [11.710s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [9.425s]
[INFO] Apache Sling Event Support  FAILURE [7:06.015s]
[INFO] Apache Sling Feature Flags  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Service User Mapper .

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

[Apache Jenkins Server]

See 


--
[...truncated 10981 lines...]
09.07.2014 01:26:08.115 *INFO* [FelixStartLevel] org.apache.felix.inventory 
Service [37] ServiceEvent REGISTERED
09.07.2014 01:26:08.115 *INFO* [FelixStartLevel] 
org.apache.sling.commons.scheduler Service [Apache Sling Scheduler 
Configuration Printer,36] ServiceEvent REGISTERED
09.07.2014 01:26:08.117 *INFO* [FelixStartLevel] 
org.apache.sling.commons.scheduler Service 
[org.apache.sling.commons.scheduler.impl.QuartzScheduler,34] ServiceEvent 
REGISTERED
09.07.2014 01:26:08.117 *INFO* [FelixStartLevel] 
org.apache.sling.commons.threads Service 
[org.apache.sling.commons.threads.impl.DefaultThreadPool.factory,33] 
ServiceEvent REGISTERED
09.07.2014 01:26:08.118 *INFO* [FelixStartLevel] org.apache.felix.inventory 
Service [41] ServiceEvent REGISTERED
09.07.2014 01:26:08.118 *INFO* [FelixStartLevel] org.apache.felix.inventory 
Service [40] ServiceEvent REGISTERED
09.07.2014 01:26:08.118 *INFO* [FelixStartLevel] 
org.apache.sling.commons.threads Service [Apache Sling Thread Pool 
Configuration Printer,39] ServiceEvent REGISTERED
09.07.2014 01:26:08.119 *INFO* [FelixStartLevel] 
org.apache.sling.commons.threads BundleEvent STARTED
09.07.2014 01:26:08.119 *INFO* [FelixStartLevel] org.apache.sling.launchpad.api 
BundleEvent RESOLVED
09.07.2014 01:26:08.119 *INFO* [FelixStartLevel] org.apache.sling.launchpad.api 
BundleEvent STARTING
09.07.2014 01:26:08.119 *INFO* [FelixStartLevel] org.apache.sling.launchpad.api 
BundleEvent STARTED
09.07.2014 01:26:08.120 *INFO* [FelixStartLevel] org.apache.sling.api 
BundleEvent RESOLVED
09.07.2014 01:26:08.120 *INFO* [FelixStartLevel] org.apache.sling.auth.core 
BundleEvent RESOLVED
09.07.2014 01:26:08.120 *INFO* [FelixStartLevel] org.apache.sling.auth.core 
BundleEvent STARTING
09.07.2014 01:26:08.130 *INFO* [FelixStartLevel] org.apache.sling.auth.core 
Service [org.apache.sling.auth.core.impl.LogoutServlet,42] ServiceEvent 
REGISTERED
09.07.2014 01:26:08.130 *INFO* [FelixStartLevel] org.apache.sling.auth.core 
Service [org.apache.sling.auth.core.impl.LoginServlet,43] ServiceEvent 
REGISTERED
09.07.2014 01:26:08.131 *INFO* [FelixStartLevel] org.apache.sling.auth.core 
BundleEvent STARTED
09.07.2014 01:26:08.131 *INFO* [FelixStartLevel] org.apache.sling.discovery.api 
BundleEvent RESOLVED
09.07.2014 01:26:08.131 *INFO* [FelixStartLevel] org.apache.sling.discovery.api 
BundleEvent STARTING
09.07.2014 01:26:08.131 *INFO* [FelixStartLevel] org.apache.sling.discovery.api 
BundleEvent STARTED
09.07.2014 01:26:08.132 *INFO* [FelixStartLevel] org.apache.sling.settings 
BundleEvent RESOLVED
09.07.2014 01:26:08.132 *INFO* [FelixStartLevel] 
org.apache.sling.discovery.standalone BundleEvent RESOLVED
09.07.2014 01:26:08.132 *INFO* [FelixStartLevel] 
org.apache.sling.discovery.standalone BundleEvent STARTING
09.07.2014 01:26:08.134 *INFO* [FelixStartLevel] 
org.apache.sling.discovery.standalone BundleEvent STARTED
09.07.2014 01:26:08.134 *INFO* [FelixStartLevel] org.apache.sling.api 
BundleEvent STARTING
09.07.2014 01:26:08.134 *INFO* [FelixStartLevel] org.apache.sling.api 
BundleEvent STARTED
09.07.2014 01:26:08.134 *INFO* [FelixStartLevel] org.apache.sling.settings 
BundleEvent STARTING
09.07.2014 01:26:08.137 *INFO* [FelixStartLevel] org.apache.sling.settings 
BundleEvent STARTED
09.07.2014 01:26:08.137 *INFO* [FelixStartLevel] 
org.apache.sling.serviceusermapper BundleEvent RESOLVED
09.07.2014 01:26:08.138 *INFO* [FelixStartLevel] 
org.apache.sling.resourceresolver BundleEvent RESOLVED
09.07.2014 01:26:08.138 *INFO* [FelixStartLevel] 
org.apache.sling.resourceresolver BundleEvent STARTING
09.07.2014 01:26:08.143 *INFO* [FelixStartLevel] 
org.apache.sling.resourceresolver Service 
[org.apache.sling.resourceresolver.impl.ResourceAccessSecurityTracker,44] 
ServiceEvent REGISTERED
09.07.2014 01:26:08.143 *INFO* [FelixStartLevel] 
org.apache.sling.resourceresolver BundleEvent STARTED
09.07.2014 01:26:08.143 *INFO* [FelixStartLevel] org.apache.sling.adapter 
BundleEvent RESOLVED
09.07.2014 01:26:08.144 *INFO* [FelixStartLevel] org.apache.sling.adapter 
BundleEvent STARTING
09.07.2014 01:26:08.146 *INFO* [FelixStartLevel] org.apache.sling.adapter 
Service [org.apache.sling.adapter.internal.AdapterManagerImpl,45] ServiceEvent 
REGISTERED
09.07.2014 01:26:08.164 *INFO* [FelixStartLevel] org.apache.felix.inventory 
Service [48] ServiceEvent REGISTERED
09.07.2014 01:26:08.164 *INFO* [FelixStartLevel] org.apache.felix.inventory 
Service [47] ServiceEvent REGISTERED
09.07.2014 01:26:08.164 *INFO* [FelixStartLevel] org.apache.sling.adapter 
Service [org.apache.sling.adapter.internal.AdapterWebConsolePlugin,46] 
ServiceEvent REGISTERED
09.07.2014 01:26:08.164 *INFO* [FelixStartLevel] org.apache.sling.adapter 
BundleEvent STARTED
09.07.2014 01:26:08.165 *INFO* [FelixStartLevel] org.apache.sling.jcr.resource 
BundleEvent RESOLVED

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2274

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Authentication XING Login #1175

[Apache Jenkins Server]

See 


Changes:

[rombert] Update svn:ignore for the xing bundles

--
[INFO] 
[INFO] 
[INFO] Building Apache Sling Authentication XING Login 0.0.3-SNAPSHOT
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.xing.api/0.0.2/org.apache.sling.auth.xing.api-0.0.2.pom
[WARNING] The POM for org.apache.sling:org.apache.sling.auth.xing.api:jar:0.0.2 
is missing, no dependency information available
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.xing.api/0.0.2/org.apache.sling.auth.xing.api-0.0.2.jar
[JENKINS] Archiving disabled

Build failed in Jenkins: sling-contrib-1.6 #1175

[Apache Jenkins Server]

See 

Changes:

[rombert] Update svn:ignore for the xing bundles

--
[...truncated 54 lines...]
[INFO] Apache Sling Google Web Toolkit Servlet Library
[INFO] Apache Sling Google Web Toolkit Sample
[INFO] Apache Sling Internationalization Support
[INFO] Apache Sling JMX Resource Provider
[INFO] Apache Sling MongoDB Resource Provider
[INFO] Apache Sling OSGi Bundle Repository
[INFO] Apache Sling Request Processing Analyzer
[INFO] Apache Sling Resource Merger
[INFO] Apache Sling Rewriter
[INFO] Apache Sling Tenant
[INFO] Apache Sling Replication
[INFO] Apache Sling Replication Integration Tests
[INFO] Apache Sling Repository Accessor
[INFO] Apache Sling JCR Java Compiler
[INFO] Apache Sling JCR Prefs
[INFO] Apache Sling JCR Resource Security
[INFO] Apache Sling Launchpad Karaf
[INFO] Apache Sling Launchpad Karaf - Features
[INFO] Apache Sling Launchpad Karaf - Integration Tests
[INFO] Apache Sling Launchpad Karaf Builder
[INFO] Apache Sling Launchpad Contrib Testing
[INFO] Apache Sling Script Console
[INFO] Apache Sling Atom Tag Library
[INFO] Apache Sling Scripting Freemarker Support
[INFO] Apache Sling Scripting Java Support
[INFO] Apache Sling Scripting JST Support
[INFO] Apache Sling Scripting Python Support
[INFO] Apache Sling Scripting Ruby Support
[INFO] Apache Sling Scripting Velocity Support
[INFO] Apache Sling Scripting W3C XML Processing Support
[INFO] Scala Script Engine
[INFO] Apache Sling Scala Scripting Configuration
[INFO] Scala for Sling Demo Application - Hello World
[INFO] Scala for Sling Demo Application - Forum
[INFO] Apache Sling Contrib (Builder)
[INFO] 
[INFO] 
[INFO] Building Apache Sling Authentication XING API 0.0.3-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
org.apache.sling.auth.xing.api ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run 
(set-bundle-required-execution-environment) @ org.apache.sling.auth.xing.api ---
[INFO] Executing tasks

main:
Setting Bundle-RequiredExecutionEnvironment=JavaSE-1.6 from sling.java.version=6
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
org.apache.sling.auth.xing.api ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ 
org.apache.sling.auth.xing.api ---
[INFO] Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
org.apache.sling.auth.xing.api ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 6 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
org.apache.sling.auth.xing.api ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
org.apache.sling.auth.xing.api ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.16:test (default-test) @ 
org.apache.sling.auth.xing.api ---
[JENKINS] Recording test results
[INFO] 
[INFO] --- animal-sniffer-maven-plugin:1.9:check (default) @ 
org.apache.sling.auth.xing.api ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java16:1.0
[INFO] 
[INFO] --- maven-bundle-plugin:2.4.0:bundle (default-bundle) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (

Re: [VOTE] Release Apache Sling Authentication XING Login 0.0.2

[Robert Munteanu]

+1

Robert

On Tue, Jul 8, 2014 at 6:07 PM, Oliver Lietz  wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12327253/
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1078/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1078 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards,
> O.

Re: [VOTE] Release Apache Sling Authentication XING OAuth 0.0.2

[Robert Munteanu]

+1

Robert

On Tue, Jul 8, 2014 at 6:08 PM, Oliver Lietz  wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12327252/
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1079/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1079 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards,
> O.

Re: [VOTE] Release Apache Sling Authentication XING API 0.0.2

[Robert Munteanu]

+1

Robert

On Tue, Jul 8, 2014 at 6:07 PM, Oliver Lietz  wrote:
> Hi,
>
> This is a shared API bundle for Sling Authentication XING Login and Sling
> Authentication XING OAuth:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12327251/
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1077/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1077 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards,
> O.

Re: [VOTE] Release Apache Sling Scripting Thymeleaf 0.0.2

[Robert Munteanu]

On Tue, Jul 8, 2014 at 12:39 PM, Robert Munteanu  wrote:
>
> I'll try this again when I am able to retrieve the key.

+1

Retrieved the key, signatures check out fine at my end.

Robert

[jira] [Resolved] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-3741.


Resolution: Fixed

Thanks for confirming, resolving as fixed.

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Release Apache Sling Settings 1.3.2

[Justin Edelson]

+1

On Tue, Jul 8, 2014 at 5:20 PM, Carsten Ziegeler  wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING-3737
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1080
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1080 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards,
> Carsten
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

Re: [VOTE] Release Apache Sling Settings 1.3.2

[Daniel Klco]

+1


On Tue, Jul 8, 2014 at 1:27 PM, Robert Munteanu  wrote:

> +1
>
> Robert
>
> On Tue, Jul 8, 2014 at 6:20 PM, Carsten Ziegeler 
> wrote:
> > Hi,
> >
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/browse/SLING-3737
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1080
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1080 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> >   [ ] +1 Approve the release
> >   [ ]  0 Don't care
> >   [ ] -1 Don't release, because ...
> >
> > This majority vote is open for at least 72 hours.
> >
> > Regards,
> > Carsten
> >
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>

Jenkins build is still unstable: sling-trunk-1.6 #2273

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2273

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Re: [VOTE] Release Apache Sling Settings 1.3.2

[Robert Munteanu]

+1

Robert

On Tue, Jul 8, 2014 at 6:20 PM, Carsten Ziegeler  wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING-3737
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1080
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1080 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards,
> Carsten
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

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

[Apache Jenkins Server]

See 

Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #646

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #2272

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #2272

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-3741:


[~rombert], looks good now, thx!

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

[Apache Jenkins Server]

See 

Changes:

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.login-0.0.2

[olli] SLING-3731 use org.apache.sling.auth.xing.api 0.0.2

[olli] SLING-3731 set version of package org.apache.sling.auth.xing.oauth to 
0.0.2

[olli] SLING-3732 use org.apache.sling.auth.xing.api 0.0.2

[olli] SLING-3732 add package info

[olli] style

[cziegeler] SLING-3737 : Instance Sling Identifier may be randomly reset on 
restart. Apply patch from Timothee Maret

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.api-0.0.2

[olli] SLING-3731 SLING-3732 set version of packages 
org.apache.sling.auth.xing.api and org.apache.sling.auth.xing.api.users to 0.0.2

--
[...truncated 31558 lines...]
[INFO] Sling Launchpad Standalone Archetype .. SUCCESS [18.241s]
[INFO] Sling Launchpad Webapp Archetype .. SUCCESS [12.115s]
[INFO] Sling Initial Content Archetype ... SUCCESS [7.138s]
[INFO] Sling Servlet Archetype ... SUCCESS [8.998s]
[INFO] Sling Bundle Archetype  SUCCESS [8.006s]
[INFO] Sling JCRInstall Bundle Archetype . SUCCESS [8.541s]
[INFO] Sling Taglib Archetype  SUCCESS [5.481s]
[INFO] Apache Sling API .. SUCCESS [12.027s]
[INFO] Apache Sling Resource Resolver  SUCCESS [11.936s]
[INFO] Apache Sling System Bundle Extension: Java Transaction API  SUCCESS 
[4.068s]
[INFO] Apache Sling System Bundle Extension: XML APIs  SUCCESS [3.425s]
[INFO] Apache Sling System Bundle Extension: Activation API  SUCCESS [4.841s]
[INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [5.378s]
[INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [11.972s]
[INFO] Apache Sling Commons Java Compiler  SUCCESS [6.550s]
[INFO] Apache Sling JSON Library . SUCCESS [8.351s]
[INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [34.914s]
[INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [3.850s]
[INFO] Apache Sling MIME type mapping support  SUCCESS [6.951s]
[INFO] Apache Sling Commons OSGi support . SUCCESS [6.694s]
[INFO] Apache Sling Scheduler Support  SUCCESS [5.730s]
[INFO] Apache Sling Testing Utilities  SUCCESS [55.112s]
[INFO] Apache Sling Thread Dumper  SUCCESS [4.096s]
[INFO] Apache Sling Thread Support ... SUCCESS [7.544s]
[INFO] Apache Sling Authentication Service ... SUCCESS [8.954s]
[INFO] Apache Sling OpenID Authentication  SUCCESS [7.255s]
[INFO] Apache Sling Form Based Authentication Handler  SUCCESS [9.854s]
[INFO] Apache Sling Authentication Selector .. SUCCESS [5.687s]
[INFO] Apache Sling Engine Implementation  SUCCESS [23.246s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [9.381s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [8.715s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [5.340s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [8.595s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [8.596s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [6.953s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[6.002s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [5.295s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [9.101s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [52.032s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.629s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [5.739s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.295s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [5.738s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [6.673s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [49.300s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [8.952s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [8.482s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [8.947s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [5.728s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [8.181s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [11.798s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [27.916s]
[INFO] Apache Sling Scripting JSP Support

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #645

[Apache Jenkins Server]

See 


--
[INFO] 
[INFO] 
[INFO] Building Apache Sling Resource Access Security Integration Tests 
0.0.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
org.apache.sling.resourceaccesssecurity.it ---
[INFO] Deleting 

[INFO] Deleting 

 (includes = [sling/**], excludes = [])
[JENKINS] Archiving disabled

[jira] [Created] (SLING-3750) Delay discovery-service readiness until first vote has finished, to avoid leader being overthrown

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3750:
--

 Summary: Delay discovery-service readiness until first vote has 
finished, to avoid leader being overthrown
 Key: SLING-3750
 URL: https://issues.apache.org/jira/browse/SLING-3750
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Discovery Impl 1.0.8
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Critical
 Fix For: Discovery Impl 1.0.10


The current implementation of discovery.impl has a subtle problem at startup. 
Consider the following problem happening with two simultaneous starts:

 * two (sling) instances start at roughly the same time
 * the goal is to write a service which runs on one of the two only, ever
 * to achieve that, on a TopologyEventListener is used to get hold of the 
latest TopologyView and derive whether the local instance is leader or not
 * currently, upon registration of a TopologyEventListener, a TOPOLOGY_INIT 
event is sent out immediately with the current TopologyView available
 * right after startup though - hence before the first voting has passed - 
discovery.impl considers itself to be in so-called "isolated" mode, creates a 
topology which contains only itself, and makes itself leader (since every 
cluster must have a leader)
 * that means, both instances will receive that isolated view in the 
TOPOLOGY_INIT and are marked as leader (which is kind of right as they don't 
know about any other instance yet - but also wrong as it is not yet an 
established view)
 * at the same time, they both start voting, then find out about each other and 
establish a view where one of the two is marked as leader - hence for the other 
of the two a 'coup d'etat' is happening (the leader is overthrown even though 
the instance did not crash). 

This is certainly very problematic and should be avoided.

The suggested way to avoid this is to delay both the time when the 
discovery.impl service is registered with OSGi (by making it a @Component only 
and registering it as a service explicitly after the first voting) - and by 
delaying the sending of TOPOLOGY_INIT until again said first voting is finished.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3749) [OSGi Installer] Intelligently manage start level during artifact handling

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra updated SLING-3749:
---

Attachment: SLING-3749.patch

Initial proposal for the approach to be taken so as to get feedback. Would add 
relevant test once we have agreement on the solution

For now it takes a simple approach and takes the lowest start level of bundle 
to be updated. 

*To be done*
This can be improved by also taking into account the startLevel of Bundles 
which provide the task impls

*To be explored*
Another approach we can take is make use of 
[FrameworkWiring.getDependencyClosure|http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/wiring/FrameworkWiring.html#getDependencyClosure%28java.util.Collection%29]
 to get an estimate of what all bundles would be effected by bundles being 
update. If the ratio is high then we should take the lowest startLevel

Any other heuristics if possible

[~cziegeler], [~fmeschbe] Thoughts?

> [OSGi Installer] Intelligently manage start level during artifact handling
> --
>
> Key: SLING-3749
> URL: https://issues.apache.org/jira/browse/SLING-3749
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3749.patch
>
>
> OSGi Installer should be made more intelligent in deciding how to handle 
> bundle updates, if multiple bundles need to be updated e.g. by lowering the 
> system start level when updating important bundles or when updating a large 
> number of bundles to reduce oscillation of the system and thus reduce update 
> time and increase stability.
> Some thoughts around this as per [~fmeschbe]:
> * Bundle installations are not problematic and don't need to be treated 
> specially
> * Bundle updates and uninstallations may cause the system to oscillated 
> because services may come and go during updates and package refreshes
> * Some bundles are more central than other bundles. For example the  bundle 
> providing the JCR Repository service is "used" by almost all of the system. 
> And bundle may be important because a certain threshold if API importing 
> bundles is reached (e.g. the Sling API bundle) or because one of the 
> registered services is used by a certain threshold of consumers.
> * When at least one important bundle is updated or uninstalled in a single 
> batch, the OSGi installer should reduce the system start level before 
> handling the batch and raise the start level after the batch again.
> * The start level to which the system is reduced is the lower of the start 
> level of the OSGi installer and its helper bundles (probably the Task 
> provides) and the start levels of the important bundle(s) handled in the 
> batch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[VOTE] Release Apache Sling Settings 1.3.2

[Carsten Ziegeler]

Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING-3737

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1080

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1080 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards,
Carsten

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Issue Comment Deleted] (SLING-3578) Support mapping amendments for service user mapper

[Antonio Sanso (JIRA)]

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

Antonio Sanso updated SLING-3578:
-

Comment: was deleted

(was: I am out of office, back on June 22.

regards

antonio


)

> Support mapping amendments for service user mapper
> --
>
> Key: SLING-3578
> URL: https://issues.apache.org/jira/browse/SLING-3578
> Project: Sling
>  Issue Type: Improvement
>  Components: Service User Mapper
>Reporter: Antonio Sanso
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Service User Mapper 1.0.2
>
>
> It would be nice to have a way to support an application deployment providing 
> some service user mapping configuration to ammend/merge the existing 
> configuration.  
> See also discussion in [0]
> [0] http://sling.markmail.org/thread/nxs4dqqiejvvkcx2



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Authentication XING Login #1174

[Apache Jenkins Server]

See 


Changes:

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.login-0.0.2

[olli] SLING-3732 use org.apache.sling.auth.xing.api 0.0.2

[olli] SLING-3732 add package info

[olli] style

--
[INFO] 
[INFO] 
[INFO] Building Apache Sling Authentication XING Login 0.0.3-SNAPSHOT
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.core/1.1.6/org.apache.sling.auth.core-1.1.6.pom
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.core/1.1.6/org.apache.sling.auth.core-1.1.6.pom
 (7 KB at 288.6 KB/sec)
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.xing.api/0.0.2/org.apache.sling.auth.xing.api-0.0.2.pom
[WARNING] The POM for org.apache.sling:org.apache.sling.auth.xing.api:jar:0.0.2 
is missing, no dependency information available
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.2/org.apache.sling.jcr.jackrabbit.server-2.1.2.pom
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.jackrabbit.server/2.1.2/org.apache.sling.jcr.jackrabbit.server-2.1.2.pom
 (10 KB at 5.7 KB/sec)
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.core/1.1.6/org.apache.sling.auth.core-1.1.6.jar
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.xing.api/0.0.2/org.apache.sling.auth.xing.api-0.0.2.jar
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.auth.core/1.1.6/org.apache.sling.auth.core-1.1.6.jar
 (85 KB at 5.0 KB/sec)
[JENKINS] Archiving disabled

Build failed in Jenkins: sling-contrib-1.6 #1174

[Apache Jenkins Server]

See 

Changes:

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.oauth-0.0.2

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.login-0.0.2

[olli] SLING-3731 use org.apache.sling.auth.xing.api 0.0.2

[olli] SLING-3731 set version of package org.apache.sling.auth.xing.oauth to 
0.0.2

[olli] SLING-3732 use org.apache.sling.auth.xing.api 0.0.2

[olli] SLING-3732 add package info

[olli] style

[olli] [maven-release-plugin] prepare for next development iteration

[olli] [maven-release-plugin] prepare release 
org.apache.sling.auth.xing.api-0.0.2

[olli] SLING-3731 SLING-3732 set version of packages 
org.apache.sling.auth.xing.api and org.apache.sling.auth.xing.api.users to 0.0.2

--
[...truncated 143 lines...]
[INFO] Apache Sling JCR Resource Security
[INFO] Apache Sling Launchpad Karaf
[INFO] Apache Sling Launchpad Karaf - Features
[INFO] Apache Sling Launchpad Karaf - Integration Tests
[INFO] Apache Sling Launchpad Karaf Builder
[INFO] Apache Sling Launchpad Contrib Testing
[INFO] Apache Sling Script Console
[INFO] Apache Sling Atom Tag Library
[INFO] Apache Sling Scripting Freemarker Support
[INFO] Apache Sling Scripting Java Support
[INFO] Apache Sling Scripting JST Support
[INFO] Apache Sling Scripting Python Support
[INFO] Apache Sling Scripting Ruby Support
[INFO] Apache Sling Scripting Velocity Support
[INFO] Apache Sling Scripting W3C XML Processing Support
[INFO] Scala Script Engine
[INFO] Apache Sling Scala Scripting Configuration
[INFO] Scala for Sling Demo Application - Hello World
[INFO] Scala for Sling Demo Application - Forum
[INFO] Apache Sling Contrib (Builder)
[INFO] 
[INFO] 
[INFO] Building Apache Sling Authentication XING API 0.0.3-SNAPSHOT
[INFO] 
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.api/2.2.0/org.apache.sling.jcr.api-2.2.0.pom
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.api/2.2.0/org.apache.sling.jcr.api-2.2.0.pom
 (3 KB at 11.5 KB/sec)
Downloading: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/bndlib/2.3.0/bndlib-2.3.0.pom
Downloaded: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/bndlib/2.3.0/bndlib-2.3.0.pom 
(2 KB at 40.9 KB/sec)
Downloading: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/parent/2.3.0/parent-2.3.0.pom
Downloaded: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/parent/2.3.0/parent-2.3.0.pom 
(5 KB at 150.0 KB/sec)
Downloading: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.api/2.2.0/org.apache.sling.jcr.api-2.2.0.jar
Downloading: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/bndlib/2.3.0/bndlib-2.3.0.jar
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.jcr.api/2.2.0/org.apache.sling.jcr.api-2.2.0.jar
 (13 KB at 910.6 KB/sec)
Downloaded: 
http://repo.maven.apache.org/maven2/biz/aQute/bnd/bndlib/2.3.0/bndlib-2.3.0.jar 
(1744 KB at 10443.1 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run 
(set-bundle-required-execution-environment) @ org.apache.sling.auth.xing.api ---
[INFO] Executing tasks

main:
Setting Bundle-RequiredExecutionEnvironment=JavaSE-1.6 from sling.java.version=6
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
org.apache.sling.auth.xing.api ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
org.apache.sling.auth.xing.api ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ 
org.apache.sling.auth.xing.api ---
[INFO] Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks
[INFO] 
[INFO] --- mave

[jira] [Created] (SLING-3749) [OSGi Installer] Intelligently manage start level during artifact handling

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created SLING-3749:
--

 Summary: [OSGi Installer] Intelligently manage start level during 
artifact handling
 Key: SLING-3749
 URL: https://issues.apache.org/jira/browse/SLING-3749
 Project: Sling
  Issue Type: Improvement
Reporter: Chetan Mehrotra


OSGi Installer should be made more intelligent in deciding how to handle bundle 
updates, if multiple bundles need to be updated e.g. by lowering the system 
start level when updating important bundles or when updating a large number of 
bundles to reduce oscillation of the system and thus reduce update time and 
increase stability.

Some thoughts around this as per [~fmeschbe]:

* Bundle installations are not problematic and don't need to be treated 
specially
* Bundle updates and uninstallations may cause the system to oscillated because 
services may come and go during updates and package refreshes
* Some bundles are more central than other bundles. For example the  bundle 
providing the JCR Repository service is "used" by almost all of the system. And 
bundle may be important because a certain threshold if API importing bundles is 
reached (e.g. the Sling API bundle) or because one of the registered services 
is used by a certain threshold of consumers.
* When at least one important bundle is updated or uninstalled in a single 
batch, the OSGi installer should reduce the system start level before handling 
the batch and raise the start level after the batch again.
* The start level to which the system is reduced is the lower of the start 
level of the OSGi installer and its helper bundles (probably the Task provides) 
and the start levels of the important bundle(s) handled in the batch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3749) [OSGi Installer] Intelligently manage start level during artifact handling

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra updated SLING-3749:
---

Component/s: Installer

> [OSGi Installer] Intelligently manage start level during artifact handling
> --
>
> Key: SLING-3749
> URL: https://issues.apache.org/jira/browse/SLING-3749
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Reporter: Chetan Mehrotra
>
> OSGi Installer should be made more intelligent in deciding how to handle 
> bundle updates, if multiple bundles need to be updated e.g. by lowering the 
> system start level when updating important bundles or when updating a large 
> number of bundles to reduce oscillation of the system and thus reduce update 
> time and increase stability.
> Some thoughts around this as per [~fmeschbe]:
> * Bundle installations are not problematic and don't need to be treated 
> specially
> * Bundle updates and uninstallations may cause the system to oscillated 
> because services may come and go during updates and package refreshes
> * Some bundles are more central than other bundles. For example the  bundle 
> providing the JCR Repository service is "used" by almost all of the system. 
> And bundle may be important because a certain threshold if API importing 
> bundles is reached (e.g. the Sling API bundle) or because one of the 
> registered services is used by a certain threshold of consumers.
> * When at least one important bundle is updated or uninstalled in a single 
> batch, the OSGi installer should reduce the system start level before 
> handling the batch and raise the start level after the batch again.
> * The start level to which the system is reduced is the lower of the start 
> level of the OSGi installer and its helper bundles (probably the Task 
> provides) and the start levels of the important bundle(s) handled in the 
> batch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[VOTE] Release Apache Sling Authentication XING Login 0.0.2

[Oliver Lietz]

Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12327253/

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1078/

You can use this UNIX script to download the release and verify the 
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1078 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards,
O.

[VOTE] Release Apache Sling Authentication XING OAuth 0.0.2

[Oliver Lietz]

Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12327252/

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1079/

You can use this UNIX script to download the release and verify the 
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1079 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards,
O.

[VOTE] Release Apache Sling Authentication XING API 0.0.2

[Oliver Lietz]

Hi,

This is a shared API bundle for Sling Authentication XING Login and Sling 
Authentication XING OAuth:
https://issues.apache.org/jira/browse/SLING/fixforversion/12327251/

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1077/

You can use this UNIX script to download the release and verify the 
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1077 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards,
O.

Jenkins build is still unstable: sling-trunk-1.6 #2271

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #644

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-3737.
-

Resolution: Fixed

Thanks, Timothee for the patch. It's applied now

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though the end of the stream was not reached.
> If this is the case, the current logic will treat the slingId as invalid and 
> generate a new one.
> A way to fix that is to read the sling id file completely, for instance using 
> the org.apache.commons.io.FileUtils API
> We are running on CentOS 6.2, JDK 1.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Eclipse stuff, source vs. convenience binaries

[Robert Munteanu]

> Ack, I'll prepare a source bundle today and upload it to my personal
> space for voting.

Started a different thread for the source bundle inclusion vote at [1]

Robert

[1]: http://sling-dev.markmail.org/thread/44dqce2svxopkdz5

[VOTE] Include ide tooling source bundle on dist.apache.org

[Robert Munteanu]

Hi,

As Bertrand has noticed [1], the Sling IDE Tooling 1.0.0 release does
not include a source bundle on dist.apache.org .

Following that discussion, I propose that we upload a source bundle at
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ . The
source bundle is a plain SVN export from the tag used to generate the
1.0.0 release.

The candidate source bundle is uploaded at [2] . It can be used to
rebuild the IDE tooling with

   mvn clean package

Please vote to approve this inclusion.

Thanks,

Robert

[1]: http://markmail.org/thread/hgxbejjrmn4wrpsv
[2]: https://people.apache.org/~rombert/sling/sling-ide-tooling-1.0.0/

[jira] [Created] (SLING-3748) Provide single update site url which works for the latest version

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-3748:
--

 Summary: Provide single update site url which works for the latest 
version
 Key: SLING-3748
 URL: https://issues.apache.org/jira/browse/SLING-3748
 Project: Sling
  Issue Type: Improvement
  Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Robert Munteanu
 Fix For: Sling Eclipse IDE 1.0.2


As asked by [~kwin] on the dev list ( 
http://sling-dev.markmail.org/thread/oxfu6vkggjjmp655 ) , we should provide an 
update site URL which always points to the latest release.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Sling IDE Tooling P2-Update-Site URL

[Robert Munteanu]

Hi Konrad,

On Tue, Jul 8, 2014 at 5:04 PM, Konrad Windszus  wrote:
>
> Currently the update site for Eclipse is deployed at 
> //sling/eclipse/1.0.0. If installing from there, one 
> would never get notified about updates, because that Update Site will always 
> only contain 1.0.0. Once there is a new version a new Update Site will be 
> deployed at a different URL.
> Please provide a stable update URL which always points to the most recent 
> (release) version of Sling IDE Tools.

Good idea, filed https://issues.apache.org/jira/browse/SLING-3748 for this.

> Thanks,
> Konrad
>
> P.S. The table of contents within http://sling.apache.org/downloads.cgi (in 
> the second paragraph below headline downloads) does not mention Sling IDE 
> Tooling.

Now fixed, thanks for noticing.

Robert


-- 
Sent from my (old) computer

Sling IDE Tooling P2-Update-Site URL

[Konrad Windszus]

Currently the update site for Eclipse is deployed at 
//sling/eclipse/1.0.0. If installing from there, one 
would never get notified about updates, because that Update Site will always 
only contain 1.0.0. Once there is a new version a new Update Site will be 
deployed at a different URL. 
Please provide a stable update URL which always points to the most recent 
(release) version of Sling IDE Tools.
Thanks,
Konrad

P.S. The table of contents within http://sling.apache.org/downloads.cgi (in the 
second paragraph below headline downloads) does not mention Sling IDE Tooling.

Jenkins build is still unstable: sling-trunk-1.6 #2270

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-3294) Simplify Performance Test Creation

[Antonio Sanso (JIRA)]

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

Antonio Sanso resolved SLING-3294.
--

Resolution: Fixed

> Simplify Performance Test Creation
> --
>
> Key: SLING-3294
> URL: https://issues.apache.org/jira/browse/SLING-3294
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Performance 1.0.0
>
>
> The current mechanism of differentiate between performance tests is a bit 
> cumbersome and requires to have a different class for different test 
> parameter.
> The new mechanism will avoid to have those ad-hoc classes



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Reopened] (SLING-3294) Simplify Performance Test Creation

[Antonio Sanso (JIRA)]

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

Antonio Sanso reopened SLING-3294:
--


> Simplify Performance Test Creation
> --
>
> Key: SLING-3294
> URL: https://issues.apache.org/jira/browse/SLING-3294
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Performance 1.0.0
>
>
> The current mechanism of differentiate between performance tests is a bit 
> cumbersome and requires to have a different class for different test 
> parameter.
> The new mechanism will avoid to have those ad-hoc classes



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3294) Simplify Performance Test Creation

[Antonio Sanso (JIRA)]

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

Antonio Sanso updated SLING-3294:
-

Fix Version/s: Performance 1.0.0

> Simplify Performance Test Creation
> --
>
> Key: SLING-3294
> URL: https://issues.apache.org/jira/browse/SLING-3294
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Performance 1.0.0
>
>
> The current mechanism of differentiate between performance tests is a bit 
> cumbersome and requires to have a different class for different test 
> parameter.
> The new mechanism will avoid to have those ad-hoc classes



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Timothee Maret (JIRA)]

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

Timothee Maret commented on SLING-3737:
---

bq. I don't want to allow the Sling ID to be easily specified by users. This is 
not the goal of the Sling ID.

Ok.

I added a new patch leveraging Data[Input|Output]Stream, please shop, improve 
and fix :-)

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though the end of the stream was not reached.
> If this is the case, the current logic will treat the slingId as invalid and 
> generate a new one.
> A way to fix that is to read the sling id file completely, for instance using 
> the org.apache.commons.io.FileUtils API
> We are running on CentOS 6.2, JDK 1.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Timothee Maret (JIRA)]

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

Timothee Maret updated SLING-3737:
--

Attachment: SLING-3737.diff

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though the end of the stream was not reached.
> If this is the case, the current logic will treat the slingId as invalid and 
> generate a new one.
> A way to fix that is to read the sling id file completely, for instance using 
> the org.apache.commons.io.FileUtils API
> We are running on CentOS 6.2, JDK 1.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Release Apache Sling Scripting Thymeleaf 0.0.2

[Oliver Lietz]

On Monday 07 July 2014 21:40:08 Oliver Lietz wrote:
> Hi,
> 
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12327184/

+1

O.

Re: [VOTE] Release Apache Sling Scripting Thymeleaf 0.0.2

[Oliver Lietz]

On Tuesday 08 July 2014 07:30:26 Chetan Mehrotra wrote:
> Hi Oliver,

Hi Chetan,

> On Tue, Jul 8, 2014 at 1:10 AM, Oliver Lietz  wrote:
> > sh check_staged_release.sh 1076 /tmp/sling-staging
> 
> +1 for the release.
> All checks ok
> 
> One minor note - Currently quite a few classes are part of public
> package 'org.apache.sling.scripting.thymeleaf'. May be all are not
> required in Export-Package like SlingWebContext,
> ThymeleafScriptEngine, ThymeleafScriptEngineFactory.

thanks for having a closer look and sharing your opinion.
They are indeed not required and I will move them to impl before the next 
release. I hadn't a strong opinion on that as some of our other scripting 
bundles handle it similar and some not.

Regards,
O.

> Chetan Mehrotra

[jira] [Commented] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-3741:


* http://svn.apache.org/viewvc?view=revision&revision=1608772 - simplified 
repository API for deleting nodes
* http://svn.apache.org/viewvc?view=revision&revision=1608773 - when resource 
data is found in a covering parent on a resource delete,  generate an 
add/update operation instead.

[~egli] - with the above changes, folder deletion should no longer be 
problematic, given that the parent's .content.xml is changed beforehand. Can 
you please cross-check?

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-3737:
--

The Sling ID is a machine identifier which is why it is a UUID for good 
uniqueness garantee. I don't want to allow the Sling ID to be easily specified 
by users. This is not the goal of the Sling ID.

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though the end of the stream was not reached.
> If this is the case, the current logic will treat the slingId as invalid and 
> generate a new one.
> A way to fix that is to read the sling id file completely, for instance using 
> the org.apache.commons.io.FileUtils API
> We are running on CentOS 6.2, JDK 1.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is still unstable: sling-trunk-1.6 #2269

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Event Support #2269

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #2269

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2269

[Apache Jenkins Server]

See 

[jira] [Comment Edited] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Timothee Maret (JIRA)]

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

Timothee Maret edited comment on SLING-3737 at 7/8/14 12:58 PM:


bq. Timothee Maret DataInputStream.readFully(byte[]) introduces no platform 
dependency since this just makes sure all bytes are read as-is.

Indeed, DataInputStream representation should be compatible among platforms.. 
but AFAIK, it is an opaque binary format.
If the Sling.id.file is not meant to be edited, then whatever representation 
would fit.
The DataInputStream has the advantage of not requiring an ad-hoc reader given 
the no external lib constraint.

With the DataInputStream solution, I think it would make sense to offer a way 
to allow users to specify sling identifiers.
This would allow to define structured scheme of identifiers which would be 
easier for a human to deal with.


was (Author: marett):
bq. Timothee Maret DataInputStream.readFully(byte[]) introduces no platform 
dependency since this just makes sure all bytes are read as-is.

Indeed, DataInputStream representation should be compatible among platforms.. 
but AFAIK, it is an opaque binary format.
If the Sling.id.file is not meant to be edited, then whatever representation 
would fit.
The DataInputStream has the advantage of not requiring an ad-hoc reader given 
the no external lib constraint.

In any case, I think it would make sense to offer a way to allow users to 
specify sling identifiers.
This would allow to define structured scheme of identifiers which would be 
easier for a human to deal with.

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though 

[jira] [Commented] (SLING-3290) Long startup time with many vanityPath

[Antonio Sanso (JIRA)]

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

Antonio Sanso commented on SLING-3290:
--

added performance test in rev. r1608751

> Long startup time with many vanityPath
> --
>
> Key: SLING-3290
> URL: https://issues.apache.org/jira/browse/SLING-3290
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>  Labels: vanity
> Attachments: StartupWithManyVanityPath.jpg
>
>
> When many vanityPath or alias are present the system take long time to 
> startup , Same when a vanityPath/alias is removed or updated .
> The reason behind is the usage of a query that updates the global mapentry.
> I have added a new Test to the performance test suite and this is the outcome
> {code}
> 0 vanityPath  16ms
> 1  vanityPath 19ms
> 10 vanityPath 70ms
> 100 vanityPath111ms
> 1000 vanityPath   200ms
> 1 vanityPath  1173ms
> 3 vanityPath  3358ms
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[Timothee Maret (JIRA)]

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

Timothee Maret commented on SLING-3737:
---

bq. Timothee Maret DataInputStream.readFully(byte[]) introduces no platform 
dependency since this just makes sure all bytes are read as-is.

Indeed, DataInputStream representation should be compatible among platforms.. 
but AFAIK, it is an opaque binary format.
If the Sling.id.file is not meant to be edited, then whatever representation 
would fit.
The DataInputStream has the advantage of not requiring an ad-hoc reader given 
the no external lib constraint.

In any case, I think it would make sense to offer a way to allow users to 
specify sling identifiers.
This would allow to define structured scheme of identifiers which would be 
easier for a human to deal with.

> Instance Sling Identifier may be randomly reset on restart
> --
>
> Key: SLING-3737
> URL: https://issues.apache.org/jira/browse/SLING-3737
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Settings 1.3.0
>Reporter: Timothee Maret
>Assignee: Carsten Ziegeler
> Fix For: Settings 1.3.2
>
> Attachments: SLING-3737.diff, SLING-3737.diff
>
>
> In our Setup, we experience instances changing their Sling identifier upon 
> restart.
> We have experienced only a few occurrences of this issue, but the effect is 
> really bad, turning the services relying on the Sling Identifier into 
> unexpected state (for instance Sling discovery service).
> We have checked that the sling.id.file was present before the issue occurred.
> We also checked that the value in this file was valid (36 byte long UUID).
> Despite having a valid sling.id.file file, the instance sometimes reset the 
> Sling ID upon restart.
> Looking at the latest code in 
> org.apache.sling.settings.impl.SlingSettingsServiceImpl#readSlingId
> it seems there is a bug in the way the sling id is read from the file 
> sling.id.file.
> {code}
> private String readSlingId(final File idFile) {
> if (idFile.exists() && idFile.length() >= 36) {
> FileInputStream fin = null;
> try {
> fin = new FileInputStream(idFile);
> final byte[] rawBytes = new byte[36];
> if (fin.read(rawBytes) == 36) {
> final String rawString = new String(rawBytes, 
> "ISO-8859-1");
> // roundtrip to ensure correct format of UUID value
> final String id = UUID.fromString(rawString).toString();
> logger.debug("Got Sling ID {} from file {}", id, idFile);
> return id;
> }
> } catch (final Throwable t) {
> logger.error("Failed reading UUID from id file " + idFile
> + ", creating new id", t);
> } finally {
> if (fin != null) {
> try {
> fin.close();
> } catch (IOException ignore) {
> }
> }
> }
> }
> return null;
> }
> {code}
> In the line
> {code}
> if (fin.read(rawBytes) == 36) {
> {code}
> The code miss uses the java.io.FileInputStream#read API.
> {code}
> /**
>  * Reads up to b.length bytes of data from this input
>  * stream into an array of bytes. This method blocks until some input
>  * is available.
>  *
>  * @param  b   the buffer into which the data is read.
>  * @return the total number of bytes read into the buffer, or
>  * -1 if there is no more data because the end of
>  * the file has been reached.
>  * @exception  IOException  if an I/O error occurs.
>  */
> {code}
> The API stipulates that the method blocks until if finds *some* data.
> This is a common pattern with Java IO APIs, and indeed, the method may return 
> with only one byte read even though the end of the stream was not reached.
> If this is the case, the current logic will treat the slingId as invalid and 
> generate a new one.
> A way to fix that is to read the sling id file completely, for instance using 
> the org.apache.commons.io.FileUtils API
> We are running on CentOS 6.2, JDK 1.7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource Access Security Integration Tests #643

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #643

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-3712) Increase code coverage for MapEntries

[Antonio Sanso (JIRA)]

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

Antonio Sanso resolved SLING-3712.
--

   Resolution: Fixed
Fix Version/s: Resource Resolver 1.1.2

> Increase code coverage for MapEntries
> -
>
> Key: SLING-3712
> URL: https://issues.apache.org/jira/browse/SLING-3712
> Project: Sling
>  Issue Type: Task
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Resource Resolver 1.1.2
>
>
> With SLING-3505 the internal of the MapEntries class has changed quite 
> substantially hence it would be good to increase the code coverage of this 
> area



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Eclipse stuff, source vs. convenience binaries

[Robert Munteanu]

On Tue, 2014-07-08 at 14:27 +0200, Bertrand Delacretaz wrote:
> Hi,
> 
> On Tue, Jul 8, 2014 at 2:05 PM, Robert Munteanu  wrote:
> > ...So what should the next step from me be? Upload the source bundle for
> > 1.0.0 release and restart the 1.0.0 vote?...
> 
> I think you can just put the 1.0.0 source archive somewhere
> (people.apache.org/~rombert for example) so that we can vote to add it
> to the existing 1.0.0 release at dist/release/sling/eclipse. No need
> to update what was released on Maven as that's only convenience
> binaries anyway.


Ack, I'll prepare a source bundle today and upload it to my personal
space for voting.

Thanks,

Robert

[jira] [Updated] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3741:
---

Attachment: sling3741.zip

bq. I'm not sure this example is correct.
I've attached a sample (partial!) zip which contains the two .content.xml that 
I've played around with. I do get that structure starting with 'grandpa' 
aggregated into one .content.xml though..

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Eclipse stuff, source vs. convenience binaries

[Bertrand Delacretaz]

Hi,

On Tue, Jul 8, 2014 at 2:05 PM, Robert Munteanu  wrote:
> ...So what should the next step from me be? Upload the source bundle for
> 1.0.0 release and restart the 1.0.0 vote?...

I think you can just put the 1.0.0 source archive somewhere
(people.apache.org/~rombert for example) so that we can vote to add it
to the existing 1.0.0 release at dist/release/sling/eclipse. No need
to update what was released on Maven as that's only convenience
binaries anyway.

-Bertrand

[jira] [Commented] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-3741:


I was able to reproduce the problem with a slightly different content 
structure. Starting with:

{code}
mapping [sling:Mapping]
\- jcr:content [nt:unstructured]
 \- par [nt:unstructured]
  \- folder [sling:Folder] 
{code}

delete the {{mapping/_jcr_content}} folder. 

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3747) Provide a way to signal Jcr Installer to pause and resume scanning

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra updated SLING-3747:
---

Attachment: SLING-3747-1.patch

Updated patch[|^SLING-3747-1.patch]

bq. I have the suspicion, that the property event may not always be caught if 
the /system/sling/installer/jcr node is removed instead of the property. In 
fact the listener is also not triggered if the property is removed.

Updated the code to also look for property removed. It would address both the 
above cases

bq. I wonder whether it would be sufficient to just check for the property 
during runOneCycle and ignore the cycle if the property is set ?

The check is being done in the while loop which invokes the runOneCycle. If we 
trip inside runOneCycle then it might cause issue as needScan flag of various 
folders would have been reset and we might loose info from those folders if no 
change happen in them by the time we run next cycle while running



> Provide a way to signal Jcr Installer to pause and resume scanning
> --
>
> Key: SLING-3747
> URL: https://issues.apache.org/jira/browse/SLING-3747
> Project: Sling
>  Issue Type: New Feature
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3747-1.patch, SLING-3747.patch
>
>
> Currently Sling Installer JCR Provider would listen for observation event and 
> would perform a rescan every 500 msec upon receiving any observation event. 
> This at times cause issue when large number of bundles get updated in 
> repository say via installation of bug fixing content package. Further if 
> same content package also updates the repository bundle then it causes issues 
> as repository bundle might get updated midway while content package is still 
> being deployed
> Based on [~fmeschbe] suggestion this can be done via introducing a signalling 
> mechanism between component which installs package and JCR Installer. It 
> would work something like this
> # JCR Installer would listen to changes done to property 
> {{/system/sling/installer/jcr/pauseInstallation}}
> # Package installer would set the above flag to true before installing the 
> package and reset it back to false post installation
> # If JCR Installer detects that flag is set to true it would not scan the 
> watch folders untill it get reset back to false
> This should also address the issue in cluster deployment



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Eclipse stuff, source vs. convenience binaries

[Robert Munteanu]

On Tue, 2014-07-08 at 13:59 +0200, Bertrand Delacretaz wrote:
> On Tue, Jul 8, 2014 at 9:13 AM, Robert Munteanu  wrote:
> > On Mon, 2014-07-07 at 11:58 +0200, Bertrand Delacretaz wrote:
> >>...if you can put it in
> >> https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ in a
> >> way that doesn't disturb Eclipse that's probably best?
> >>
> >> And add a link to that file to the
> >> http://apache.org/dist/sling/eclipse/1.0.0/index.html page with a
> >> recommendation to build from source?
> >
> > Yes, I'll do both of the above, after we've clarified that indeed it's
> > OK to upload the source bundle...
> 
> If we didn't vote on that source bundle we need to do that, so its a
> decision of the PMC to release it.

So what should the next step from me be? Upload the source bundle for
1.0.0 release and restart the 1.0.0 vote? Or rather take down the 1.0.0
release and start the 1.0.2 release vote?

And what should the process be? Would it be acceptable from a release
POV if I

1. Uploaded a source bundle in a staging repo, which can undergo the
regular release process
2. Once the vote is successful, drop the staging repo ( since the source
bundle is not a usable Maven artifact ) and upload the following
artifacts to dist/release/sling/eclipse ( names shortened just for this
email )

- 1.0.0/source-bundle-1.0.0.zip
- 1.0.0/update-site-1.0.0.zip
- 1.0.0/(all jars/xmls required for a p2 update site )

Thanks,

Robert

Re: Eclipse stuff, source vs. convenience binaries

[Bertrand Delacretaz]

On Tue, Jul 8, 2014 at 9:13 AM, Robert Munteanu  wrote:
> On Mon, 2014-07-07 at 11:58 +0200, Bertrand Delacretaz wrote:
>>...if you can put it in
>> https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ in a
>> way that doesn't disturb Eclipse that's probably best?
>>
>> And add a link to that file to the
>> http://apache.org/dist/sling/eclipse/1.0.0/index.html page with a
>> recommendation to build from source?
>
> Yes, I'll do both of the above, after we've clarified that indeed it's
> OK to upload the source bundle...

If we didn't vote on that source bundle we need to do that, so its a
decision of the PMC to release it.

-Bertrand

[jira] [Commented] (SLING-3747) Provide a way to signal Jcr Installer to pause and resume scanning

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-3747:
--

Thanks for providing the patch.

Some remarks:

* runOneCycle should probably also check for the property
* I have the suspicion, that the property event may not always be caught if the 
{{/system/sling/installer/jcr}} node is removed instead of the property. In 
fact the listener is also not triggered if the property is removed.

I wonder whether it would be sufficient to just check for the property during 
runOneCycle and ignore the cycle if the property is set ?

> Provide a way to signal Jcr Installer to pause and resume scanning
> --
>
> Key: SLING-3747
> URL: https://issues.apache.org/jira/browse/SLING-3747
> Project: Sling
>  Issue Type: New Feature
>  Components: Installer
>Reporter: Chetan Mehrotra
> Attachments: SLING-3747.patch
>
>
> Currently Sling Installer JCR Provider would listen for observation event and 
> would perform a rescan every 500 msec upon receiving any observation event. 
> This at times cause issue when large number of bundles get updated in 
> repository say via installation of bug fixing content package. Further if 
> same content package also updates the repository bundle then it causes issues 
> as repository bundle might get updated midway while content package is still 
> being deployed
> Based on [~fmeschbe] suggestion this can be done via introducing a signalling 
> mechanism between component which installs package and JCR Installer. It 
> would work something like this
> # JCR Installer would listen to changes done to property 
> {{/system/sling/installer/jcr/pauseInstallation}}
> # Package installer would set the above flag to true before installing the 
> package and reset it back to false post installation
> # If JCR Installer detects that flag is set to true it would not scan the 
> watch folders untill it get reset back to false
> This should also address the issue in cluster deployment



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is still unstable: sling-trunk-1.6 #2268

[Apache Jenkins Server]

See