[VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Carsten Ziegeler]

Hi,

as announced it's time for some more releases :)

Apart from our first releases of
OSGi Installer 3.0.0
JCR Installer 3.0.0
File Installer 1.0.0

I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314354


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

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 039 /tmp/sling-staging

Please vote to approve this release:

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

This vote will be open for 72 hours.

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

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Carsten Ziegeler]

+1 Approve the release

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

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

[Apache Hudson Server]

See 

Changes:

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

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.install.fileinstall-1.0.0

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

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.jcr.jcrinstall-3.0.0

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

[cziegeler] Prepare release

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.commons.testing-2.0.6

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

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.osgi.installer-3.0.0

[cziegeler] Prepare release

[cziegeler] No need for extra type constants

--
[...truncated 16879 lines...]
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at 
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Invalid BundleContext.
at 
org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:393)
at 
org.apache.felix.framework.BundleContextImpl.getBundle(BundleContextImpl.java:92)
at 
org.ops4j.pax.logging.OSGIPaxLoggingManager.getLogger(OSGIPaxLoggingManager.java:95)
at 
org.ops4j.pax.logging.slf4j.Slf4jLoggerFactory.getLogger(Slf4jLoggerFactory.java:90)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at 
org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155)
at 
org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:272)
at 
org.ops4j.pax.exam.junit.extender.impl.internal.CallableTestMethodImpl.(CallableTestMethodImpl.java:54)
... 24 more
ERROR: EventDispatcher: Error during dispatch. 
(java.lang.IllegalStateException: Invalid BundleContext.)
java.lang.IllegalStateException: Invalid BundleContext.
at 
org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:393)
at 
org.apache.felix.framework.BundleContextImpl.getBundle(BundleContextImpl.java:92)
16.09.2010 09:42:44.012 *INFO* [main] 
org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test 
testContextUpdate 
[felix](org.apache.sling.osgi.installer.it.ContextBundleUpdateTest)
at 
org.ops4j.pax.logging.OSGIPaxLoggingManager.getLogger(OSGIPaxLoggingManager.java:95)
at 
org.ops4j.pax.logging.slf4j.Slf4jLoggerFactory.getLogger(Slf4jLoggerFactory.java:90)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:209)
at 
org.apache.sling.commons.log.internal.LogSupport.getLogger(LogSupport.java:393)
at 
org.apache.sling.commons.log.internal.LogSupport.logOut(LogSupport.java:408)
at 
org.apache.sling.commons.log.internal.LogSupport.fireLogEvent(LogSupport.java:203)
at 
org.apache.sling.commons.log.internal.LogSupport.bundleChanged(LogSupport.java:249)
at 
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800)
at 
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728)
at 
org.apache.felix.framework.util.EventDispatcher.run(EventDispatcher.java:956)
at 
org.apache.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:54)
at 
org.apache.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:106)
at java.lang.Thread.run(Thread.java:595)
[org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl] : Remote call of 
[org.ops4j.pax.exam.junit.extender.CallableTestMethod.call]
[org.ops4j.pax.exam.rbc.internal.RemoteBundleContextImpl] : Look up service 
[org.ops4j.pax.exam.junit.extender.CallableTestMethod], timeout in 0 millis
16.09.2010 09:42:44.017 *INFO* [main] 
org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Shutting down 
the test container (Pax Runner)

ERROR: EventDispatcher: Error during dispatch. 
(java.lang.IllegalStateException: Invalid BundleContext.)
java.lang.IllegalStateException: Invalid BundleContext.
at 
org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:393)
at 
org.apache.felix.framework.BundleContextImpl.getBundle(BundleContextImpl.java:92)
at 
org.ops4j.pax.logging.OSGIPaxLoggingManager.getLogger(OSGIPaxLoggingManager.java:95)
   

Hudson build is still unstable: sling-trunk-1.5 » Apache Sling OSGi Installer Integration Tests #888

[Apache Hudson Server]

See 

[jira] Created: (SLING-1779) Content loader activator does not logout session

[Felix Meschberger (JIRA)]

Content loader activator does not logout session


 Key: SLING-1779
 URL: https://issues.apache.org/jira/browse/SLING-1779
 Project: Sling
  Issue Type: Bug
  Components: JCR
Affects Versions: JCR ContentLoader 2.1.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
 Fix For: JCR ContentLoader 2.1.2


The JCR Content Loader bundle activator acquires a session to load content of 
bundles installed before the content loader is started. Unfortunately this 
session is not logged out and may leak resources.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SLING-1779) Content loader activator does not logout session

[Felix Meschberger (JIRA)]

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

Felix Meschberger resolved SLING-1779.
--

Resolution: Fixed

Fixed in Rev 997684.

> Content loader activator does not logout session
> 
>
> Key: SLING-1779
> URL: https://issues.apache.org/jira/browse/SLING-1779
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR ContentLoader 2.1.0
>Reporter: Felix Meschberger
>Assignee: Felix Meschberger
> Fix For: JCR ContentLoader 2.1.2
>
>
> The JCR Content Loader bundle activator acquires a session to load content of 
> bundles installed before the content loader is started. Unfortunately this 
> session is not logged out and may leak resources.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1777) Build error: JobEventHandlerTest

[Pontus Amberg (JIRA)]

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

Pontus Amberg commented on SLING-1777:
--

I'm not sure this will help but I had lots of strange build problems when using 
Maven 3.0-beta 3 a while ago. Downgrading to Maven 2.2.1 seems to have solved 
those problems for me. I just built the current trunk with no failing tests 
using maven 2.2.1 on an Ubuntu 10.04 installation.

> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 63.362 sec 
> <<< FAILURE!
> Running org.apache.sling.event.EventUtilTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec
> Results :
> Failed tests: 
>   testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: SLING-1741

[Felix Meschberger]

Hi,

I owe you an answer and will provide one shortly 

Just did not get around to do it.

Regards
Felix

Am 10.09.2010 04:12, schrieb Justin Edelson:
> I put up a proposed patch for SLING-1741 at
> http://codereview.appspot.com/2144046
> 
> This didn't seem to break any integration tests, but I also commented
> out the whole "cutting off the selector/suffix" part and got no
> integration test failures, so I'm concerned the code involved might not
> be well-tested. Could someone involved in SLING-588 take a look?
> 
> Thanks,
> Justin
> 

RE: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Stefan Seifert]

+1 (non-binding)

>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Thursday, September 16, 2010 9:48 AM
>To: Sling Developers
>Subject: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR
>Installer 3.0.0, and File Installer 1.0.0
>
>Hi,
>
>as announced it's time for some more releases :)
>
>Apart from our first releases of
>OSGi Installer 3.0.0
>JCR Installer 3.0.0
>File Installer 1.0.0
>
>I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
>https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310
>710&fixfor=12314354
>
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-039/
>
>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 039 /tmp/sling-staging
>
>Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
>This vote will be open for 72 hours.
>
>Carsten
>--
>Carsten Ziegeler
>cziege...@apache.org

[jira] Commented: (SLING-1739) Update Commons Log exported SLF4J version

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-1739:
--

So can we then resolve this with just upgrading the exported SLF4J API and 
without the spi and helpers export ?

