Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
+1 On Mon, Mar 23, 2015 at 6:03 AM, Radu Cotescu r...@apache.org wrote: Hi, We solved 54 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12329007 (44) https://issues.apache.org/jira/browse/SLING/fixforversion/12329008 (10) Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1216 The staging repository contains the following artifacts: org.apache.sling.scripting.sightly org.apache.sling.scripting.sightly.js.provider org.apache.sling.scripting.sightly.repl org.apache.sling.scripting.sightly.testing org.apache.sling.scripting.sightly.testing-content 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 1216 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Created] (SLING-4530) Add .mvn/jvm.config to reactor project
Robert Munteanu created SLING-4530: -- Summary: Add .mvn/jvm.config to reactor project Key: SLING-4530 URL: https://issues.apache.org/jira/browse/SLING-4530 Project: Sling Issue Type: Bug Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu Maven 3.3.1 has added the possibility of storing the JVM configuration in a .mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm options and command line parameters|http://jira.codehaus.org/browse/MNG-5767] ). Those flags will apply to all builds by default. We should add the flags specified in SLING-443 and SLING-1782 to make sure that we have everyone building Sling with the required flags OOTB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4530) Add .mvn/jvm.config to reactor
[ https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-4530. Resolution: Fixed Add .mvn/jvm.config to reactor -- Key: SLING-4530 URL: https://issues.apache.org/jira/browse/SLING-4530 Project: Sling Issue Type: Bug Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu Maven 3.3.1 has added the possibility of storing the JVM configuration in a .mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm options and command line parameters|http://jira.codehaus.org/browse/MNG-5767] ). Those flags will apply to all builds by default. We should add the flags specified in SLING-443 and SLING-1782 to make sure that we have everyone building Sling with the required flags OOTB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3987) move from Subversion to Git
[
https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375863#comment-14375863
]
Robert Munteanu commented on SLING-3987:
{quote}After playing around with some and reading about pros and cons, it seems
that Google repo fits best for Sling.{quote}
Being a gitslave user for some time, I find it a good fit for our own products
( we use it internally at Adobe ). It would be great to list the pros and cons
of each tool in the wiki page
move from Subversion to Git
---
Key: SLING-3987
URL: https://issues.apache.org/jira/browse/SLING-3987
Project: Sling
Issue Type: Task
Components: Best practices
Reporter: Oliver Lietz
track work for moving to Git
[Wiki: Move from Subversion to
Git|https://cwiki.apache.org/confluence/display/SLING/Move+from+Subversion+to+Git]
[discussion
@dev|http://apache-sling.73963.n3.nabble.com/jira-Created-SLING-3987-move-from-Subversion-to-Git-td4040882.html#a4040901]
with [~cziegeler], [~bdelacretaz], [~fmeschbe], [~justinedelson], [~rombert]
and [~radu.cotescu]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert
[jira] [Assigned] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-4050: -- Assignee: Robert Munteanu Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-443) OutOfMemory Error while building the jcr/jackrabbit-server bundle
[ https://issues.apache.org/jira/browse/SLING-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-443. --- Resolution: Fixed This looks like it's been fixed a long time ago, please reopen if still an issue OutOfMemory Error while building the jcr/jackrabbit-server bundle - Key: SLING-443 URL: https://issues.apache.org/jira/browse/SLING-443 Project: Sling Issue Type: Bug Components: JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Priority: Minor Reported on [1], the full build of Sling causes an OutOfMemoryError while building the jcr/jackrabbit-server bundle. This is most probably the result of implementing SLING-437. A fix must be found for this issue to circumvent this. [1] http://markmail.org/message/gdn7jtlrdjcepngg -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4530) Add .mvn/jvm.config to reactor
[ https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-4530: --- Summary: Add .mvn/jvm.config to reactor (was: Add .mvn/jvm.config to reactor project) Add .mvn/jvm.config to reactor -- Key: SLING-4530 URL: https://issues.apache.org/jira/browse/SLING-4530 Project: Sling Issue Type: Bug Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu Maven 3.3.1 has added the possibility of storing the JVM configuration in a .mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm options and command line parameters|http://jira.codehaus.org/browse/MNG-5767] ). Those flags will apply to all builds by default. We should add the flags specified in SLING-443 and SLING-1782 to make sure that we have everyone building Sling with the required flags OOTB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4530) Add .mvn/jvm.config to reactor
[ https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375886#comment-14375886 ] Robert Munteanu commented on SLING-4530: Created config in https://svn.apache.org/viewvc?view=revisionrevision=r1668633 Add .mvn/jvm.config to reactor -- Key: SLING-4530 URL: https://issues.apache.org/jira/browse/SLING-4530 Project: Sling Issue Type: Bug Components: General Reporter: Robert Munteanu Assignee: Robert Munteanu Maven 3.3.1 has added the possibility of storing the JVM configuration in a .mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm options and command line parameters|http://jira.codehaus.org/browse/MNG-5767] ). Those flags will apply to all builds by default. We should add the flags specified in SLING-443 and SLING-1782 to make sure that we have everyone building Sling with the required flags OOTB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Hi Robert Another option might be to use mongo as an additional run mode. I.e. run mode oak would select the Oak repository implementation and run mode mongo would add some configuration in order to activate the mongo persistence. I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu romb...@apache.org wrote: Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert
[jira] [Commented] (SLING-2192) Support JAX-RS resource classes
[ https://issues.apache.org/jira/browse/SLING-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375729#comment-14375729 ] Krystian Panek commented on SLING-2192: --- +1 Support JAX-RS resource classes --- Key: SLING-2192 URL: https://issues.apache.org/jira/browse/SLING-2192 Project: Sling Issue Type: New Feature Reporter: Reto Gmür Attachments: SLING-2192-20110310.patch, SLING-2192-20111004.patch, SLING-2192-20111013.patch, SLING-2192-new-jax-rs-bundle.patch, SLING-2192-new-jax-rs-bundle.patch, SLING-2192-with-sling-style-style-registration.patch, SLING-2192-with-tests.patch, jaxrs-in-contrib.patch, slingr-on-wink-osgi.patch It should be possible to register jax resource classes and providers as services. As they don't implement a specific interface services that expose java.lang.Object should be considered as javx-rs services iff they have the service property javax.ws.rs set to true. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to normal : sling-trunk-1.6 #3202
See https://builds.apache.org/job/sling-trunk-1.6/3202/changes
[jira] [Commented] (SLING-4528) Moving to Oak
[
https://issues.apache.org/jira/browse/SLING-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376021#comment-14376021
]
Chetan Mehrotra commented on SLING-4528:
[~olli] JcrRepositoryHacks does not look good in name! In January I got most of
the IT in Sling pass with Oak however was not able to cleanup the server bundle
code. Unfortunately I do not yet have time to look into this. Hopefully would
have some time post 1.2 release
Moving to Oak
-
Key: SLING-4528
URL: https://issues.apache.org/jira/browse/SLING-4528
Project: Sling
Issue Type: Task
Components: JCR
Reporter: Oliver Lietz
Labels: oak
Fix For: JCR Oak Server 1.0.0
_Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is
not released and contains some TODOs and {{JcrRepositoryHacks}}.
What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4531) sling:Folder should include a mix:title mixin.
Ben Helleman created SLING-4531: --- Summary: sling:Folder should include a mix:title mixin. Key: SLING-4531 URL: https://issues.apache.org/jira/browse/SLING-4531 Project: Sling Issue Type: Improvement Components: Best practices Affects Versions: API 2.9.0 Reporter: Ben Helleman It would be nice to have a consistent definition to define a title for a sling folder. To provide consistency it adding a mixin mix:title would help provide clarity. Adding mix:title includes: jcr:description jcr:title -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4531) sling:Folder should include a mix:title mixin.
[ https://issues.apache.org/jira/browse/SLING-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Helleman updated SLING-4531: Description: It would be nice to have a consistent definition to define a title for a sling:Folder. To provide consistency it adding a mixin mix:title would help provide clarity. Adding mix:title includes: jcr:description jcr:title was: It would be nice to have a consistent definition to define a title for a sling folder. To provide consistency it adding a mixin mix:title would help provide clarity. Adding mix:title includes: jcr:description jcr:title sling:Folder should include a mix:title mixin. -- Key: SLING-4531 URL: https://issues.apache.org/jira/browse/SLING-4531 Project: Sling Issue Type: Improvement Components: Best practices Affects Versions: API 2.9.0 Reporter: Ben Helleman It would be nice to have a consistent definition to define a title for a sling:Folder. To provide consistency it adding a mixin mix:title would help provide clarity. Adding mix:title includes: jcr:description jcr:title -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
On Mon, 2015-03-23 at 10:50 -0400, Daniel Klco wrote: org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. Good catch! I assumed the maven release plugin would be banning SNAPSHOTs, but apparently this is not the case ... We can't deploy SNAPSHOT depedencies on Maven Central and we should not as a general rule depend on SNAPSHOTs from releases, as the SNAPSHOTs will at some point go away and make the released artifact invalid. So we either release the org.apache.sling.performance.base artifact and depend on it or drop the org.apache.sling.sightly.testing artifact from the release. Radu? Robert
Re: SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Hi Robert ... We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? Yes, I think that's a good option. So to set the default to oak_tar the sling.properties file should contain a line similar to the following: sling.run.mode.install.options=jackrabbit,oak|oak_tar,oak_mongo That indicates that run mode jackrabbit (default) or oak must be active and oak_tar or oak_mongo must also be active. Is it a problem if oak_tar is active for jackrabbit deployments? Carsten, I believe you know this mechanism best. Is it possible to have run modes depend on the presence of other run modes? Regards Julian On Mon, Mar 23, 2015 at 3:41 PM, Robert Munteanu rob...@lmn.ro wrote: Hi Julian, On Mon, Mar 23, 2015 at 3:35 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert Another option might be to use mongo as an additional run mode. I.e. run mode oak would select the Oak repository implementation and run mode mongo would add some configuration in order to activate the mongo persistence. I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Overall that looks good, but I would still use the 'oak' prefix. This way, we don't clash with other possible runmodes, for instance 'mongo' might clash with a runmode for the MongoDB resource provider, or another persistence provider using the mongo backend. What I not 100% sure about though is how we would 'deactivate' the default TarkMK configuration if we have something like oak,oak_mongo active. The 'oak' runmode would define a SegmentNodeStoreService OSGi config and then the oak_mongo runmode would define a DocumentNodeStoreService OSGi config, which will clash. I would see a way out by having oak be an 'abstract' profile and then oak_tar and oak_mongo inheriting from it. We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? If it does, let's see if this is doable or if any changes are needed, because I have no idea how to implement them :-) Robert Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu romb...@apache.org wrote: Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert -- Sent from my (old) computer
[jira] [Commented] (SLING-2387) OBR at http://sling.apache.org/obr/repository.xml is totally out of date
[ https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376042#comment-14376042 ] Jason E Bailey commented on SLING-2387: --- We're looking at the OBR to solve a number of issues we have from a maintenance POV in our build and production environments. According to this page; https://sling.apache.org/documentation/development/release-management.html#appendix-c-deploy-bundles-on-the-sling-obr It indicates that the release to the OBR is part of the release process. It would be very helpful to us if the current OBR could be updated. OBR at http://sling.apache.org/obr/repository.xml is totally out of date Key: SLING-2387 URL: https://issues.apache.org/jira/browse/SLING-2387 Project: Sling Issue Type: Bug Reporter: Markus Joschko Priority: Minor It would be quite handy to have the most recent stable bundles of sling available in a bundle repository so that existing installations can easily be updated. However the versions in the existing obr are out of date (way out of date). If there is a way to automate the deployment I might be able to give a hand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Build failed in Jenkins: sling-contrib-1.6 #1682
On Mon, Mar 23, 2015 at 4:10 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: [ERROR] Failed to execute goal on project org.apache.sling.distribution.it: Could not resolve dependencies for project org.apache.sling:org.apache.sling.distribution.it:bundle:0.0.1-SNAPSHOT: Could not find artifact org.apache.sling:org.apache.sling.launchpad:jar:standalone:7-SNAPSHOT in Nexus (http://repository.apache.org/snapshots) - [Help 1] Switched dependency to launchpad 7 in https://svn.apache.org/r1668655 Robert
[VOTE RESULT] Release Apache Sling discovery.impl 1.1.0
The vote passed with 3 +1 votes - thanks for voting! I'll do the rest next, Cheers, Stefan
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
On Mon, 2015-03-23 at 12:03 +0200, Radu Cotescu wrote: Please vote to approve this release: [ ] +1 Approve the release +1 Robert
Re: SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Hi Julian, On Mon, Mar 23, 2015 at 3:35 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert Another option might be to use mongo as an additional run mode. I.e. run mode oak would select the Oak repository implementation and run mode mongo would add some configuration in order to activate the mongo persistence. I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Overall that looks good, but I would still use the 'oak' prefix. This way, we don't clash with other possible runmodes, for instance 'mongo' might clash with a runmode for the MongoDB resource provider, or another persistence provider using the mongo backend. What I not 100% sure about though is how we would 'deactivate' the default TarkMK configuration if we have something like oak,oak_mongo active. The 'oak' runmode would define a SegmentNodeStoreService OSGi config and then the oak_mongo runmode would define a DocumentNodeStoreService OSGi config, which will clash. I would see a way out by having oak be an 'abstract' profile and then oak_tar and oak_mongo inheriting from it. We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? If it does, let's see if this is doable or if any changes are needed, because I have no idea how to implement them :-) Robert Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu romb...@apache.org wrote: Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert -- Sent from my (old) computer
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. -Dan On Mon, Mar 23, 2015 at 10:43 AM, Robert Munteanu romb...@apache.org wrote: On Mon, 2015-03-23 at 12:03 +0200, Radu Cotescu wrote: Please vote to approve this release: [ ] +1 Approve the release +1 Robert
Build failed in Jenkins: sling-contrib-1.6 #1682
See https://builds.apache.org/job/sling-contrib-1.6/1682/ -- [...truncated 11960 lines...] Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/project/4.1.1/project-4.1.1.pom (17 KB at 909.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1/httpclient-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1/httpclient-4.1.pom (6 KB at 310.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1/httpcomponents-client-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1/httpcomponents-client-4.1.pom (12 KB at 612.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/commons-codec/commons-codec/1.4/commons-codec-1.4.pom Downloaded: http://repo.maven.apache.org/maven2/commons-codec/commons-codec/1.4/commons-codec-1.4.pom (11 KB at 602.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.pom (6 KB at 283.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.json/2.0.6/org.apache.sling.commons.json-2.0.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.json/2.0.6/org.apache.sling.commons.json-2.0.6.pom (4 KB at 166.5 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/sling/10/sling-10.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/sling/10/sling-10.pom (26 KB at 1253.3 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.discovery.impl/1.0.12/org.apache.sling.discovery.impl-1.0.12.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.discovery.impl/1.0.12/org.apache.sling.discovery.impl-1.0.12.pom (10 KB at 297.3 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/org.apache.jackrabbit.vault/3.1.0/org.apache.jackrabbit.vault-3.1.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/org.apache.jackrabbit.vault/3.1.0/org.apache.jackrabbit.vault-3.1.0.pom (10 KB at 381.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.1.0/parent-3.1.0.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/vault/parent/3.1.0/parent-3.1.0.pom (14 KB at 443.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.3.1/httpcore-osgi-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.3.1/httpcore-osgi-4.3.1.pom (4 KB at 121.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.3.1/httpcomponents-core-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.3.1/httpcomponents-core-4.3.1.pom (12 KB at 659.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.3.1/httpcore-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.3.1/httpcore-4.3.1.pom (5 KB at 264.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.3.1/httpcore-nio-4.3.1.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.3.1/httpcore-nio-4.3.1.pom (5 KB at 239.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.3.2/httpclient-osgi-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.3.2/httpclient-osgi-4.3.2.pom (8 KB at 318.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.3.2/httpcomponents-client-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.3.2/httpcomponents-client-4.3.2.pom (16 KB at 816.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.3.2/httpclient-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.3.2/httpclient-4.3.2.pom (6 KB at 276.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.3.2/httpmime-4.3.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.3.2/httpmime-4.3.2.pom (5 KB at 267.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-cache/4.3.2/httpclient-cache-4.3.2.pom Downloaded:
Jenkins build became unstable: sling-trunk-1.6 #3205
See https://builds.apache.org/job/sling-trunk-1.6/3205/changes
[jira] [Updated] (SLING-2729) Performance Testing suite: Modified ReportLogger to log the test case name
[ https://issues.apache.org/jira/browse/SLING-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-2729: Fix Version/s: Sling JUnit Performance 1.0.2 Performance Testing suite: Modified ReportLogger to log the test case name --- Key: SLING-2729 URL: https://issues.apache.org/jira/browse/SLING-2729 Project: Sling Issue Type: Improvement Components: Testing Reporter: Antonio Sanso Assignee: Antonio Sanso Priority: Minor Labels: PatchAvailable Fix For: Sling JUnit Performance 1.0.2 Attachments: performance_reportlogger-svn.patch, performance_reportlogger.patch Modified ReportLogger to log the test case name as well. Also, changed the method signatures so that it's clear what is being logged. This works with patch 1 to distinguish between different test case instances The motivation behind this is that a suite can contain test cases that are different logically, but the test case should be able to be parameterized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3579) Allow performance tests to report custom class name to the report logger
[ https://issues.apache.org/jira/browse/SLING-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-3579: Fix Version/s: Sling JUnit Performance 1.0.2 Allow performance tests to report custom class name to the report logger Key: SLING-3579 URL: https://issues.apache.org/jira/browse/SLING-3579 Project: Sling Issue Type: Improvement Components: Testing Reporter: Andrei Dulvac Assignee: Antonio Sanso Priority: Minor Labels: PatchAvailable Fix For: Sling JUnit Performance 1.0.2 Attachments: SLING-3579.patch allow performance tests to overwrite the class name passed in by the junit runner to the report logger. This is useful for test factories and the like. SLING-3294 breaks SLING-2727 because it forces a toString method on the test class. The proposed solution allows this only if the test case implements IdentifiableClassName#testClassName() -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4535) discovery: lower warn to info for 'still in isolated mode'
Stefan Egli created SLING-4535:
--
Summary: discovery: lower warn to info for 'still in isolated mode'
Key: SLING-4535
URL: https://issues.apache.org/jira/browse/SLING-4535
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Discovery Impl 1.0.10
Reporter: Stefan Egli
Fix For: Discovery Impl 1.1.2
The following warn shows up in various situations eg when PropertyProvider are
bound but first voting has not finished yet. This should not be a WARN but
rather an INFO
{code}
WARN [pool-6-thread-14] org.apache.sling.discovery.impl.DiscoveryServiceImpl
handlePotentialTopologyChange: still in isolated mode - cannot send
TOPOLOGY_INIT yet.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SLING-4535) discovery: lower warn to info for 'still in isolated mode'
[
https://issues.apache.org/jira/browse/SLING-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-4535:
--
Assignee: Stefan Egli
discovery: lower warn to info for 'still in isolated mode'
--
Key: SLING-4535
URL: https://issues.apache.org/jira/browse/SLING-4535
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Discovery Impl 1.0.10
Reporter: Stefan Egli
Assignee: Stefan Egli
Fix For: Discovery Impl 1.1.2
The following warn shows up in various situations eg when PropertyProvider
are bound but first voting has not finished yet. This should not be a WARN
but rather an INFO
{code}
WARN [pool-6-thread-14] org.apache.sling.discovery.impl.DiscoveryServiceImpl
handlePotentialTopologyChange: still in isolated mode - cannot send
TOPOLOGY_INIT yet.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4536) exclude HtmlResponse.html from Rat checks
Oliver Lietz created SLING-4536:
---
Summary: exclude HtmlResponse.html from Rat checks
Key: SLING-4536
URL: https://issues.apache.org/jira/browse/SLING-4536
Project: Sling
Issue Type: Task
Components: Servlets
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Servlets POST 2.3.8
{noformat}
plugin
groupIdorg.apache.rat/groupId
artifactIdapache-rat-plugin/artifactId
configuration
excludes
excludesrc/main/resources/org/apache/sling/servlets/post/HtmlResponse.html/exclude
/excludes
/configuration
/plugin
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.8 #891
See https://builds.apache.org/job/sling-trunk-1.8/891/changes
[jira] [Commented] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376124#comment-14376124 ] Robert Munteanu commented on SLING-4050: Updated the documentation in https://svn.apache.org/viewvc?view=revisionrevision=1668678 Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4532) Performance: DefaultSlingScript has too much overhead
[ https://issues.apache.org/jira/browse/SLING-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Richard updated SLING-4532: Attachment: measure.patch Performance: DefaultSlingScript has too much overhead - Key: SLING-4532 URL: https://issues.apache.org/jira/browse/SLING-4532 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Core 2.0.28 Reporter: Joel Richard Attachments: measure.patch While I was profiling a slow page, I saw that a significant amount of time is spent inside DefaultSlingScript. Since profilers often cannot be trusted, I added some code (see attachment) to measure the time spent without the script execution itself (JSP in my case) and came to 8% of the whole page rendering time. Since the JSP itself has been compiled before the measurements, I would have expected the overhead clearly below 1%. The page which I profiled has about 100 sling includes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4532) Performance: DefaultSlingScript has too much overhead
Joel Richard created SLING-4532: --- Summary: Performance: DefaultSlingScript has too much overhead Key: SLING-4532 URL: https://issues.apache.org/jira/browse/SLING-4532 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting Core 2.0.28 Reporter: Joel Richard Attachments: measure.patch While I was profiling a slow page, I saw that a significant amount of time is spent inside DefaultSlingScript. Since profilers often cannot be trusted, I added some code (see attachment) to measure the time spent without the script execution itself (JSP in my case) and came to 8% of the whole page rendering time. Since the JSP itself has been compiled before the measurements, I would have expected the overhead clearly below 1%. The page which I profiled has about 100 sling includes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Hm, I'm doing something wrong and not sure what. On Mon, Mar 23, 2015 at 5:06 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert ... We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? Yes, I think that's a good option. So to set the default to oak_tar the sling.properties file should contain a line similar to the following: sling.run.mode.install.options=jackrabbit,oak|oak_tar,oak_mongo Great, I used exactly that. That indicates that run mode jackrabbit (default) or oak must be active and oak_tar or oak_mongo must also be active. Is it a problem if oak_tar is active for jackrabbit deployments? I think not and we could revisit this later if neeed. The net effect is that an OSGi config is added but no one picks it up and for the oak_mongo runmode that an additional bundle is installed. So based on the value of sling.run.modes, the following behaviour is observed - (empty): jackrabbit 2.x configured - oak: Oak with SegmentNodeStore configured - oak,oak_mongo: Oak with DocumentNodeStore configured Other combinations may be added later, but we now have a good starting point. Thanks for your help, Robert Regards Julian On Mon, Mar 23, 2015 at 3:41 PM, Robert Munteanu rob...@lmn.ro wrote: Hi Julian, On Mon, Mar 23, 2015 at 3:35 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert Another option might be to use mongo as an additional run mode. I.e. run mode oak would select the Oak repository implementation and run mode mongo would add some configuration in order to activate the mongo persistence. I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Overall that looks good, but I would still use the 'oak' prefix. This way, we don't clash with other possible runmodes, for instance 'mongo' might clash with a runmode for the MongoDB resource provider, or another persistence provider using the mongo backend. What I not 100% sure about though is how we would 'deactivate' the default TarkMK configuration if we have something like oak,oak_mongo active. The 'oak' runmode would define a SegmentNodeStoreService OSGi config and then the oak_mongo runmode would define a DocumentNodeStoreService OSGi config, which will clash. I would see a way out by having oak be an 'abstract' profile and then oak_tar and oak_mongo inheriting from it. We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? If it does, let's see if this is doable or if any changes are needed, because I have no idea how to implement them :-) Robert Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu romb...@apache.org wrote: Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert -- Sent from my (old) computer -- Sent from my (old) computer
[jira] [Commented] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376114#comment-14376114 ] Robert Munteanu commented on SLING-4050: Updated runmode definitions in https://svn.apache.org/viewvc?view=revisionrevision=r1668674 . Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: SLING-4050 - Make it easier to run launchpad on Oak/Mongo
Good job! I agree that tar vs mongo is currently sufficient. Regards Julian On Mon, Mar 23, 2015 at 5:06 PM, Robert Munteanu rob...@lmn.ro wrote: Hm, I'm doing something wrong and not sure what. On Mon, Mar 23, 2015 at 5:06 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert ... We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? Yes, I think that's a good option. So to set the default to oak_tar the sling.properties file should contain a line similar to the following: sling.run.mode.install.options=jackrabbit,oak|oak_tar,oak_mongo Great, I used exactly that. That indicates that run mode jackrabbit (default) or oak must be active and oak_tar or oak_mongo must also be active. Is it a problem if oak_tar is active for jackrabbit deployments? I think not and we could revisit this later if neeed. The net effect is that an OSGi config is added but no one picks it up and for the oak_mongo runmode that an additional bundle is installed. So based on the value of sling.run.modes, the following behaviour is observed - (empty): jackrabbit 2.x configured - oak: Oak with SegmentNodeStore configured - oak,oak_mongo: Oak with DocumentNodeStore configured Other combinations may be added later, but we now have a good starting point. Thanks for your help, Robert Regards Julian On Mon, Mar 23, 2015 at 3:41 PM, Robert Munteanu rob...@lmn.ro wrote: Hi Julian, On Mon, Mar 23, 2015 at 3:35 PM, Julian Sedding jsedd...@gmail.com wrote: Hi Robert Another option might be to use mongo as an additional run mode. I.e. run mode oak would select the Oak repository implementation and run mode mongo would add some configuration in order to activate the mongo persistence. I could imagine various pre-configured aspects for Oak, e.g. whether a file datastore should be used or not. So examples might be: oak: Oak repository on TarMK with blobs stored in segments oak,datastore: Oak repository on TarMK with blobs in datastore oak,mongo,datastore: Oak repository on Mongo with blobs in datastore WDYT, would that be a viable alternative? Overall that looks good, but I would still use the 'oak' prefix. This way, we don't clash with other possible runmodes, for instance 'mongo' might clash with a runmode for the MongoDB resource provider, or another persistence provider using the mongo backend. What I not 100% sure about though is how we would 'deactivate' the default TarkMK configuration if we have something like oak,oak_mongo active. The 'oak' runmode would define a SegmentNodeStoreService OSGi config and then the oak_mongo runmode would define a DocumentNodeStoreService OSGi config, which will clash. I would see a way out by having oak be an 'abstract' profile and then oak_tar and oak_mongo inheriting from it. We could also make it that when the oak runmode is activated it requires one of oak_tar,oak_mongo active as well and defaults to oak_tar. Would that work for you? If it does, let's see if this is doable or if any changes are needed, because I have no idea how to implement them :-) Robert Regards Julian On Mon, Mar 23, 2015 at 2:21 PM, Robert Munteanu romb...@apache.org wrote: Hi, I'm going to take a quick look at SLING-4050 and will probably add a new runmode for Mongo. I noticed that we currenty define two exclusive run modes for the Launchpad: jackrabbit and oak. For SLING-4050 I would define the third one: oak_mongo . I find that it would be better to rename the oak runmode to oak_tar - as it uses the TarMK backend, but I'm not sure of the implications. The 'oak' runmode has not been released with Launchpad 7 so the only people affected would be the ones using -SNAPSHOT releases. Does anyone see any issues with renaming the oak runmode to oak_tar ? I will handle all the Maven/Jenkins stuff if we agree to do that. Cheers, Robert -- Sent from my (old) computer -- Sent from my (old) computer
[jira] [Created] (SLING-4534) exclude all JSON files from Rat checks
Oliver Lietz created SLING-4534:
---
Summary: exclude all JSON files from Rat checks
Key: SLING-4534
URL: https://issues.apache.org/jira/browse/SLING-4534
Project: Sling
Issue Type: Task
Affects Versions: Parent 22
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Parent 23
{noformat}
exclude**/*.json/exclude
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build is back to stable : sling-oak-it-1.6 #429
See https://builds.apache.org/job/sling-oak-it-1.6/429/changes
[jira] [Resolved] (SLING-4534) exclude all JSON files from Rat checks
[
https://issues.apache.org/jira/browse/SLING-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-4534.
-
Resolution: Done
r1668719
exclude all JSON files from Rat checks
--
Key: SLING-4534
URL: https://issues.apache.org/jira/browse/SLING-4534
Project: Sling
Issue Type: Task
Affects Versions: Parent 22
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Parent 23
{noformat}
exclude**/*.json/exclude
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Build failed in Jenkins: sling-trunk-1.6 #3201
See https://builds.apache.org/job/sling-trunk-1.6/3201/changes Changes: [radu] @trivial: corrected test [radu] [maven-release-plugin] prepare for next development iteration [radu] [maven-release-plugin] prepare release org.apache.sling.scripting.sightly-1.0.0 [radu] @releng: using released version of o.a.s.xss [radu] @releng: updated o.a.s.xss to released version -- [...truncated 59920 lines...] [INFO] Apache Sling JSON Library . SUCCESS [8.844s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [37.660s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [6.178s] [INFO] Apache Sling MIME type mapping support SUCCESS [8.009s] [INFO] Apache Sling Commons OSGi support . SUCCESS [8.438s] [INFO] Apache Sling Scheduler Support SUCCESS [7.635s] [INFO] Apache Sling Testing Utilities SUCCESS [15.336s] [INFO] Apache Sling Thread Dumper SUCCESS [5.633s] [INFO] Apache Sling Thread Support ... SUCCESS [7.699s] [INFO] Apache Sling Authentication Service ... SUCCESS [7.325s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [12.364s] [INFO] Apache Sling Engine Implementation SUCCESS [18.833s] [INFO] Apache Sling Repository API Bundle SUCCESS [9.259s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [6.562s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [5.528s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [7.113s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [26.483s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [6.536s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [6.103s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [7.895s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [38.860s] [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SUCCESS [20.008s] [INFO] Apache Sling Versioning Integration Tests . SUCCESS [14.676s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [7.673s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [7.002s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.718s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [10.830s] [INFO] Apache Sling Oak Repository Server SUCCESS [9.246s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [53.904s] [INFO] Apache Sling Servlet Resolver . SUCCESS [13.373s] [INFO] Apache Sling Default GET Servlets . SUCCESS [7.936s] [INFO] Apache Sling Default POST Servlets SUCCESS [10.510s] [INFO] Apache Sling Compat Servlets .. SUCCESS [5.869s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [5.700s] [INFO] Apache Sling Scripting Core implementation SUCCESS [14.630s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [14.228s] [INFO] Apache Sling Scripting JSP Support SUCCESS [11.436s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [11.829s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [7.745s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [6.128s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [21.963s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [9.250s] [INFO] Apache Sling Discovery API SUCCESS [8.319s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [4:07.300s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [6.405s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [5.250s] [INFO] Apache Sling Event Support SUCCESS [11:54.381s] [INFO] Apache Sling Feature Flags SUCCESS [5.531s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [6.375s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [7.163s] [INFO] Apache Sling Service User Mapper .. SUCCESS [8.559s] [INFO] Apache Sling Settings . SUCCESS [6.225s] [INFO] Apache Sling Web Console Branding . SUCCESS [5.669s] [INFO] Apache Sling Web Console Security Provider SUCCESS [6.403s] [INFO] Apache Sling Explorer . SUCCESS [14.577s] [INFO] Apache Sling Health Check Core SUCCESS [10.032s] [INFO] Apache Sling Health Check Annotations . SUCCESS [5.360s] [INFO] Apache Sling Health Check Samples . SUCCESS [6.915s] [INFO] Apache Sling Health Check Support Components .. SUCCESS [6.468s] [INFO]
[VOTE] Release Apache Sling Scripting Sightly 1.0.0
Hi, We solved 54 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12329007 (44) https://issues.apache.org/jira/browse/SLING/fixforversion/12329008 (10) Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1216 The staging repository contains the following artifacts: org.apache.sling.scripting.sightly org.apache.sling.scripting.sightly.js.provider org.apache.sling.scripting.sightly.repl org.apache.sling.scripting.sightly.testing org.apache.sling.scripting.sightly.testing-content 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 1216 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Commented] (SLING-4528) Moving to Oak
[
https://issues.apache.org/jira/browse/SLING-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375587#comment-14375587
]
Michael Dürig commented on SLING-4528:
--
Maybe [~chetanm] and [~fmeschbe] would know more as they have been involved
with SLING-4277 and SLING-3384, respectively. Also maybe helpful:
http://markmail.org/message/rqtck5dbtvj32po5
Moving to Oak
-
Key: SLING-4528
URL: https://issues.apache.org/jira/browse/SLING-4528
Project: Sling
Issue Type: Task
Components: JCR
Reporter: Oliver Lietz
Labels: oak
Fix For: JCR Oak Server 1.0.0
_Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is
not released and contains some TODOs and {{JcrRepositoryHacks}}.
What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4528) Moving to Oak
[
https://issues.apache.org/jira/browse/SLING-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375592#comment-14375592
]
Bertrand Delacretaz commented on SLING-4528:
I'd suggest reviewing the TODOs with the Oak project, maybe ask on their list
with the relevant code excerpts.
If all our tests pass, or if the disabled ones are reasonable
(launchpad/integration-tests does have some @Category(JackrabbitOnly.class)
tests) we can go ahead with a release.
The Oak integration tests are running at
https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.6/ and they're
green (well..blue) now, but I'm not sure if they are using the latest snapshots
and Oak version.
Moving to Oak
-
Key: SLING-4528
URL: https://issues.apache.org/jira/browse/SLING-4528
Project: Sling
Issue Type: Task
Components: JCR
Reporter: Oliver Lietz
Labels: oak
Fix For: JCR Oak Server 1.0.0
_Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is
not released and contains some TODOs and {{JcrRepositoryHacks}}.
What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4528) Moving to Oak
[
https://issues.apache.org/jira/browse/SLING-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375591#comment-14375591
]
Felix Meschberger commented on SLING-4528:
--
I am sorry, I don't know where the Oak based repository bundle stands at this
point.
Moving to Oak
-
Key: SLING-4528
URL: https://issues.apache.org/jira/browse/SLING-4528
Project: Sling
Issue Type: Task
Components: JCR
Reporter: Oliver Lietz
Labels: oak
Fix For: JCR Oak Server 1.0.0
_Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is
not released and contains some TODOs and {{JcrRepositoryHacks}}.
What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Sling Models 1.2, Validation
... we should not build such references from 'core' to contrib. +1 On Sun, Mar 22, 2015 at 3:53 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Friday 20 March 2015 14:09:19 Robert Munteanu wrote: On Thu, 2015-03-19 at 11:07 +0100, Stefan Seifert wrote: @other sling committers: sling validation is part of contrib, is it allowed to be referenced by sling models? or should validation moved out of contrib first? I stated my opinion at [1] that we should not build such references from 'core' to contrib. +1 Kondrad seems to think otherwise, but it would be interesting to hear at least a third opinion. Is Validation ready for 1.0 or at least for a first release? See my comment in SLING-4461 regarding release versions. O. Robert [1]: http://sling-dev.markmail.org/thread/srnx3iysytt7dtfk
[jira] [Commented] (SLING-4530) Add .mvn/jvm.config to reactor
[
https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376691#comment-14376691
]
Robert Munteanu commented on SLING-4530:
The point is to get consistency when building Sling. Does {{.mvn/jvm.config}}
override your MAVEN_OPTS?
Add .mvn/jvm.config to reactor
--
Key: SLING-4530
URL: https://issues.apache.org/jira/browse/SLING-4530
Project: Sling
Issue Type: Bug
Components: General
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Maven 3.3.1 has added the possibility of storing the JVM configuration in a
.mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm
options and command line parameters|http://jira.codehaus.org/browse/MNG-5767]
). Those flags will apply to all builds by default.
We should add the flags specified in SLING-443 and SLING-1782 to make sure
that we have everyone building Sling with the required flags OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.6 #3207
See https://builds.apache.org/job/sling-trunk-1.6/3207/changes
[jira] [Updated] (SLING-2311) Sling Performance Testing tool
[ https://issues.apache.org/jira/browse/SLING-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-2311: Fix Version/s: Sling JUnit Performance 1.0.2 Sling Performance Testing tool -- Key: SLING-2311 URL: https://issues.apache.org/jira/browse/SLING-2311 Project: Sling Issue Type: New Feature Components: Testing Reporter: Antonio Sanso Assignee: Justin Edelson Priority: Minor Fix For: Sling JUnit Performance 1.0.2 Attachments: ResolveWithManyAliasTest.java, ResolveWithManyVanityPath.png, SLING-2311-patch.txt, plot.sh, plot.sh As described/discussed in [0] it would be nice to have a performance test tool in Sling . This can be useful in different situations (e.g. micro benchmarks of a feature and so on). Patch to follow [0] http://sling.markmail.org/message/bz44im7aqeae4r57 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-2727) Allow PerformanceRunner to run tests provided by a factory method
[ https://issues.apache.org/jira/browse/SLING-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-2727: Fix Version/s: Sling JUnit Performance 1.0.2 Allow PerformanceRunner to run tests provided by a factory method - Key: SLING-2727 URL: https://issues.apache.org/jira/browse/SLING-2727 Project: Sling Issue Type: Improvement Components: Testing Reporter: Andrei Dulvac Assignee: Antonio Sanso Priority: Minor Labels: PatchAvailable Fix For: Sling JUnit Performance 1.0.2 Attachments: performance_factory-svn.patch, performance_factory.patch 1. I have modified PerformanceRunner to be able to run tests provided through a factory method annotated with @PerformanceTestFactory, when used with @PerformanceTestSuites. The method can be used (this is optional) on a test case object that is added to the ParameterizedTestList returned by the @PerformanceTestSuite method. If there is no @PerformanceTestFactory method, the behaviour stays the same as before. If a @PerformanceTestFactory exists, the PerformanceRunner adds all the test case instances returned by the factory to the testObjects list, instead of the test case itself. Optionally, the test cases can implement an IdentifiableTestCase interface, which gives the ability to have custom names for tests running on different instances. The motivation behind this is that a suite can contain test cases that are different logically, but the test case should be able to be parameterized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-2593) Improvement for the Sling performance tools
[ https://issues.apache.org/jira/browse/SLING-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-2593: Fix Version/s: Sling JUnit Performance 1.0.2 Improvement for the Sling performance tools Key: SLING-2593 URL: https://issues.apache.org/jira/browse/SLING-2593 Project: Sling Issue Type: Improvement Components: Testing Reporter: Vazzolla-Popa Cristian-George Assignee: Antonio Sanso Priority: Minor Fix For: Sling JUnit Performance 1.0.2 Attachments: performance_patch_2.patch, report_level_patch.patch, sling_performance_framework_refactoring.patch Added a few improvements to the Sling performance testing tools: 1. Added the possibility to run each test method in a class as a performance test; until now a test was represented by a class (for each new test you had to add a new java class) 2. Added a PerformanceTest annotation that is used to discover the test methods in a java class 3. Added the possibility to provide with the PerformanceTest annotation a few configuration parameters for the test like the warmup time, run time , warm up invocations or run invocations; by default the warmuptime and runtime are used but a user can choose not to count on the time but to prefer setting the number of test invocations that he wants to be made during the test run 4. Created a new maven project that contains only the sling performance tests and left the framework(tool) related part in the base project as we would like to use the framework for performance testing in other projects also 5. Added the possibility to have parameters sent to test suite object, added a before suite and after suite method -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376126#comment-14376126 ] Robert Munteanu edited comment on SLING-4050 at 3/23/15 8:43 PM: - Resolving as fixed ( thanks [~bdelacretaz] for the initial patch ) . Further customisations can be added if needed in different runmodes, but for this issue we're good to go. was (Author: rombert): Resolving as fixed ( thanks [~bdelacre] for the initial patch ) . Further customisations can be added if needed in different runmodes, but for this issue we're good to go. Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4536) exclude HtmlResponse.html from Rat checks
[
https://issues.apache.org/jira/browse/SLING-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-4536.
-
Resolution: Done
r1668729
exclude HtmlResponse.html from Rat checks
-
Key: SLING-4536
URL: https://issues.apache.org/jira/browse/SLING-4536
Project: Sling
Issue Type: Task
Components: Servlets
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
Fix For: Servlets POST 2.3.8
{noformat}
plugin
groupIdorg.apache.rat/groupId
artifactIdapache-rat-plugin/artifactId
configuration
excludes
excludesrc/main/resources/org/apache/sling/servlets/post/HtmlResponse.html/exclude
/excludes
/configuration
/plugin
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-920) Sling Jenkins setup
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376580#comment-14376580
]
Robert Munteanu commented on SLING-920:
---
Adjusted sling-oak-it-1.{6,7} to set -Dsling.run.modes=oak,oak_tar following
the changes for SLING-4050
Sling Jenkins setup
---
Key: SLING-920
URL: https://issues.apache.org/jira/browse/SLING-920
Project: Sling
Issue Type: Task
Components: Testing
Reporter: Bertrand Delacretaz
Use this issue to record changes to the Jenkins setup at
https://builds.apache.org/view/S-Z/view/Sling/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[VOTE] Release Apache Sling Performance Test Utilities 1.0.2
Hi, We solved 7 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327378 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1218 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 1218 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks, Radu
[jira] [Reopened] (SLING-4530) Add .mvn/jvm.config to reactor
[
https://issues.apache.org/jira/browse/SLING-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz reopened SLING-4530:
-
Do we really want/need this? I now get {{Java HotSpot(TM) 64-Bit Server VM
warning: ignoring option MaxPermSize=256m; support was removed in 8.0}} and run
Maven by default with {{MAVEN_OPTS=-Xms1G\ -Xmx4G}} instead of {{-Xmx512m
-XX:MaxPermSize=256m}} from {{.mvn/jvm.config}}.
Add .mvn/jvm.config to reactor
--
Key: SLING-4530
URL: https://issues.apache.org/jira/browse/SLING-4530
Project: Sling
Issue Type: Bug
Components: General
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Maven 3.3.1 has added the possibility of storing the JVM configuration in a
.mvn/jvm.config file ( see [MNG-5767 - project-specific default jvm
options and command line parameters|http://jira.codehaus.org/browse/MNG-5767]
). Those flags will apply to all builds by default.
We should add the flags specified in SLING-443 and SLING-1782 to make sure
that we have everyone building Sling with the required flags OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
Hi, I've started a release thread for org.apache.sling.performance.base at http://sling.markmail.org/thread/m7xyhb6saxfyqs6w. I've also dropped org.apache.sling.scripting.sightly.testing from staging repository 1216 and restaged this artifact at 1219. You can use this UNIX script to download the release and verify the signatures for org.apache.sling.scripting.sightly.testing: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1219 /tmp/sling-staging Thanks, Radu On Mon, Mar 23, 2015 at 7:25 PM, Radu Cotescu r...@apache.org wrote: Hi Robert, It would be better to release that snapshot dependency in order to provide a way to easily test Sightly artifacts. I'll take care of that this evening. Cheers, Radu On Monday, March 23, 2015, Robert Munteanu romb...@apache.org wrote: On Mon, 2015-03-23 at 10:50 -0400, Daniel Klco wrote: org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. Good catch! I assumed the maven release plugin would be banning SNAPSHOTs, but apparently this is not the case ... We can't deploy SNAPSHOT depedencies on Maven Central and we should not as a general rule depend on SNAPSHOTs from releases, as the SNAPSHOTs will at some point go away and make the released artifact invalid. So we either release the org.apache.sling.performance.base artifact and depend on it or drop the org.apache.sling.sightly.testing artifact from the release. Radu? Robert -- Sent with clumsy fingers from a touchscreen
[jira] [Commented] (SLING-2387) OBR at http://sling.apache.org/obr/repository.xml is totally out of date
[ https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376701#comment-14376701 ] Robert Munteanu commented on SLING-2387: [~jebailey] - are there any particular bundles that are out of date? OBR at http://sling.apache.org/obr/repository.xml is totally out of date Key: SLING-2387 URL: https://issues.apache.org/jira/browse/SLING-2387 Project: Sling Issue Type: Bug Reporter: Markus Joschko Priority: Minor It would be quite handy to have the most recent stable bundles of sling available in a bundle repository so that existing installations can easily be updated. However the versions in the existing obr are out of date (way out of date). If there is a way to automate the deployment I might be able to give a hand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
Hi Robert, 1216 contains: org.apache.sling.scripting.sightly org.apache.sling.scripting.sightly.js.provider org.apache.sling.scripting.sightly.repl org.apache.sling.scripting.sightly.testing-content as I've removed org.apache.sling.scripting.sightly.testing, since it was pointing to a snapshot dependency. 1219 contains: org.apache.sling.scripting.sightly.testing, which now points to org.apache.sling.performance.base 1.0.2. Thanks, Radu On Mon, Mar 23, 2015 at 11:37 PM, Robert Munteanu rob...@lmn.ro wrote: On Mon, Mar 23, 2015 at 11:29 PM, Radu Cotescu r...@apache.org wrote: Hi, I've started a release thread for org.apache.sling.performance.base at http://sling.markmail.org/thread/m7xyhb6saxfyqs6w. I've also dropped org.apache.sling.scripting.sightly.testing from staging repository 1216 and restaged this artifact at 1219. You can use this UNIX script to download the release and verify the signatures for org.apache.sling.scripting.sightly.testing: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1219 /tmp/sling-staging So on which repository/artifacts are we voting now? Both 1216 and 1219 seem to be active. Robert Thanks, Radu On Mon, Mar 23, 2015 at 7:25 PM, Radu Cotescu r...@apache.org wrote: Hi Robert, It would be better to release that snapshot dependency in order to provide a way to easily test Sightly artifacts. I'll take care of that this evening. Cheers, Radu On Monday, March 23, 2015, Robert Munteanu romb...@apache.org wrote: On Mon, 2015-03-23 at 10:50 -0400, Daniel Klco wrote: org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. Good catch! I assumed the maven release plugin would be banning SNAPSHOTs, but apparently this is not the case ... We can't deploy SNAPSHOT depedencies on Maven Central and we should not as a general rule depend on SNAPSHOTs from releases, as the SNAPSHOTs will at some point go away and make the released artifact invalid. So we either release the org.apache.sling.performance.base artifact and depend on it or drop the org.apache.sling.sightly.testing artifact from the release. Radu? Robert -- Sent with clumsy fingers from a touchscreen -- Sent from my (old) computer
Jenkins build is back to stable : sling-trunk-1.6 #3208
See https://builds.apache.org/job/sling-trunk-1.6/3208/changes
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
On Mon, Mar 23, 2015 at 11:29 PM, Radu Cotescu r...@apache.org wrote: Hi, I've started a release thread for org.apache.sling.performance.base at http://sling.markmail.org/thread/m7xyhb6saxfyqs6w. I've also dropped org.apache.sling.scripting.sightly.testing from staging repository 1216 and restaged this artifact at 1219. You can use this UNIX script to download the release and verify the signatures for org.apache.sling.scripting.sightly.testing: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1219 /tmp/sling-staging So on which repository/artifacts are we voting now? Both 1216 and 1219 seem to be active. Robert Thanks, Radu On Mon, Mar 23, 2015 at 7:25 PM, Radu Cotescu r...@apache.org wrote: Hi Robert, It would be better to release that snapshot dependency in order to provide a way to easily test Sightly artifacts. I'll take care of that this evening. Cheers, Radu On Monday, March 23, 2015, Robert Munteanu romb...@apache.org wrote: On Mon, 2015-03-23 at 10:50 -0400, Daniel Klco wrote: org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. Good catch! I assumed the maven release plugin would be banning SNAPSHOTs, but apparently this is not the case ... We can't deploy SNAPSHOT depedencies on Maven Central and we should not as a general rule depend on SNAPSHOTs from releases, as the SNAPSHOTs will at some point go away and make the released artifact invalid. So we either release the org.apache.sling.performance.base artifact and depend on it or drop the org.apache.sling.sightly.testing artifact from the release. Radu? Robert -- Sent with clumsy fingers from a touchscreen -- Sent from my (old) computer
[jira] [Resolved] (SLING-4535) discovery: lower warn to info for 'still in isolated mode'
[
https://issues.apache.org/jira/browse/SLING-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-4535.
Resolution: Fixed
fixed (1668731)
discovery: lower warn to info for 'still in isolated mode'
--
Key: SLING-4535
URL: https://issues.apache.org/jira/browse/SLING-4535
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Discovery Impl 1.0.10
Reporter: Stefan Egli
Assignee: Stefan Egli
Fix For: Discovery Impl 1.1.2
The following warn shows up in various situations eg when PropertyProvider
are bound but first voting has not finished yet. This should not be a WARN
but rather an INFO
{code}
WARN [pool-6-thread-14] org.apache.sling.discovery.impl.DiscoveryServiceImpl
handlePotentialTopologyChange: still in isolated mode - cannot send
TOPOLOGY_INIT yet.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-4050. Resolution: Fixed Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[ https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376126#comment-14376126 ] Robert Munteanu commented on SLING-4050: Resolving as fixed ( thanks [~bdelacre] for the initial patch ) . Further customisations can be added if needed in different runmodes, but for this issue we're good to go. Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz Assignee: Robert Munteanu Attachments: SLING-4050.patch It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Scripting Sightly 1.0.0
Hi Robert, It would be better to release that snapshot dependency in order to provide a way to easily test Sightly artifacts. I'll take care of that this evening. Cheers, Radu On Monday, March 23, 2015, Robert Munteanu romb...@apache.org wrote: On Mon, 2015-03-23 at 10:50 -0400, Daniel Klco wrote: org.apache.sling.sightly.testing relies on a SNAPSHOT dependency: dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.performance.base/artifactId version0.0.1-SNAPSHOT/version scopetest/scope /dependency As this is a testing project, I'm not sure if this is a big deal or acceptable. Ideally, if we could make a release of this performance tools it would be good to apply performance tests across all of the scripting languages available in Sling. Good catch! I assumed the maven release plugin would be banning SNAPSHOTs, but apparently this is not the case ... We can't deploy SNAPSHOT depedencies on Maven Central and we should not as a general rule depend on SNAPSHOTs from releases, as the SNAPSHOTs will at some point go away and make the released artifact invalid. So we either release the org.apache.sling.performance.base artifact and depend on it or drop the org.apache.sling.sightly.testing artifact from the release. Radu? Robert -- Sent with clumsy fingers from a touchscreen
Jenkins build became unstable: sling-oak-it-1.6 #427
See https://builds.apache.org/job/sling-oak-it-1.6/427/
[jira] [Created] (SLING-4533) OakResourceListener does not allow to configure the OAK observation queue length
Marc Pfaff created SLING-4533: - Summary: OakResourceListener does not allow to configure the OAK observation queue length Key: SLING-4533 URL: https://issues.apache.org/jira/browse/SLING-4533 Project: Sling Issue Type: Bug Components: JCR, Oak Affects Versions: JCR Resource 2.5.0 Reporter: Marc Pfaff Currently the OakResourceListener does not allow to configure the OAK observation queue length when instantiating the OAK BackgroundObserver. Thus the default queue size of 1000 is used. If the max queue size is reached, OAK seem's to turn the observation in a 'graceful degratation' mode, which leads to a compacted view of observations. Means, not every single observation makes it to the observer no more. From the point of view of the Sling resource changed events, this looks like some events are missing. I would propose to make the OAK observation queue size configurable in order to have the possibility to avoid 'graceful degratation'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.6 #3206
See https://builds.apache.org/job/sling-trunk-1.6/3206/changes
Re: Jenkins build became unstable: sling-oak-it-1.6 #427
The failure probably happened because the launchpad was already initialised and the new oak_tar runmode did not get applied. I wiped out the workspace and triggered another build. Robert On Mon, Mar 23, 2015 at 7:54 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/sling-oak-it-1.6/427/
Jenkins build is still unstable: sling-oak-it-1.6 #428
See https://builds.apache.org/job/sling-oak-it-1.6/428/
[jira] [Updated] (SLING-2387) OBR at http://sling.apache.org/obr/repository.xml is totally out of date
[ https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey updated SLING-2387: -- Attachment: screenshot-1.png OBR at http://sling.apache.org/obr/repository.xml is totally out of date Key: SLING-2387 URL: https://issues.apache.org/jira/browse/SLING-2387 Project: Sling Issue Type: Bug Reporter: Markus Joschko Priority: Minor Attachments: screenshot-1.png It would be quite handy to have the most recent stable bundles of sling available in a bundle repository so that existing installations can easily be updated. However the versions in the existing obr are out of date (way out of date). If there is a way to automate the deployment I might be able to give a hand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
