[jira] [Resolved] (SLING-7165) CAConfig Impl: Potential data loss when saving multiple nested configuration lists

[ https://issues.apache.org/jira/browse/SLING-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-7165. --- Resolution: Fixed Completed: At revision: 1810138 > CAConfig Impl: Potential data loss

Re: Ok to replace sling.apache.org with the new JBake-generated site ?

+1 Thanks for driving this Bertrand! On Fri, Sep 29, 2017 at 12:50 PM Julian Sedding wrote: > Thanks for the great work Bertrand! That should make contributing > documentation simpler & more transparent. > > Regards > Julian > > On Thu, Sep 28, 2017 at 8:21 PM, Stefan

Re: Ok to replace sling.apache.org with the new JBake-generated site ?

Thanks for the great work Bertrand! That should make contributing documentation simpler & more transparent. Regards Julian On Thu, Sep 28, 2017 at 8:21 PM, Stefan Seifert wrote: > great, thanks for all the work! > > btw. on github, there is still a remnant oft he

Re: Deprecate Commons Testing?

+ 1 & +1 to stefan's suggestions Regards Julian On Thu, Sep 28, 2017 at 6:07 PM, Stefan Seifert wrote: > +1 > > perhaps we can start making a new release with all classes deprecated, and > updating pom references to this. > then it's easier to find it's usage and

[jira] [Created] (SLING-7165) CAConfig Impl: Potential data loss when saving multiple nested configuration lists

Stefan Seifert created SLING-7165: - Summary: CAConfig Impl: Potential data loss when saving multiple nested configuration lists Key: SLING-7165 URL: https://issues.apache.org/jira/browse/SLING-7165

Re: [RT] Updates to the provisioning model - run mode

Stefan Seifert wrote> >> * No support for run modes in the model - run modes can be modeled >> through separate features > > is there a plan to generally remove the "run mode" concept from sling - or > just not express it in the feature model? > if it is kept - where come the features and run

RE: [RT] Updates to the provisioning model - maven coordinates

>Carsten Ziegeler wrote> > >> Thanks for the pointer Stefan. We should definitely support this, I'll >> update the code. >> For some reason we have based the provisioning model and therefore the >> feature model on >> https://ops4j1.jira.com/wiki/spaces/paxurl/pages/3833866/Mvn+Protocol >> > >I

RE: [RT] Updates to the provisioning model - run mode

>* No support for run modes in the model - run modes can be modeled >through separate features is there a plan to generally remove the "run mode" concept from sling - or just not express it in the feature model? if it is kept - where come the features and run modes together? stefan

Re: [RT] Updates to the provisioning model - maven coordinates

Carsten Ziegeler wrote> > Thanks for the pointer Stefan. We should definitely support this, I'll > update the code. > For some reason we have based the provisioning model and therefore the > feature model on > https://ops4j1.jira.com/wiki/spaces/paxurl/pages/3833866/Mvn+Protocol > I think the

Re: [RT] Updates to the provisioning model - maven coordinates

Stefan Seifert wrote> >> One minor thing, the current proposal uses the Maven coordinates to >> describe artifacts. It's using the path part of a maven url, so >> basically group id, artifact id, version are separated by a slash. It >> seems that the notation of separating these things by a colon

RE: [VOTE] Release Apache Sling Thread Support 3.2.10

+1 all tests running fine on windows. stefan

RE: [RT] Updates to the provisioning model - maven coordinates

>One minor thing, the current proposal uses the Maven coordinates to >describe artifacts. It's using the path part of a maven url, so >basically group id, artifact id, version are separated by a slash. It >seems that the notation of separating these things by a colon is more >common/natural. And

Re: sling-site git commit: Update README

On Fri, Sep 29, 2017 at 3:10 PM, Carsten Ziegeler wrote: > ...What exactly does "sync the `target/sling-site-*` folder to the > `asf-site` branch" mean?... I have put suggested commands at https://github.com/apache/sling-site -Bertrand

[website] tag support added

Hi, Start at http://sling.apache.org/tags/core.html for example. I have added an initial set of tags to all pages, just did a quick pass, feel free to tweak! -Bertrand

Re: sling-site git commit: Update README

 What exactly does "sync the `target/sling-site-*` folder to the `asf-site` branch" mean? It would be great to simply have the commands listed there to do so. Regards Carsten Bertrand Delacretaz wrote > Repository: sling-site > Updated Branches: > refs/heads/master 9de648ff4 -> b08c52ab6 >

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

[ https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185731#comment-16185731 ] Ian Boston commented on SLING-7140: --- Configuration information

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

[ https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185711#comment-16185711 ] Ian Boston commented on SLING-7140: --- Pull request: https://github.com/apache/sling/pull/252 This

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

[ https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185709#comment-16185709 ] ASF GitHub Bot commented on SLING-7140: --- GitHub user ieb opened a pull request:

[GitHub] sling pull request #252: SLING-7140 Support redirects to URLs provided by th...

GitHub user ieb opened a pull request: https://github.com/apache/sling/pull/252 SLING-7140 Support redirects to URLs provided by the underlying datastore. This pull request contains API and pom changes which is why I am not committing it directly myself. It should be squashed

FIY, requested move of sling-site repo to Gitbox

Hi, That's at https://issues.apache.org/jira/browse/INFRA-15190 - it would allow us to see how that works before migrating the rest to Git. IIUC all committers will need to visite https://gitbox.apache.org/setup/ to link their Apache and Github accounts. -Bertrand

Re: Website ToC considers only h2 and h3

On Fri, Sep 29, 2017 at 12:09 PM, Konrad Windszus wrote: > I just pushed the change in > https://git-wip-us.apache.org/repos/asf?p=sling-site.git;a=commit;h=9de648ff47e1bb0ad6c8309870fca238097a809f. Thanks, it's live now. -Bertrand

[jira] [Commented] (SLING-7140) Support redirects to URLs provided by the underlying datastore.

[ https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185668#comment-16185668 ] Ian Boston commented on SLING-7140: --- Update from testing, also reported in Oak Tested against Sling

Re: Website ToC considers only h2 and h3

I just pushed the change in https://git-wip-us.apache.org/repos/asf?p=sling-site.git;a=commit;h=9de648ff47e1bb0ad6c8309870fca238097a809f. > On 29. Sep 2017, at 11:38, Bertrand Delacretaz wrote: > > On Fri, Sep 29, 2017 at 11:30 AM, Konrad Windszus

Re: Website ToC considers only h2 and h3

On Fri, 2017-09-29 at 11:38 +0200, Bertrand Delacretaz wrote: > On Fri, Sep 29, 2017 at 11:30 AM, Konrad Windszus > wrote: > > ... Do you want me to propose something or are you planning to > > migrate the Git repo to gitbox soon?.. > > If you can implement what you suggest that

Re: Website ToC considers only h2 and h3

Currently the MD files either start the explicit headlines with an h1 (https://github.com/apache/sling-site/blob/master/src/main/jbake/content/documentation/development/jsr-305.md) or with an h2 (e.g.

[jira] [Commented] (SLING-7158) API changes review for Sling

[ https://issues.apache.org/jira/browse/SLING-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185564#comment-16185564 ] Robert Munteanu commented on SLING-7158: Thanks for this report. Apache Sling is a heavy user of

[jira] [Resolved] (SLING-7158) API changes review for Sling

[ https://issues.apache.org/jira/browse/SLING-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7158. Resolution: Not A Bug > API changes review for Sling > > >

[GitHub] sling-site pull request #1: TODO does commit to github work?

Github user bdelacretaz closed the pull request at: https://github.com/apache/sling-site/pull/1 ---

[GitHub] sling-site issue #1: TODO does commit to github work?

Github user bdelacretaz commented on the issue: https://github.com/apache/sling-site/pull/1 Looks like we need to move to gitbox to be able to merge PRs from github, will look at that. ---

[GitHub] sling-site pull request #1: TODO does commit to github work?

GitHub user bdelacretaz opened a pull request: https://github.com/apache/sling-site/pull/1 TODO does commit to github work? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bdelacretaz/sling-site patch-1 Alternatively you can

Website ToC considers only h2 and h3

Hi, Konrad Windszus wrote: > What is the reason why the selector at > https://github.com/apache/sling-site/blob/f7d38e20d4576a37413fb3d31a28060e8dc0ac60/src/main/jbake/templates/page.tpl#L49 > only lists h2 and h3? Omitting h1 avoids duplicating the page title in the ToC, and stopping at h3

[GitHub] sling pull request #131: Documented the internals of Sling Event, with help ...

Github user asfgit closed the pull request at: https://github.com/apache/sling/pull/131 ---

[jira] [Resolved] (SLING-6955) Convert Sling website to JBake and gitpubsub

[ https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-6955. Resolution: Fixed http://sling.apache.org/ is now generated from

[jira] [Resolved] (SLING-7132) No longer use the animal-sniffer-plugin with JDK >= 9

[ https://issues.apache.org/jira/browse/SLING-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7132. Resolution: Fixed Fix Version/s: Parent 33 Resolved in

[jira] [Created] (SLING-7164) Set up the sling aggregtor repository

Robert Munteanu created SLING-7164: -- Summary: Set up the sling aggregtor repository Key: SLING-7164 URL: https://issues.apache.org/jira/browse/SLING-7164 Project: Sling Issue Type: Sub-task

[jira] [Updated] (SLING-7164) Set up the sling aggregator repository

[ https://issues.apache.org/jira/browse/SLING-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7164: --- Summary: Set up the sling aggregator repository (was: Set up the sling aggregtor repository)

Re: Git migration - final checks

Hi Konrad. On Fri, 2017-09-29 at 10:06 +0200, Konrad Windszus wrote: > Just one thing: I am wondering why commits which I have done do not > have a clickable author information, in contrast to the ones from > Karl or from Oli (can be observed in https://github.com/not-sling/sli >

[RT] Updates to the provisioning model

Hi, as some of you might already have seen or heard during adaptTo, the whiteboard contains a new feature based model at [1] which is intended to be a better provisioning model. The repository at [1] contains a readme which details the reasons and is a basic description of the approach. But I

Re: Git migration - final checks

Just one thing: I am wondering why commits which I have done do not have a clickable author information, in contrast to the ones from Karl or from Oli (can be observed in https://github.com/not-sling/sling-org.apache.sling.validation.core/commits/master) Where is the author information coming

Git migration - final checks

Hi, tldr: please test the test-migrated git repos, we'll migrate soon The git migration is almost ready to go. We're waiting for infra to reply on how to activate the transition but otherwise we're basically good to go. I'd like to point you again to our wiki page where the transition is

[jira] [Closed] (SLING-7092) Stop using port 8888 as a default for testing

[ https://issues.apache.org/jira/browse/SLING-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7092. -- > Stop using port as a default for testing > - > >

[jira] [Closed] (SLING-7060) Allow running a test only if a certain bundle is present at a certain version

[ https://issues.apache.org/jira/browse/SLING-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7060. -- > Allow running a test only if a certain bundle is present at a certain version >

[jira] [Closed] (SLING-7101) Teleporter tests fail on Java 9 - java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter

[ https://issues.apache.org/jira/browse/SLING-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7101. -- > Teleporter tests fail on Java 9 - java.lang.NoClassDefFoundError: >

[jira] [Closed] (SLING-7128) slingstart-maven-plugin should respect JAVA_HOME when set

[ https://issues.apache.org/jira/browse/SLING-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7128. -- > slingstart-maven-plugin should respect JAVA_HOME when set >

[jira] [Closed] (SLING-7083) The StopMojo should block until the process is finished

[ https://issues.apache.org/jira/browse/SLING-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7083. -- > The StopMojo should block until the process is finished >

[jira] [Closed] (SLING-7137) Scripting web console plugins no longer listed

[ https://issues.apache.org/jira/browse/SLING-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7137. -- > Scripting web console plugins no longer listed > -- >

[jira] [Closed] (SLING-7136) Scripting variables web console plugin lists 'all' option for each scripting engine

[ https://issues.apache.org/jira/browse/SLING-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7136. -- > Scripting variables web console plugin lists 'all' option for each scripting > engine >

[jira] [Closed] (SLING-7138) Some web console plugins in the 'Sling' category don't appear

[ https://issues.apache.org/jira/browse/SLING-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7138. -- > Some web console plugins in the 'Sling' category don't appear >

[jira] [Closed] (SLING-6737) Migrate to OSGi R6 annotations

[ https://issues.apache.org/jira/browse/SLING-6737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6737. -- > Migrate to OSGi R6 annotations > -- > > Key:

[jira] [Closed] (SLING-7139) ScriptEngineManagerFactory does not register ScriptEngineFactory references

[ https://issues.apache.org/jira/browse/SLING-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7139. -- > ScriptEngineManagerFactory does not register ScriptEngineFactory references >

[jira] [Closed] (SLING-6724) Scripting core build fails with "ServiceLookup gave up" during tests

[ https://issues.apache.org/jira/browse/SLING-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6724. -- > Scripting core build fails with "ServiceLookup gave up" during tests >

[jira] [Closed] (SLING-7091) Label and value are interchanged for queue type

[ https://issues.apache.org/jira/browse/SLING-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7091. -- > Label and value are interchanged for queue type > ---

[RESULT] [VOTE] Release Apache Sling Scripting Core implementation 2.0.48, Apache Event Support 4.2.8, Apache Sling SlingStart Maven Plugin 1.7.10, Apache Sling JUnit Tests Teleporter 1.0.16, Apache S

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Carsten Ziegeler, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks all for voting. Robert

Re: [VOTE] Release Apache Sling Thread Support 3.2.10

+1 Robert Munteanu wrote > > Hi, > > We solved 6 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12335535 > > 1 issue in this version is still open as it affects other modules as > well, but for Commons Threads the fix has been applied. > > Staging

Re: [VOTE] Release Apache Sling Scripting Core implementation 2.0.48, Apache Event Support 4.2.8, Apache Sling SlingStart Maven Plugin 1.7.10, Apache Sling JUnit Tests Teleporter 1.0.16, Apache Sling

+1 Robert Munteanu wrote > Anyone else? > > Robert > > On Mon, 2017-09-25 at 13:50 +0200, Robert Munteanu wrote: >> Hi, >> >> This is a catch-all release vote for some modules I saw had changes >> but >> no releases. Due to a network hiccup they are split into 2 release >> repositories. >> >>