> Update Commons Log exported SLF4J version
> -
>
> Key: SLING-1739
> URL: https://issues.apache.org/jira/browse/SLING-1739
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Log 2.0.6
>Reporter: Jason Rose
>Assignee: Felix Meschberger
>Priority: Minor
> Fix For: Commons Log 2.0.8
>
> Attachments: commons-log.patch
>
>
> Commons Log is currently exporting version 1.5.2 of SLF4j.  This is a very 
> old version of the library.  I'm currently using Commons Logging as a 
> replacement for PAX Logging because of classloading issues with PAX in JBoss, 
> and I needed to make a couple changes to facilitate that.
> Updating the dependency and exported versions of SLF4j fixes most of the 
> issues I have with trying to exclusively use Commons Log.  In addition to 
> updating the version, I've moved the spi and helpers packages into the 
> exported packages instead of private packages.  This makes it mirror PAX more 
> closely and handles all the logging requirements of 3rd party bundles in my 
> application.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is still unstable: sling-trunk-1.6 » Apache Sling OSGi Installer Integration Tests #577

[Apache Hudson Server]

See 

Hudson build is unstable: sling-trunk-1.6 #577

[Apache Hudson Server]

See 

[jira] Commented: (SLING-1778) Symlinks

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-1778:
-

I haven't looked into your patch yet, but what about using a ResourceDecorator 
instead of a provider - this avoids all observation stuff etc. 

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1778) Symlinks

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-1778:


Component/s: JCR

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-1778:


> ...JCR content from the sling:symlinkTarget path is then exposed below the 
> symlink node...

Not sure if I understand this correctly, can you confirm that the use case is 
as follows?

Node /b/bar has property text="one"
Node /b/bar/4/2 has property text="three"
Node /a/foo has property text="two"

Then if /a/foo has sling:simlinkTarget = /b/bar

/a/foo/text is "one"
/a/foo/4/2/text is "three"

Is that correct?





> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Julian Sedding (JIRA)]

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

Julian Sedding commented on SLING-1778:
---

@Carsten
I didn't look into the ResourceDecorator mechanism, so I don't know if the same 
use-case could be implemented that way. But if you have input I'm certainly 
very interested.

@Bertrand
The example you gave is precisely what I had in mind and what the patch 
achieves.

Additionally, extending your example, assume

/a/foo/4 has property text="four"

Then if /a/foo has property sling:overlayable=true (in addition to 
sling:symlinkTarget = /b/bar)
/a/foo/text is "one"
/a/foo/4/text is "four"
/a/foo/4/2/text is "three" 


> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-1778:


Thanks for the clarifcation.

> Then if /a/foo has property sling:overlayable=true 
> (in addition to sling:symlinkTarget = /b/bar) 
> /a/foo/4/text is "four" 

Seems like this could be very confusing...if you really need it, I'd suggest 
making it configurable and turned off by default.

IMO symlinks should mimic what happens in a unixish filesystem: if /a/foo has 
sling:simlinkTarget = /b/bar, I'd like /a/foo and everything under it to be the 
same tree as /b/bar.


> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-1778:
--

Looks interesting to me 

@Carsten: I don't think ResourceDecorator would help here, because this 
functionality really creates a virtual subtree in the resource tree root et the 
symlink resource containing the subtree rooted at the symlink target.

Some comments to the patch:

  * As for the symlink query: I would look for sling:symlinkTarget properties 
and not the node type. The node type is mostly
  interesting for applications/administrators but on an implementation 
level, the property is what we are interested in
  * sling:overlayable: I understand the concept, but: can we come up  with a 
nicer name ? ;-)
  * The ResourceResolver field of the SymlinkManager should be private. Access 
to the field for the SymlinkResourceProvider
  should be possible using a getter method
  * SymlinkResourceProvider.listChildren should probably support non-Symlink 
resources, particularly if the symlink overlay is
  enabled
  * As a convenience it would be usefull to add the rootPath to the 
service.description property of the provider service registration
  * Not sure here: Would it make sense to have the sling:SymlinkResource type 
also extend sling:Resource ?
  * How is the symlink resource accessible ?

Symlink Resource Access: Provided you have a resource /content/symlink with a 
symlink target set to /content/target. Thus accessing /content/symlink would 
actually return you the /content/target resource, which makes perfect sense. 
But: How is the actual /content/symlink resource accessible ? For example, if 
we want to remove the symlink or if we want to retarget the symlink ?

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-1778:
--

... one more thing: for us to be able to use this contribution you should 
upload it with the "Grant license to ASF for inclusion in ASF works" button 
checked. Thanks.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #595

[Apache Hudson Server]

See 


Changes:

[cziegeler] Go back to latest snapshots

--
[...truncated 19 lines...]
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.commons.scheduler/2.2.0/org.apache.sling.commons.scheduler-2.2.0.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.commons.threads/3.0.2/org.apache.sling.commons.threads-3.0.2.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.api:2.1.1-SNAPSHOT: checking 
for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.api/2.1.1-SNAPSHOT/org.apache.sling.api-2.1.1-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.settings/1.0.0/org.apache.sling.settings-1.0.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.auth.core:1.0.3-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.core/1.0.3-SNAPSHOT/org.apache.sling.auth.core-1.0.3-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.engine/2.1.0/org.apache.sling.engine-2.1.0.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.openid/1.0.0/org.apache.sling.auth.openid-1.0.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.auth.form:1.0.1-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.form/1.0.1-SNAPSHOT/org.apache.sling.auth.form-1.0.1-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.selector/1.0.0/org.apache.sling.auth.selector-1.0.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.adapter:2.0.7-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.adapter/2.0.7-SNAPSHOT/org.apache.sling.adapter-2.0.7-SNAPSHOT.jar
 to 

[INFO] snapshot 
org.apache.sling:org.apache.sling.servlets.resolver:2.0.9-SNAPSHOT: checking 
for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.servlets.resolver/2.0.9-SNAPSHOT/org.apache.sling.servlets.resolver-2.0.9-SNAPSHOT.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.servlets.get:2.0.9-SNAPSHOT: 
checking for updates from scala-to

Build failed in Hudson: sling-contrib-1.5 #595

[Apache Hudson Server]

See 

Changes:

[cziegeler] Go back to latest snapshots

--
[...truncated 3444 lines...]
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.core/1.0.3-SNAPSHOT/org.apache.sling.auth.core-1.0.3-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.engine/2.1.0/org.apache.sling.engine-2.1.0.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.openid/1.0.0/org.apache.sling.auth.openid-1.0.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.auth.form:1.0.1-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.form/1.0.1-SNAPSHOT/org.apache.sling.auth.form-1.0.1-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.auth.selector/1.0.0/org.apache.sling.auth.selector-1.0.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.adapter:2.0.7-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.adapter/2.0.7-SNAPSHOT/org.apache.sling.adapter-2.0.7-SNAPSHOT.jar
 to 

[INFO] snapshot 
org.apache.sling:org.apache.sling.servlets.resolver:2.0.9-SNAPSHOT: checking 
for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.servlets.resolver/2.0.9-SNAPSHOT/org.apache.sling.servlets.resolver-2.0.9-SNAPSHOT.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.servlets.get:2.0.9-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.servlets.get/2.0.9-SNAPSHOT/org.apache.sling.servlets.get-2.0.9-SNAPSHOT.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.servlets.post:2.0.5-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.servlets.post/2.0.5-SNAPSHOT/org.apache.sling.servlets.post-2.0.5-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.jcr.contentloader/2.1.0/org.apache.sling.jcr.contentloader-2.1.0.jar
 to 

