Re: Jenkins build is still unstable: sling-trunk-1.6 #1329
Hi, yes, you're right. Strange, I'm wondering why I didn't see this yesterday :) The test is failing on my machine as well. Regards Carsten 2012/5/22 Pontus Amberg pontus.amb...@comhem.se: I'm not sure what going on but if you go to https://builds.apache.org/job/sling-trunk-1.6/1329/ you can see that the same test that has been failing for almost a week now is still failing. https://builds.apache.org/job/sling-trunk-1.6/1329/org.apache.sling$org.apache.sling.launchpad.testing/testReport/org.apache.sling.launchpad.webapp.integrationtest.login/RedirectOnLoginErrorTest/testRedirectToOpenIDLoginFormAfterLoginError/ /Pontus On 2012-05-22 19:45, Carsten Ziegeler wrote: According to the web page at: https://builds.apache.org/job/sling-trunk-1.6/1329/console this job succeeded, so why do we get a failed mail? Carsten 2012/5/22 Apache Jenkins Serverjenk...@builds.apache.org: Seehttps://builds.apache.org/job/sling-trunk-1.6/changes -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2483) Update bundle plugin to 2.3.7 and add bndlib
[ https://issues.apache.org/jira/browse/SLING-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281452#comment-13281452 ] Carsten Ziegeler commented on SLING-2483: - Fixed the open id bundle to use more recent versions of jackrabbit to make the test cases pass (Revision 1341774) Update bundle plugin to 2.3.7 and add bndlib Key: SLING-2483 URL: https://issues.apache.org/jira/browse/SLING-2483 Project: Sling Issue Type: Improvement Components: General Affects Versions: Parent 12 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Parent 13 The Sling parent POM currently refers to version 2.0.1 of the bundle plugin which is quite dated. We should update to the latest version 2.3.7 which also includes the latest version of the BND library. In addition we should add the bndlib library to the managed dependencies. This allows for easy use of the BND annotations for declaring exported packages instead of using Export-Package configuration elements in the poms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Sling Site and CMS
Great work, Felix - I like the new layout :)
Carsten
2012/5/22 Felix Meschberger fmesc...@adobe.com:
Hi,
Am 22.05.2012 um 10:59 schrieb Felix Meschberger:
Hi
Thanks for the feedback.
I worked a bit more on the conversion and the rendering.
I have described some supported functionality in the site/trunk/readme.txt
file.
Finally, I started fixing conversion leftovers (like removing duplicate
titles or fixing the bullet points on the bundles page).
Have a look at sling.staging.apache.org. IMHO it looks much better now.
Remaining tasks include:
* Fully recreate subfolder structures with real filesystem folders
* Fix-up all tables (ASF CMS markdown seems to not like tables without
headers)
* Fixup remaining missing things like {note} macros and the like.
Plus: The download page. I imagine we create a special download page template
for this where the source is just a list of artifact names and Maven GAV
entries. The template would read the source and prepare the markup for the
actual download page.
Regards
Felix
Am 21.05.2012 um 14:24 schrieb Ruben Reusser:
also, it seems like the tutorials section is not working due to the URL
http://sling.staging.apache.org/tutorials--how-tos.html
This had a special character conversion issue earlier (as had the pages with
parentheses in the name). I modified the page name to URL conversion and
this should now be fixed:
http://sling.staging.apache.org/tutorials-how-tos.html
Regards
Felix
Ruben
On 5/21/2012 5:05 AM, Bertrand Delacretaz wrote:
Hi Felix,
On Sun, May 20, 2012 at 1:09 AM, Felix Meschbergerfmesc...@adobe.com
wrote:
...Granted we have a few open issues like the confluence to markdown
conversion mangling with the {{}} constructs...
...The rest we can fix over time...
There's still a number of pages where tables and lists are broken and
make the content in unusable in large part:
http://sling.staging.apache.org/dispatching-requests.html
http://sling.staging.apache.org/mappings-for-resource-resolution.html
http://sling.staging.apache.org/bundles.html (no links)
http://sling.staging.apache.org/news.html
I think we should fix those before switching...unfortunately I'm
unable to help right now.
-Bertrand
--
Carsten Ziegeler
cziege...@apache.org
[jira] [Created] (SLING-2492) add documentation on SlingPostServlet's post processor
Nicolas Peltier created SLING-2492: -- Summary: add documentation on SlingPostServlet's post processor Key: SLING-2492 URL: https://issues.apache.org/jira/browse/SLING-2492 Project: Sling Issue Type: Wish Components: Documentation Reporter: Nicolas Peltier Priority: Minor I've started a documentation on https://cwiki.apache.org/confluence/display/SLING/Creating+a+SlingPostServlet+post+processor for integration in http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is back to stable : sling-trunk-1.5 #1662
See https://builds.apache.org/job/sling-trunk-1.5/1662/changes
Jenkins build is back to stable : sling-trunk-1.6 #1330
See https://builds.apache.org/job/sling-trunk-1.6/1330/changes
Build failed in Jenkins: sling-contrib-1.5 #876
See https://builds.apache.org/job/sling-contrib-1.5/876/ -- [...truncated 3293 lines...] [INFO] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ org.apache.sling.scripting.xproc --- mojoSucceeded org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1(default) [INFO] Installing https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/scripting/xproc/target/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.jar mojoStarted org.apache.maven.plugins:maven-install-plugin:2.3.1(default-install)[INFO] Installing https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/scripting/xproc/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/scripting/xproc/target/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.apache.sling.scripting.xproc --- mojoSucceeded org.apache.maven.plugins:maven-install-plugin:2.3.1(default-install) mojoStarted org.apache.felix:maven-bundle-plugin:2.0.1(default-install)[INFO] Local OBR update disabled (enable with -DobrRepository) [INFO] [INFO] --- maven-bundle-plugin:2.0.1:install (default-install) @ org.apache.sling.scripting.xproc --- mojoSucceeded org.apache.felix:maven-bundle-plugin:2.0.1(default-install) projectSucceeded org.apache.sling:org.apache.sling.scripting.xproc:2.0.0-SNAPSHOT projectStarted org.apache.sling:org.apache.sling.launchpad.smx-kernel:2.0.0-SNAPSHOT [INFO] [INFO] Deleting https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/launchpad/smx-kernel/target [INFO] [INFO] Building Apache Sling Features for ServiceMix Kernel 2.0.0-SNAPSHOT [INFO] mojoStarted org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean) [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ org.apache.sling.launchpad.smx-kernel --- mojoSucceeded org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean) mojoStarted org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java) [INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java) @ org.apache.sling.launchpad.smx-kernel --- mojoSucceeded org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java) mojoStarted org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default) [INFO] [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ org.apache.sling.launchpad.smx-kernel --- [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. mojoSucceeded org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default) mojoStarted org.apache.maven.plugins:maven-resources-plugin:2.4.3(filter) [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (filter) @ org.apache.sling.launchpad.smx-kernel --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources mojoSucceeded org.apache.maven.plugins:maven-resources-plugin:2.4.3(filter) mojoStarted org.apache.maven.plugins:maven-antrun-plugin:1.6(default) [INFO] [INFO] --- maven-antrun-plugin:1.6:run (default) @ org.apache.sling.launchpad.smx-kernel --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 mojoSucceeded org.apache.maven.plugins:maven-antrun-plugin:1.6(default) [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks mojoStarted org.codehaus.mojo:animal-sniffer-maven-plugin:1.7(default) [INFO] [INFO] --- animal-sniffer-maven-plugin:1.7:check (default) @ org.apache.sling.launchpad.smx-kernel --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 mojoSucceeded
Build failed in Jenkins: sling-samples-1.5 #325
See https://builds.apache.org/job/sling-samples-1.5/325/ -- [...truncated 1764 lines...] [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default) mojoStarted org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)[INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ org.apache.sling.samples.accessmanager.ui --- [INFO] Copying 14 resources [INFO] Copying 3 resources mojoSucceeded org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources) mojoStarted org.apache.maven.plugins:maven-antrun-plugin:1.6(default)[INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- maven-antrun-plugin:1.6:run (default) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-antrun-plugin:1.6(default) mojoStarted net.alchim31.maven:yuicompressor-maven-plugin:1.3.0(default)[INFO] nothing to do, https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/src/main/resources/js/accessmanager/accessmanager.min.js is younger than original, use 'force' option or clean your target [INFO] nothing to do, https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/src/main/resources/css/accessmanager/accessmanager.min.css is younger than original, use 'force' option or clean your target [INFO] nothing to do, https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/src/main/resources/js/accessmanager/accessmanager.min.js is younger than original, use 'force' option or clean your target [INFO] nothing to do, https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/src/main/resources/css/accessmanager/accessmanager.min.css is younger than original, use 'force' option or clean your target [INFO] nb warnings: 0, nb errors: 0 [INFO] [INFO] --- yuicompressor-maven-plugin:1.3.0:compress (default) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded net.alchim31.maven:yuicompressor-maven-plugin:1.3.0(default) mojoStarted org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-compile)[INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-compile) mojoStarted org.apache.felix:maven-scr-plugin:1.7.2(generate-scr-scrdescriptor) [INFO] [INFO] --- maven-scr-plugin:1.7.2:scr (generate-scr-scrdescriptor) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.felix:maven-scr-plugin:1.7.2(generate-scr-scrdescriptor) mojoStarted org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-testResources)[INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-testResources) mojoStarted org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-testCompile)[INFO] No sources to compile [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-compiler-plugin:2.3.2(default-testCompile) mojoStarted org.apache.maven.plugins:maven-surefire-plugin:2.7.2(default-test)[INFO] Surefire report directory: https://builds.apache.org/job/sling-samples-1.5/ws/contrib-1.5/accessmanager-ui/target/surefire-reports [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @ org.apache.sling.samples.accessmanager.ui --- --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 mojoSucceeded org.apache.maven.plugins:maven-surefire-plugin:2.7.2(default-test) [JENKINS] Recording test results[INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 mojoStarted
[jira] [Created] (SLING-2493) sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes
Alexander Klimetschek created SLING-2493: Summary: sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.1.0 Reporter: Alexander Klimetschek Priority: Minor MapEntries [0] does first a scan in doInit() and then starts a thread for getting observation changes for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2493) sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes
[ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: - Description: MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java was: MapEntries [0] does first a scan in doInit() and then starts a thread for getting observation changes for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes --- Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.1.0 Reporter: Alexander Klimetschek Priority: Minor MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2493) sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes
[ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: - Attachment: SLING-2493.patch Attached possible patch (untested, as testing this is really difficult). sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes --- Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Reporter: Alexander Klimetschek Priority: Minor Attachments: SLING-2493.patch MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2493) sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes
[ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: - Summary: sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes (was: sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes) sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes - Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Reporter: Alexander Klimetschek Priority: Minor Attachments: SLING-2493.patch MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2493) sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes
[ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: - Affects Version/s: (was: JCR Resource 2.1.0) sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes - Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Reporter: Alexander Klimetschek Priority: Minor Attachments: SLING-2493.patch MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated at the same time. Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