[INFO] snapshot org.apache.sling:org.apache.sling.jcr.resource:2.0.7-SNAPSHOT: 
checking for updates from scala-tools.org
[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.jcr.resource/2.0.7-SNAPSHOT/org.apache.sling.jcr.resource-2.0.7-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.jcr.ocm/2.0.4-incubator/org.apache.sling.jcr.ocm-2.0.4-incubator.jar
 to 

[jira] Commented: (SLING-1778) Symlinks

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1778:
---

with the exception of "overlayable", don't JCR 2 shareable nodes accomplish the 
same thing and have the advantage that the post servlet will work on all 
members of the shared set?

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1739) Update Commons Log exported SLF4J version

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1739:
---

>So can we then resolve this with just upgrading the exported SLF4J API and 
>without the spi and helpers export ?
I think so

> Update Commons Log exported SLF4J version
> -
>
> Key: SLING-1739
> URL: https://issues.apache.org/jira/browse/SLING-1739
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Log 2.0.6
>Reporter: Jason Rose
>Assignee: Felix Meschberger
>Priority: Minor
> Fix For: Commons Log 2.0.8
>
> Attachments: commons-log.patch
>
>
> Commons Log is currently exporting version 1.5.2 of SLF4j.  This is a very 
> old version of the library.  I'm currently using Commons Logging as a 
> replacement for PAX Logging because of classloading issues with PAX in JBoss, 
> and I needed to make a couple changes to facilitate that.
> Updating the dependency and exported versions of SLF4j fixes most of the 
> issues I have with trying to exclusively use Commons Log.  In addition to 
> updating the version, I've moved the spi and helpers packages into the 
> exported packages instead of private packages.  This makes it mirror PAX more 
> closely and handles all the logging requirements of 3rd party bundles in my 
> application.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1708) contrib/scripting/velocity is missing suitable resourceloader for the JCR

[Olaf Otto (JIRA)]

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

Olaf Otto commented on SLING-1708:
--

Well, this does work, in a sense of including yet another resource, however 
this includes the result of the call to the script. 
#include would insert the unevaluated velocity code and expose all variables 
and macro definitions of the included resource, $sling.include() does not.

> contrib/scripting/velocity is missing suitable resourceloader for the JCR
> -
>
> Key: SLING-1708
> URL: https://issues.apache.org/jira/browse/SLING-1708
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
> Environment: Felix 1.4, Sling 2.0.7, Apache Velocity 1.6.2 
>Reporter: Olaf Otto
> Fix For: Scripting Velocity 2.0.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Affects: Rev. 989119 of 
> https://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/velocity 
> (2.0.0-SNAPSHOT) 
> The velocity resource manager 
> (org.apache.velocity.runtime.resource.ResourceManagerImpl) has, by default, 
> only an org.apache.velocity.runtime.resource.loader.FileResourceLoader 
> instance. This resourceloader cannot load resources JCR resources as it 
> attempts to access the filesystem.
> To reproduce, simply create a .vlt script and add an include directive:
> template1.vlt:
> #include("/path/to/template2.vlt")
> This will fail:
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find 
> resource '/path/to/template2.vlt'
>   at 
> org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:483)
>   at 
> org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:354)
>   at 
> org.apache.velocity.runtime.RuntimeInstance.getContent(RuntimeInstance.java:1445)
>   at 
> org.apache.velocity.runtime.directive.Include.renderOutput(Include.java:229)
>   at 
> org.apache.velocity.runtime.directive.Include.render(Include.java:155)
>   at 
> org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175)
>   at 
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
>   at 
> org.apache.velocity.runtime.RuntimeInstance.render(RuntimeInstance.java:1277)
>   at 
> org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1216)
> A suitable resource loader should be provided to the VelocityEngine instance 
> (perhaps in the VelocityTemplatesScriptEngine).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Justin Edelson]

+1

On 9/16/10 3:48 AM, Carsten Ziegeler wrote:
> Hi,
> 
> as announced it's time for some more releases :)
> 
> Apart from our first releases of
> OSGi Installer 3.0.0
> JCR Installer 3.0.0
> File Installer 1.0.0
> 
> I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314354
> 
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-039/
> 
> 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 039 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Carsten

[jira] Commented: (SLING-1777) Build error: JobEventHandlerTest

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-1777:
-

Andreas, can you please add the output of the surefire tests? 
And what does your "see also" mean?

> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 63.362 sec 
> <<< FAILURE!
> Running org.apache.sling.event.EventUtilTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec
> Results :
> Failed tests: 
>   testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1777) Build error: JobEventHandlerTest

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1777:
---

If we're seeing tests fail on Maven 3.0-beta-3 or 3.0-RC1, but not on Maven 
2.2.1, I think we should get some guidance from the Maven team about what to 
look for.

I'll send maven-dev an email.

> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 63.362 sec 
> <<< FAILURE!
> Running org.apache.sling.event.EventUtilTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec
> Results :
> Failed tests: 
>   testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Julian Sedding (JIRA)]

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

Julian Sedding commented on SLING-1778:
---

Thanks for the feedback so far!

@Bertrand
> Seems like this could be very confusing...if you really need it, I'd suggest 
> making it configurable and turned off by default. 
It is configurable via the sling:overlayable boolean property and the default, 
i.e. if the property is missing, is off.


@Felix
> * As for the symlink query: I would look for sling:symlinkTarget properties
agreed

> * sling:overlayable: I understand the concept, but: can we come up with a 
> nicer name ? ;-) 
Please feel free to suggest something more intuitive ;)

> * The ResourceResolver field of the SymlinkManager should be private. Access 
> to the field for the SymlinkResourceProvider
>  should be possible using a getter method 
Yes, that should be private. I think it is not used by SymlinkResourceProvider 
at all.

>  * SymlinkResourceProvider.listChildren should probably support non-Symlink 
> resources, particularly if the symlink overlay is
>  enabled 
Yes, I was thinking about this. I don't think it's trivial, as the 
ResourceResolver might go into a recursion. That's the reason I'm using the JCR 
API in places. An option might be to directly query other ResourceProviders.

> * As a convenience it would be usefull to add the rootPath to the 
> service.description property of the provider service registration
Purely for information? Yes, makes sense. A web console plugin might also be 
useful. I was also playing with the thought of exposing SymlinkManager as a 
service and provide an API to e.g. list registered symlinks.

> * Not sure here: Would it make sense to have the sling:SymlinkResource type 
> also extend sling:Resource ?
Not sure either, probably won't hurt. What's the use of slingResource btw?

> * How is the symlink resource accessible ? 
I used CRXDE lite for testing, which works via the Jackrabbit davx servlet. 
Therefore I don't know. Is the POST servlet purely JCR based? If that's the 
case, at least modifications would be possible. It seems, however, that a 
solution is needed to also view the symlink definition. Ideas welcome :)

> ... one more thing: for us to be able to use this contribution you should 
> upload it with the "Grant license to ASF for inclusion in ASF works" button 
> checked. Thanks. 
That's a mistake, I meant to check this of course.


@Justin
I agree that shareable nodes could be an alternative way to explore this. 
However, the use-case I need to cover is creating a language tree in a WCM 
scenario, which can be gradually overlayed with translated pages. So the "with 
exception of overlayable" would have hurt.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1778) Symlinks

[Julian Sedding (JIRA)]

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

Julian Sedding updated SLING-1778:
--

Attachment: (was: symlinks.patch)

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1778) Symlinks

[Julian Sedding (JIRA)]

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

Julian Sedding updated SLING-1778:
--

Attachment: symlinks.patch

Re-attached and granted license to ASF.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1778:
---

> However, the use-case I need to cover is creating a language tree in a WCM 
> scenario, which can be gradually overlayed with translated 
> pages

Just thinking out loud here, but how about *only* supporting overlays. I can 
see how overlays and symlinks are related, but they actually seems like 
different use cases.


> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Vidar Ramdal]

On Thu, Sep 16, 2010 at 9:48 AM, Carsten Ziegeler  wrote:
> Hi,
>
> as announced it's time for some more releases :)
>
> Apart from our first releases of
> OSGi Installer 3.0.0
> JCR Installer 3.0.0
> File Installer 1.0.0
>
> I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314354
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-039/
>
> 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 039 /tmp/sling-staging

Don't know if this is just me, but I'm getting reports on bad
signatures for all artifacts:


  CHECK SIGNATURES AND DIGESTS

sling-staging/039/.index/nexus-maven-repository-index.gz
gpg:  
md5:  BAD
sha1: BAD
sling-staging/039/.index/nexus-maven-repository-index.properties
gpg:  
md5:  BAD
sha1: BAD
sling-staging/039/.meta/p2-metadata.properties
gpg:  
md5:  
sha1: 
sling-staging/039/.meta/repository-metadata.xml
gpg:  
md5:  
sha1: 
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-javadoc.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-source-release.zip
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-sources.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6.pom
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/maven-metadata.xml
gpg:  
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0-source-release.zip
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0-sources.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0.pom
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/maven-metadata.xml
gpg:  
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0-source-release.zip
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0-sources.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0.pom
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/maven-metadata.xml
gpg:  
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-javadoc.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-source-release.zip
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-sources.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0.jar
gpg:  BAD
md5:  BAD
sha1: BAD
sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0.pom
gpg:  BAD
md5:  BAD
sha1: BAD

[jira] Commented: (SLING-1778) Symlinks

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-1778:


> Just thinking out loud here, but how about *only* supporting overlays. I can 
> see how 
> overlays and symlinks are related, but they actually seems like different use 
> cases. 

I like that.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

RE: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Stefan Seifert]

>Don't know if this is just me, but I'm getting reports on bad
>signatures for all artifacts:

i've tested it on a linux machine and got GOOD results for the md5 and sha1 
hashes, BAD only for pgp
(although i've scanned the results only briefly and deleted them already)

stefan

[jira] Commented: (SLING-1778) Symlinks

[Julian Sedding (JIRA)]

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

Julian Sedding commented on SLING-1778:
---

> Just thinking out loud here, but how about *only* supporting overlays. I can 
> see how
> overlays and symlinks are related, but they actually seems like different use 
> cases. 

Ok, that could be easily done. What about the following: if we think of the 
tree we want to overlay as the "shadow"-tree (again, I'm open for better 
names), we could define a property "sling:shadow" (or sling:shadowPath, 
sling:shadowRoot?). "sling:shadow" would contain a string value, the root path 
of the "shadow"-tree.

You suggest *only* supporting overlays. Would you drop the symlink use-case 
entirely, implement it using shareable nodes or support it via a sling:symlink 
(aka sling:symlinkTarget, playing the names-game again) property? Supporting 
the last use-case would be trivial, however, it might be confusing.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-1778:


I suggest sling:overlayPath for the property name.

As for symlinks, I'd consider this a distinct problem, and if needed create a 
distinct component to handle them. I think that's what Justin meant.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1778) Symlinks

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1778:
---

>> Just thinking out loud here, but how about *only* supporting overlays. I can 
>> see how 
>> overlays and symlinks are related, but they actually seems like different 
>> use cases. 
>
>Ok, that could be easily done. What about the following: if we think of the 
>tree we want to overlay as the "shadow"-tree (again, I'm open for >better 
>names), we could define a property "sling:shadow" (or sling:shadowPath, 
>sling:shadowRoot?). "sling:shadow" would contain a string >value, the root 
>path of the "shadow"-tree. 
I liked "overlay" :)

Any reason you couldn't have this be a multivalued property?

> You suggest *only* supporting overlays. Would you drop the symlink use-case 
> entirely, implement it using shareable nodes or support it via 
> a sling:symlink (aka sling:symlinkTarget, playing the names-game again) 
> property? Supporting the last use-case would be trivial, however, it 
> might be confusing.
I would say drop it entirely. It can be done with shareable nodes and it sounds 
like you don't need it. If someone needs it in the future, we can revisit.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SLING-1780) check_staged_release.sh gives BAD md5/sha1 on macosx

[Bertrand Delacretaz (JIRA)]

check_staged_release.sh gives BAD md5/sha1 on macosx


 Key: SLING-1780
 URL: https://issues.apache.org/jira/browse/SLING-1780
 Project: Sling
  Issue Type: Bug
Reporter: Bertrand Delacretaz
Assignee: Bertrand Delacretaz
Priority: Minor


With the 039 staged release on my fully updated macosx 10.6.4 system I get BAD 
md5/sha1 as openssl adds (stdin) to its output:

$ cat org.apache.sling.install.fileinstall-1.0.0.jar.md5  ; echo
d903fcea9bf63e8f463b87d837bea540

$ openssl md5 < org.apache.sling.install.fileinstall-1.0.0.jar
(stdin)= d903fcea9bf63e8f463b87d837bea540



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1780) check_staged_release.sh gives BAD md5/sha1 on macosx

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-1780:


Refactored the script in revision 997819, also displays the digests if they 
differ:

gpg:  GOOD

md5 : BAD!! : b4d1e4b7d4f80d990320e48f186ace79 not equal to (stdin)= 
b4d1e4b7d4f80d990320e48f186ace79

sha1 : BAD!! : 236278d6ee804a04ec4df37beaed0aebc1d99077 not equal to (stdin)= 
236278d6ee804a04ec4df37beaed0aebc1d99077

Bugfix in next revision...

> check_staged_release.sh gives BAD md5/sha1 on macosx
> 
>
> Key: SLING-1780
> URL: https://issues.apache.org/jira/browse/SLING-1780
> Project: Sling
>  Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> With the 039 staged release on my fully updated macosx 10.6.4 system I get 
> BAD md5/sha1 as openssl adds (stdin) to its output:
> $ cat org.apache.sling.install.fileinstall-1.0.0.jar.md5  ; echo
> d903fcea9bf63e8f463b87d837bea540
> $ openssl md5 < org.apache.sling.install.fileinstall-1.0.0.jar
> (stdin)= d903fcea9bf63e8f463b87d837bea540

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SLING-1780) check_staged_release.sh gives BAD md5/sha1 on macosx

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz resolved SLING-1780.


Resolution: Fixed

Added a sed filter to remove everything before = sign in openssl output, 
revision 997821

> check_staged_release.sh gives BAD md5/sha1 on macosx
> 
>
> Key: SLING-1780
> URL: https://issues.apache.org/jira/browse/SLING-1780
> Project: Sling
>  Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> With the 039 staged release on my fully updated macosx 10.6.4 system I get 
> BAD md5/sha1 as openssl adds (stdin) to its output:
> $ cat org.apache.sling.install.fileinstall-1.0.0.jar.md5  ; echo
> d903fcea9bf63e8f463b87d837bea540
> $ openssl md5 < org.apache.sling.install.fileinstall-1.0.0.jar
> (stdin)= d903fcea9bf63e8f463b87d837bea540

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

SLING-1780 - please re-test the check_staged_release.sh script on your platforms

[Bertrand Delacretaz]

Hi,

Could people who use it please test the changes I just committed to
the check_staged_release.sh script?

For example
sh check_staged_release.sh 039 /tmp/sling-staging

I *think* my changes should work on all platforms but that's just theory ;-)

Thanks,
-Bertrand

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Bertrand Delacretaz]

On Thu, Sep 16, 2010 at 5:27 PM, Vidar Ramdal  wrote:
>...
> 
>                          CHECK SIGNATURES AND DIGESTS
> 
> sling-staging/039/.index/nexus-maven-repository-index.gz
> gpg:  
> md5:  BAD
> sha1: BAD

Should be SLING-1780, can you svn up and try again?

-Bertrand

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Bertrand Delacretaz]

On Thu, Sep 16, 2010 at 9:48 AM, Carsten Ziegeler  wrote:
> ...Apart from our first releases of
> OSGi Installer 3.0.0
> JCR Installer 3.0.0
> File Installer 1.0.0
>
> I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314354...

+1 to the release.

Checked sigs and md5, and briefly tested OSGi Installer 3.0.0 and JCR
Installer 3.0.0 on a complex $work project, looks good!

-Bertrand

Re: SLING-1780 - please re-test the check_staged_release.sh script on your platforms

[Justin Edelson]

Fails for me:

/tmp/sling-staging/039/Sonatype-content.css?1.7.1
gpg:  
md5 : BAD!! :  not equal to 3f8dbd531e30872d5ff79d00ddace3bd
sha1 : BAD!! :  not equal to 4ceff0a69b18dafd5ea1fb9b7a534472594e41c8

OS X 10.6.4


On 9/16/10 12:22 PM, Bertrand Delacretaz wrote:
> Hi,
> 
> Could people who use it please test the changes I just committed to
> the check_staged_release.sh script?
> 
> For example
> sh check_staged_release.sh 039 /tmp/sling-staging
> 
> I *think* my changes should work on all platforms but that's just theory ;-)
> 
> Thanks,
> -Bertrand

Re: SLING-1780 - please re-test the check_staged_release.sh script on your platforms

[Bertrand Delacretaz]

On Thu, Sep 16, 2010 at 6:35 PM, Justin Edelson  wrote:
> Fails for me:
>
> /tmp/sling-staging/039/Sonatype-content.css?1.7.1
> gpg:  
> md5 : BAD!! :  not equal to 3f8dbd531e30872d5ff79d00ddace3bd
> sha1 : BAD!! :  not equal to 4ceff0a69b18dafd5ea1fb9b7a534472594e41c8
>
> OS X 10.6.4

Ah yes, missed that. Can you try again? You should now get

/tmp/sling-staging/039/Sonatype-content.css?1.7.1
gpg:  
md5 : 
sha1 : 

-Bertrand

[jira] Updated: (SLING-1438) GSoC 2010: create a mini-CMS to demonstrate Sling

[Federico Paparoni (JIRA)]

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

Federico Paparoni updated SLING-1438:
-

Attachment: david16092010.zip

Updated version with documentation provided as initial content.

> GSoC 2010: create a mini-CMS to demonstrate Sling
> -
>
> Key: SLING-1438
> URL: https://issues.apache.org/jira/browse/SLING-1438
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Reporter: Bertrand Delacretaz
>Assignee: Federico Paparoni
> Attachments: david.rar, david16092010.zip
>
>
> This is a suggested project for Google Summer of Code 2010.
> The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
> practices.
> The emphasis is on the quality and readability of the demo code, and we 
> expect to have to go through several iterations to refine it and the 
> corresponding JCR content model so that they demonstrate Sling best 
> practices. We will not necessarily create a full-fledged CMS, the goal is for 
> the result to be educational and help Sling newcomers understand how to 
> create web applications with it.
> Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
> server-side scripting, and Java code in OSGi bundles for back-end 
> functionality.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: SLING-1780 - please re-test the check_staged_release.sh script on your platforms

[Felix Meschberger]

Hi

Confirmed on Ubuntu 10.04

Regards
Felix

Am 16.09.2010 18:22, schrieb Bertrand Delacretaz:
> Hi,
> 
> Could people who use it please test the changes I just committed to
> the check_staged_release.sh script?
> 
> For example
> sh check_staged_release.sh 039 /tmp/sling-staging
> 
> I *think* my changes should work on all platforms but that's just theory ;-)
> 
> Thanks,
> -Bertrand
> 

Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0

[Felix Meschberger]

+1

What sounds a bit odd, though, is the bundle symbolic names:

  org.apache.sling.jcr.jcrinstall
  org.apache.sling.osgi.installer
  org.apache.sling.install.fileinstall

Sounds like they have something in common, but not really much ...

Wouldn't it make sense to have some concise naming convention for this ?

For example

  org.apache.sling.install.core (today: ...osgi.installer)
  org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall)
  org.apache.sling.install.provider.file (today: ...install.fileinstall)

WDYT ?

Regards
Felix

Am 16.09.2010 09:48, schrieb Carsten Ziegeler:
> Hi,
> 
> as announced it's time for some more releases :)
> 
> Apart from our first releases of
> OSGi Installer 3.0.0
> JCR Installer 3.0.0
> File Installer 1.0.0
> 
> I've added Commons Testing 2.0.6 (which is a dep of jcr installer)
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314354
> 
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-039/
> 
> 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 039 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Carsten

Hudson build is still unstable: sling-trunk-1.5 » Apache Sling OSGi Installer Integration Tests #889

[Apache Hudson Server]

See 

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

[Apache Hudson Server]

See 

[jira] Resolved: (SLING-1781) bad String equality check in jcr.resource

[Justin Edelson (JIRA)]

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

Justin Edelson resolved SLING-1781.
---

Resolution: Fixed

> bad String equality check in jcr.resource
> -
>
> Key: SLING-1781
> URL: https://issues.apache.org/jira/browse/SLING-1781
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> in a few locations in jcr.resource == is used to test for String equality. 
> This is bad.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SLING-1781) bad String equality check in jcr.resource

[Justin Edelson (JIRA)]

bad String equality check in jcr.resource
-

 Key: SLING-1781
 URL: https://issues.apache.org/jira/browse/SLING-1781
 Project: Sling
  Issue Type: Bug
  Components: JCR
Reporter: Justin Edelson
Assignee: Justin Edelson
 Fix For: JCR Resource 2.0.8


in a few locations in jcr.resource == is used to test for String equality. This 
is bad.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1781) bad String equality check in jcr.resource

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-1781:
---

fixed in r997904

> bad String equality check in jcr.resource
> -
>
> Key: SLING-1781
> URL: https://issues.apache.org/jira/browse/SLING-1781
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> in a few locations in jcr.resource == is used to test for String equality. 
> This is bad.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r997904 - in /sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper: jcr/JcrNodeResource.java starresource/StarResource.java

[Felix Meschberger]

Hi Justin,

These have been done like this by intent: The constant is set during
object creation as a special value to indicate that the super type has
not be calculated yet. As such it is kind of a special "null" value.

The reason for not using "null" in this case is, that "null" is in fact
a valid value for a calculated super type as is any string happening to
be "equal" to UNSET_RESOURCE_SUPER_TYPE.

The only supertype value impossible to set is the exact object reference
of UNSET_RESOURCE_SUPER_TYPE (unless the value is interned, but then ...)

Regards
Felix

Am 16.09.2010 22:06, schrieb jus...@apache.org:
> Author: justin
> Date: Thu Sep 16 20:06:20 2010
> New Revision: 997904
> 
> URL: http://svn.apache.org/viewvc?rev=997904&view=rev
> Log:
> SLING-1781 - fixing String equality check
> 
> Modified:
> 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
> 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
> 
> Modified: 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
> URL: 
> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java?rev=997904&r1=997903&r2=997904&view=diff
> ==
> --- 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>  (original)
> +++ 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>  Thu Sep 16 20:06:20 2010
> @@ -93,7 +93,7 @@ class JcrNodeResource extends JcrItemRes
>  }
>  
>  public String getResourceSuperType() {
> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>  try {
>  if 
> (node.hasProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY)) {
>  resourceSuperType = 
> node.getProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY).getValue().getString();
> @@ -101,7 +101,7 @@ class JcrNodeResource extends JcrItemRes
>  } catch (RepositoryException re) {
>  // we ignore this
>  }
> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>  resourceSuperType = null;
>  }
>  }
> 
> Modified: 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
> URL: 
> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java?rev=997904&r1=997903&r2=997904&view=diff
> ==
> --- 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>  (original)
> +++ 
> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>  Thu Sep 16 20:06:20 2010
> @@ -69,7 +69,7 @@ public class StarResource extends Synthe
>   * to dynamically resolve the resource super type of this star resource.
>   */
>  public String getResourceSuperType() {
> -if (resourceSuperType == UNSET_RESOURCE_SUPER_TYPE) {
> +if (UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType)) {
>  resourceSuperType = 
> ResourceUtil.getResourceSuperType(this.getResourceResolver(),
>  this.getResourceType());
>  }
> 
> 
> 

[jira] Reopened: (SLING-1781) bad String equality check in jcr.resource

[Justin Edelson (JIRA)]

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

Justin Edelson reopened SLING-1781:
---


> bad String equality check in jcr.resource
> -
>
> Key: SLING-1781
> URL: https://issues.apache.org/jira/browse/SLING-1781
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> in a few locations in jcr.resource == is used to test for String equality. 
> This is bad.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SLING-1781) bad String equality check in jcr.resource

[Justin Edelson (JIRA)]

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

Justin Edelson resolved SLING-1781.
---

Resolution: Invalid

reverted. this was done intentionally

> bad String equality check in jcr.resource
> -
>
> Key: SLING-1781
> URL: https://issues.apache.org/jira/browse/SLING-1781
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: JCR Resource 2.0.8
>
>
> in a few locations in jcr.resource == is used to test for String equality. 
> This is bad.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r997904 - in /sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper: jcr/JcrNodeResource.java starresource/StarResource.java

[Justin Edelson]

OK. I reverted and added a comment.

Justin

On 9/16/10 4:20 PM, Felix Meschberger wrote:
> Hi Justin,
> 
> These have been done like this by intent: The constant is set during
> object creation as a special value to indicate that the super type has
> not be calculated yet. As such it is kind of a special "null" value.
> 
> The reason for not using "null" in this case is, that "null" is in fact
> a valid value for a calculated super type as is any string happening to
> be "equal" to UNSET_RESOURCE_SUPER_TYPE.
> 
> The only supertype value impossible to set is the exact object reference
> of UNSET_RESOURCE_SUPER_TYPE (unless the value is interned, but then ...)
> 
> Regards
> Felix
> 
> Am 16.09.2010 22:06, schrieb jus...@apache.org:
>> Author: justin
>> Date: Thu Sep 16 20:06:20 2010
>> New Revision: 997904
>>
>> URL: http://svn.apache.org/viewvc?rev=997904&view=rev
>> Log:
>> SLING-1781 - fixing String equality check
>>
>> Modified:
>> 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>> 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>
>> Modified: 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>> URL: 
>> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java?rev=997904&r1=997903&r2=997904&view=diff
>> ==
>> --- 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>  (original)
>> +++ 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>  Thu Sep 16 20:06:20 2010
>> @@ -93,7 +93,7 @@ class JcrNodeResource extends JcrItemRes
>>  }
>>  
>>  public String getResourceSuperType() {
>> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
>> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>>  try {
>>  if 
>> (node.hasProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY)) {
>>  resourceSuperType = 
>> node.getProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY).getValue().getString();
>> @@ -101,7 +101,7 @@ class JcrNodeResource extends JcrItemRes
>>  } catch (RepositoryException re) {
>>  // we ignore this
>>  }
>> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
>> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>>  resourceSuperType = null;
>>  }
>>  }
>>
>> Modified: 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>> URL: 
>> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java?rev=997904&r1=997903&r2=997904&view=diff
>> ==
>> --- 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>  (original)
>> +++ 
>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>  Thu Sep 16 20:06:20 2010
>> @@ -69,7 +69,7 @@ public class StarResource extends Synthe
>>   * to dynamically resolve the resource super type of this star resource.
>>   */
>>  public String getResourceSuperType() {
>> -if (resourceSuperType == UNSET_RESOURCE_SUPER_TYPE) {
>> +if (UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType)) {
>>  resourceSuperType = 
>> ResourceUtil.getResourceSuperType(this.getResourceResolver(),
>>  this.getResourceType());
>>  }
>>
>>
>>

Re: svn commit: r997904 - in /sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper: jcr/JcrNodeResource.java starresource/StarResource.java

[Felix Meschberger]

Thanks. Regards
Felix

Am 16.09.2010 22:32, schrieb Justin Edelson:
> OK. I reverted and added a comment.
> 
> Justin
> 
> On 9/16/10 4:20 PM, Felix Meschberger wrote:
>> Hi Justin,
>>
>> These have been done like this by intent: The constant is set during
>> object creation as a special value to indicate that the super type has
>> not be calculated yet. As such it is kind of a special "null" value.
>>
>> The reason for not using "null" in this case is, that "null" is in fact
>> a valid value for a calculated super type as is any string happening to
>> be "equal" to UNSET_RESOURCE_SUPER_TYPE.
>>
>> The only supertype value impossible to set is the exact object reference
>> of UNSET_RESOURCE_SUPER_TYPE (unless the value is interned, but then ...)
>>
>> Regards
>> Felix
>>
>> Am 16.09.2010 22:06, schrieb jus...@apache.org:
>>> Author: justin
>>> Date: Thu Sep 16 20:06:20 2010
>>> New Revision: 997904
>>>
>>> URL: http://svn.apache.org/viewvc?rev=997904&view=rev
>>> Log:
>>> SLING-1781 - fixing String equality check
>>>
>>> Modified:
>>> 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>> 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>>
>>> Modified: 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>> URL: 
>>> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java?rev=997904&r1=997903&r2=997904&view=diff
>>> ==
>>> --- 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>>  (original)
>>> +++ 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrNodeResource.java
>>>  Thu Sep 16 20:06:20 2010
>>> @@ -93,7 +93,7 @@ class JcrNodeResource extends JcrItemRes
>>>  }
>>>  
>>>  public String getResourceSuperType() {
>>> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
>>> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>>>  try {
>>>  if 
>>> (node.hasProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY)) 
>>> {
>>>  resourceSuperType = 
>>> node.getProperty(JcrResourceConstants.SLING_RESOURCE_SUPER_TYPE_PROPERTY).getValue().getString();
>>> @@ -101,7 +101,7 @@ class JcrNodeResource extends JcrItemRes
>>>  } catch (RepositoryException re) {
>>>  // we ignore this
>>>  }
>>> -if ( resourceSuperType == UNSET_RESOURCE_SUPER_TYPE ) {
>>> +if ( UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType) ) {
>>>  resourceSuperType = null;
>>>  }
>>>  }
>>>
>>> Modified: 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>> URL: 
>>> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java?rev=997904&r1=997903&r2=997904&view=diff
>>> ==
>>> --- 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>>  (original)
>>> +++ 
>>> sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/starresource/StarResource.java
>>>  Thu Sep 16 20:06:20 2010
>>> @@ -69,7 +69,7 @@ public class StarResource extends Synthe
>>>   * to dynamically resolve the resource super type of this star 
>>> resource.
>>>   */
>>>  public String getResourceSuperType() {
>>> -if (resourceSuperType == UNSET_RESOURCE_SUPER_TYPE) {
>>> +if (UNSET_RESOURCE_SUPER_TYPE.equals(resourceSuperType)) {
>>>  resourceSuperType = 
>>> ResourceUtil.getResourceSuperType(this.getResourceResolver(),
>>>  this.getResourceType());
>>>  }
>>>
>>>
>>>
> 
> 

[jira] Commented: (SLING-1777) Build error: JobEventHandlerTest

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz commented on SLING-1777:
-

I used and use Apache Maven 2.2.1 (rdebian-4).

I am currently  trying to build revision 997835 (which takes a lng time) 
and will report the result when that ends.

> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 63.362 sec 
> <<< FAILURE!
> Running org.apache.sling.event.EventUtilTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec
> Results :
> Failed tests: 
>   testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1228) Launchpad Contrib Testing: Sling cannot start

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz commented on SLING-1228:
-

Why is this issue still open?


> Launchpad Contrib Testing: Sling cannot start
> -
>
> Key: SLING-1228
> URL: https://issues.apache.org/jira/browse/SLING-1228
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Michael Dürig
>
> Currently all tests fail since Sling cannot start: 
> org.osgi.framework.BundleException: sling.home property is missing, cannot 
> start
>   at 
> org.apache.sling.launchpad.base.impl.Sling.loadConfigProperties(Sling.java:388)
>   at org.apache.sling.launchpad.base.impl.Sling.(Sling.java:216)
>   at 
> org.apache.sling.launchpad.base.webapp.SlingBridge.(SlingBridge.java:41)
> See 
> http://hudson.zones.apache.org/hudson/view/Sling/job/sling-contrib-1.5/276/consoleFull

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (SLING-1777) Build error: JobEventHandlerTest

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz edited comment on SLING-1777 at 9/16/10 5:08 PM:
--

I used and use Apache Maven 2.2.1 (rdebian-4).

I am currently  trying to build revision 997835 (which takes a loong 
time) and will report the result when that ends.

  was (Author: akuckartz):
I used and use Apache Maven 2.2.1 (rdebian-4).

I am currently  trying to build revision 997835 (which takes a lng time) 
and will report the result when that ends.
  
> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 63.362 sec 
> <<< FAILURE!
> Running org.apache.sling.event.EventUtilTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec
> Results :
> Failed tests: 
>   testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)
> Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SLING-1782) Build error: tests take a loooooooooong time

[Andreas Kuckartz (JIRA)]

Build error: tests take a loong time


 Key: SLING-1782
 URL: https://issues.apache.org/jira/browse/SLING-1782
 Project: Sling
  Issue Type: Bug
Reporter: Andreas Kuckartz


Building revision 997835 takes a loong time. I stopped that after the 
integration tests had run longer than half an hour and there werde some 
problems as one can see in the log.

I did not find any more information in 
sling/launchpad/testing/target/surefire-reports, but there were a small number 
of warnings "[main] HttpMethodBase.java:682   Going to buffer response 
body of large or unknown size. Using getResponseBodyAsStream instead is 
recommended."

---
Running org.apache.sling.launchpad.testing.TestAll
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
Checking if the required Sling services are started (timeout 62 seconds)...
(base URLs=http://localhost:43374 and http://localhost:43374)
Sling services seem to be started, continuing with integration tests.
JSP script engine configured using serverscripts/jsp-engine-setup.jsp
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
Tests run: 6, Failures: 5, Errors: 1, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.SyntheticResourceTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateGroupTest
Tests run: 3, Failures: 3, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.ExtensionServletTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (SLING-1782) Build error: tests take a loooooooooong time

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-1782:
--

What are your heap and PermGen sizes ? It might be that your GC is taken over 
the reign ;-)

> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
> Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
> Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
> Tests run: 6, Failures: 5, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.SyntheticResourceTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.w

[jira] Issue Comment Edited: (SLING-1782) Build error: tests take a loooooooooong time

[Felix Meschberger (JIRA)]

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

Felix Meschberger edited comment on SLING-1782 at 9/16/10 5:28 PM:
---

What are your heap and PermGen sizes ? It might be that your GC is taken over 
the reign ;-)
Also you need more memory if your on a 64bit system

  was (Author: fmeschbe):
What are your heap and PermGen sizes ? It might be that your GC is taken 
over the reign ;-)
  
> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
> Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
> Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTe

Hudson build is back to normal : sling-samples-1.5 #172

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trunk-1.6 » Apache Sling OSGi Installer Integration Tests #578

[Apache Hudson Server]

See 

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

[Apache Hudson Server]

See 

[jira] Commented: (SLING-1782) Build error: tests take a loooooooooong time

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz commented on SLING-1782:
-

Yes, PermSize is a problem. Unfortunately the build did not abort and the info 
on that problem ("java.lang.OutOfMemoryError: PermGen space") was hidden in 
org.apache.sling.launchpad.testing.TestAll.txt

I now changed PermSize from 128M to 256M. The documentation should be modified 
as well (http://sling.apache.org/site/getting-and-building-sling.html).

But it turns out that this did not solve the problem. Fortunately the problem 
now is logged normally:

Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.ModifyAceTest
ERROR: EventDispatcher: Error during dispatch. (java.lang.OutOfMemoryError: 
PermGen space)
java.lang.OutOfMemoryError: PermGen space
ERROR: EventDispatcher: Error during dispatch. (java.lang.OutOfMemoryError: 
PermGen space)
java.lang.OutOfMemoryError: PermGen space

I will try again with PermSize 512M. But it is strange that the PermSize 
requirements multiplied within a few days ...


> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integr

[jira] Commented: (SLING-1777) Build error: JobEventHandlerTest

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz commented on SLING-1777:
-

sling/bundles/extensions/event/target/surefire-reports/org.apache.sling.event.impl.JobEventHandlerTest.txt
 says this:

---
Test set: org.apache.sling.event.impl.JobEventHandlerTest
---
Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 57.544 sec <<< 
FAILURE!
testCancelJob(org.apache.sling.event.impl.JobEventHandlerTest)  Time elapsed: 
2.777 sec  <<< FAILURE!
java.lang.AssertionError:
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertFalse(Assert.java:68)
at org.junit.Assert.assertFalse(Assert.java:79)
at 
org.apache.sling.event.impl.JobEventHandlerTest.testCancelJob(JobEventHandlerTest.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:66)
at org.jmock.integration.junit4.JMock$1.invoke(JMock.java:37)
at 
org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:105)
at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:86)
at 
org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:94)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:84)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
at 
org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:98)
at 
org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:61)
at 
org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:54)
at 
org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
at 
org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
at 
org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:52)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)


> Build error: JobEventHandlerTest
> 
>
> Key: SLING-1777
> URL: https://issues.apache.org/jira/browse/SLING-1777
> Project: Sling
>  Issue Type: Bug
> Environment: Debian Linux
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>Reporter: Andreas Kuckartz
>Priority: Critical
>
> From the build log for revision 997371:
> 112735 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> opened
> 112953 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 112956 [Thread-136] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 112957 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 113286 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session opened
> 113288 [Thread-142] INFO org.apache.sling.event.impl.JobEventHandler - Apache 
> Sling Job Event Handler started on instance 4711
> 115288 [Thread-141] INFO org.apache.jackrabbit.core.TransientRepository - 
> Session closed
> 115290 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> 115292 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
> closed
> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Ti

[jira] Commented: (SLING-1782) Build error: tests take a loooooooooong time

[Andreas Kuckartz (JIRA)]

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

Andreas Kuckartz commented on SLING-1782:
-

PermSize 512 solved this problem (so that I can now see a different problem).

This issue can be closed when the PermSize requirement (PermSize 512M for 64 
bit Linux) has been added to the Gettin and Building Sling page.



> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
> Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
> Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
> Tests run: 6, Failures: 5, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.i

[jira] Assigned: (SLING-1782) Build error: tests take a loooooooooong time

[Felix Meschberger (JIRA)]

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

Felix Meschberger reassigned SLING-1782:


Assignee: Felix Meschberger

> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>Assignee: Felix Meschberger
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
> Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
> Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
> Tests run: 6, Failures: 5, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.SyntheticResourceTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateGroupTest
> Tests run: 3, Fail

[jira] Resolved: (SLING-1782) Build error: tests take a loooooooooong time

[Felix Meschberger (JIRA)]

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

Felix Meschberger resolved SLING-1782.
--

Resolution: Fixed

Ammended the MAVEN_OPTS recommendation output generated during the build in the 
parent POM in Rev. 997987. (This will show up, once we release the parent POM 
and refer to it from the projects).

Also updated the recommendations on the Getting and Building Page.

> Build error: tests take a loong time
> 
>
> Key: SLING-1782
> URL: https://issues.apache.org/jira/browse/SLING-1782
> Project: Sling
>  Issue Type: Bug
>Reporter: Andreas Kuckartz
>Assignee: Felix Meschberger
>
> Building revision 997835 takes a loong time. I stopped that after the 
> integration tests had run longer than half an hour and there werde some 
> problems as one can see in the log.
> I did not find any more information in 
> sling/launchpad/testing/target/surefire-reports, but there were a small 
> number of warnings "[main] HttpMethodBase.java:682   Going to buffer 
> response body of large or unknown size. Using getResponseBodyAsStream instead 
> is recommended."
> ---
> Running org.apache.sling.launchpad.testing.TestAll
> Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
> Checking if the required Sling services are started (timeout 62 seconds)...
> (base URLs=http://localhost:43374 and http://localhost:43374)
> Sling services seem to be started, continuing with integration tests.
> JSP script engine configured using serverscripts/jsp-engine-setup.jsp
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
> Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest
> Tests run: 4, Failures: 1, Errors: 3, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
> Tests run: 5, Failures: 5, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
> Tests run: 9, Failures: 0, Errors: 9, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0
> Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest
> Tests run: 4, Failures: 4, Errors: 0, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
> Tests run: 12, Failures: 2, Errors: 10, Skipped: 0
> Running 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
> Tests run: 6, Failures: 5, Errors: 1, Skipped

Welcome Clemens Wyss

[Felix Meschberger]

Hi all,

I want to let you know that the Apache Sling PMC decided to invite
Clemens Wyss as a committer to the Apache Sling project based on his
work on the JCR Explorer; an invitation which Clemens accepted. Thanks.

Please join me in welcoming Clemens Wyss as a new committer !

Keep up the good work, Clemens, and thanks for your contributions. And
feel free to briefly introduce yourself if you want ;-)

Regards
Felix

[REPORT] Sling Board report - September 2010

[Felix Meschberger]

Sling is an OSGI-based scriptable web framework that uses a Java Content
Repository, such as Apache Jackrabbit, to store and manage content.

Sling graduated as a TLP on June 17th, 2009.

There are no issues which require board attention at the moment.

Community

* This period showed strong activity towards the release of the Sling 6
  distributable. This shows in a number of bugs being fixed and new
  functionality being added.
* Added Justin Edelson to the PMC (2010/08/26)
* Federico Paparoni successfully completed his GSoC project, creating a
  mini-CMS that will be useful as a substantial example application.
* Added Clemens Wyss as a committer (2010/09/17)

Releases

* 2010/08/03 Adapter Manager 2.0.6, Engine 2.1.0, Settings 1.0.0
* 2010/08/21 Sling API 2.1.0
* 2010/08/25 Web Console Branding 1.0.0,
 Web Console Security Provider 1.0.0
* 2010/08/27 Authentication Core 1.0.0, Authentication Form 1.0.0,
 Authentication OpenID 1.0.0, Authentication Selector 1.0.0
* 2010/08/27 Authentication Core 1.0.2
* 2010/08/30 Commons ClassLoader 1.2.0, JCR ClassLoader 3.1.2
* 2010/09/06 Eventing 2.4.0, Commons Threads 3.0.2
* 2010/09/10 JCR API, JCR Base, JCR Content Loader, and
 Jackrabbit Server 2.1.0

Documentation

* Added two non-committer documentation contributors (Jean-Christophe
  Kautzmann and Alison Heimoz)
* Website documentation is steadily improving including the creation of
  targeted templates like
  http://sling.apache.org/site/how-to-manage-events-in-sling.html

Licensing and other issues

* none

Regard
Felix