RE: [VOTE] Release Apache Sling JCR Jackrabbit Access Manager version 4.0.2

2024-01-11 Thread Stefan Seifert 
+1

stefan

Re: [VOTE] Release Apache Sling JCR Jackrabbit Access Manager version 4.0.2

2024-01-11 Thread Eric Norman 
+1 for me

We still need two more binding vote for this one.  Please review and
provide a vote if you are a PMC member and have the time.

Regards,
Eric

On Mon, Jan 8, 2024 at 4:02 PM Eric Norman  wrote:

> Hi,
>
> We solved 1 issues in this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353756=Text
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2827/
>
> You can use this UNIX script to download the release and verify the
> signatures:
>
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 2827 /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.
>

Re: Sling Johnzon Wrapper & Jakarta JSON

2024-01-11 Thread Eric Norman 
For the record, I am not saying this change is good or bad.  However, no
one responded to my feedback which doesn't feel like community consensus to
me.  No vote was taken, it was just done how Carsten wanted it to be done.

Regards,
Eric

On Thu, Jan 11, 2024 at 6:10 AM Robert Munteanu  wrote:

> For the record:
>
> - starting with
>
> https://github.com/apache/sling-org-apache-sling-starter/commit/31e6d31de2ddbb740b553c9c6775e021b5b1d57b
> we are using our own Johnzon wrapper, which does not need the SPIFly
> mediator
> - the SPIFly mediator is still present as it's needed by the Groovy
> bundles
>
> Overall a good balance IMO, thanks Carsten for making the changes.
>
> Robert
>
> On Mon, 2023-11-20 at 15:25 -0800, Eric Norman wrote:
> > Hi Carsten,
> >
> > For me, requiring a service loader mediator isn't a deal breaker.
> > There
> > are other parts of my projects that already require it to be there.
> > The
> > configuration setup is a one time thing and the runtime overhead
> > appears to
> > be insignificant.
> >
> > For example,
> >
> >1. Jetty - The "light" classifier of the
> > org.apache.felix.http.jetty
> >bundle requires the use of the ServiceLoader to find services
> > provided by
> >the various jetty* bundles
> >2. SLING-11906 
> > -
> >SLF4j 2.x uses the ServiceLoader to locate the logging
> > implementation.  So
> >any bundles that have migrated to slf4j 2.x (for example logback
> > 1.3+, tika
> >2.5+ and jetty 10+) would require a serviceloader mediator as
> > well.
> >
> >
> > Regards,
> > Eric
> >
> > On Mon, Nov 20, 2023 at 12:57 AM Carsten Ziegeler
> > 
> > wrote:
> >
> > > I think the downside of all of these solutions is that they all
> > > require
> > > service loader support - which drags in a lot of other stuff.
> > > We should try to convince the johnzon community to remove the hard
> > > requirement on serviceloader - it doesn't really make sense in this
> > > case. and then we would have an apache, dependency free
> > > implementation.
> > >
> > > To avoid all those dependencies I switched to
> > > "org.glassfish:jakarta.json:2.0.1" for my projects. Its older, but
> > > works
> > > and does not require service loader or anything else at all.
> > >
> > > Regards
> > > Carsten
> > >
> > > On 17.11.2023 20:37, Eric Norman wrote:
> > > > Is the johnzon 2.x implementation better than the parsson library
> > > > that we
> > > > are already including in the starter?
> > > >
> > > > I've just been switching the geronimo-json_1.0_spec and johnzon-
> > > > core
> > > > dependencies to these:
> > > >
> > > >  
> > > >  
> > > >  jakarta.json
> > > >  jakarta.json-api
> > > >  2.1.1
> > > >  provided
> > > >  
> > > >
> > > >   > > Carsten Ziegeler
> > > Adobe
> > > cziege...@apache.org
> > >
>
>

Re: [PR] SLING-11836 : Add Jakarta JSON support to the Sling Starter [sling-org-apache-sling-starter]

2024-01-11 Thread via GitHub 


rombert merged PR #296:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/296


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] SLING-11836 : Add Jakarta JSON support to the Sling Starter [sling-org-apache-sling-starter]

2024-01-11 Thread via GitHub 


rombert opened a new pull request, #296:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/296

   Remove org.apache.aries.spifly.auto.* framework properties that are no 
longer in use after commit 31e6d31.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Sling Johnzon Wrapper & Jakarta JSON

2024-01-11 Thread Robert Munteanu 
For the record:

- starting with
https://github.com/apache/sling-org-apache-sling-starter/commit/31e6d31de2ddbb740b553c9c6775e021b5b1d57b
we are using our own Johnzon wrapper, which does not need the SPIFly
mediator
- the SPIFly mediator is still present as it's needed by the Groovy
bundles

Overall a good balance IMO, thanks Carsten for making the changes.

Robert

On Mon, 2023-11-20 at 15:25 -0800, Eric Norman wrote:
> Hi Carsten,
> 
> For me, requiring a service loader mediator isn't a deal breaker. 
> There
> are other parts of my projects that already require it to be there. 
> The
> configuration setup is a one time thing and the runtime overhead
> appears to
> be insignificant.
> 
> For example,
> 
>    1. Jetty - The "light" classifier of the
> org.apache.felix.http.jetty
>    bundle requires the use of the ServiceLoader to find services
> provided by
>    the various jetty* bundles
>    2. SLING-11906 
> -
>    SLF4j 2.x uses the ServiceLoader to locate the logging
> implementation.  So
>    any bundles that have migrated to slf4j 2.x (for example logback
> 1.3+, tika
>    2.5+ and jetty 10+) would require a serviceloader mediator as
> well.
> 
> 
> Regards,
> Eric
> 
> On Mon, Nov 20, 2023 at 12:57 AM Carsten Ziegeler
> 
> wrote:
> 
> > I think the downside of all of these solutions is that they all
> > require
> > service loader support - which drags in a lot of other stuff.
> > We should try to convince the johnzon community to remove the hard
> > requirement on serviceloader - it doesn't really make sense in this
> > case. and then we would have an apache, dependency free
> > implementation.
> > 
> > To avoid all those dependencies I switched to
> > "org.glassfish:jakarta.json:2.0.1" for my projects. Its older, but
> > works
> > and does not require service loader or anything else at all.
> > 
> > Regards
> > Carsten
> > 
> > On 17.11.2023 20:37, Eric Norman wrote:
> > > Is the johnzon 2.x implementation better than the parsson library
> > > that we
> > > are already including in the starter?
> > > 
> > > I've just been switching the geronimo-json_1.0_spec and johnzon-
> > > core
> > > dependencies to these:
> > > 
> > >  
> > >  
> > >  jakarta.json
> > >  jakarta.json-api
> > >  2.1.1
> > >  provided
> > >  
> > > 
> > >   > Carsten Ziegeler
> > Adobe
> > cziege...@apache.org
> >

Re: [PR] chore(deps): update dependency org.apache.jackrabbit:jackrabbit-jcr-commons to v2.20.14 [sling-org-apache-sling-starter]

2024-01-11 Thread via GitHub 


rombert merged PR #294:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/294


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] chore(deps): update dependency org.apache.sling:org.apache.sling.commons.johnzon to v2 [sling-org-apache-sling-starter]

2024-01-11 Thread via GitHub 


renovate-bot opened a new pull request, #295:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/295

   [![Mend 
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)
   
   This PR contains the following updates:
   
   | Package | Change | Age | Adoption | Passing | Confidence |
   |---|---|---|---|---|---|
   | 
[org.apache.sling:org.apache.sling.commons.johnzon](https://sling.apache.org) 
([source](https://togithub.com/apache/sling-org-apache-sling-commons-johnzon)) 
| `1.2.16` -> `2.0.0` | 
[![age](https://developer.mend.io/api/mc/badges/age/maven/org.apache.sling:org.apache.sling.commons.johnzon/2.0.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![adoption](https://developer.mend.io/api/mc/badges/adoption/maven/org.apache.sling:org.apache.sling.commons.johnzon/2.0.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![passing](https://developer.mend.io/api/mc/badges/compatibility/maven/org.apache.sling:org.apache.sling.commons.johnzon/1.2.16/2.0.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.apache.sling:org.apache.sling.commons.johnzon/1.2.16/2.0.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 |
   
   ---
   
   ### Configuration
   
    **Schedule**: Branch creation - At any time (no schedule defined), 
Automerge - At any time (no schedule defined).
   
    **Automerge**: Disabled by config. Please merge this manually once you are 
satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry 
checkbox.
   
    **Ignore**: Close this PR and you won't be reminded about this update 
again.
   
   ---
   
- [ ] If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR has been generated by [Mend 
Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository 
job log 
[here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter).
   

   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[PR] chore(deps): update dependency org.apache.jackrabbit:jackrabbit-jcr-commons to v2.20.14 [sling-org-apache-sling-starter]

2024-01-11 Thread via GitHub 


renovate-bot opened a new pull request, #294:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/294

   [![Mend 
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)
   
   This PR contains the following updates:
   
   | Package | Change | Age | Adoption | Passing | Confidence |
   |---|---|---|---|---|---|
   | 
[org.apache.jackrabbit:jackrabbit-jcr-commons](http://jackrabbit.apache.org/) | 
`2.20.13` -> `2.20.14` | 
[![age](https://developer.mend.io/api/mc/badges/age/maven/org.apache.jackrabbit:jackrabbit-jcr-commons/2.20.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![adoption](https://developer.mend.io/api/mc/badges/adoption/maven/org.apache.jackrabbit:jackrabbit-jcr-commons/2.20.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![passing](https://developer.mend.io/api/mc/badges/compatibility/maven/org.apache.jackrabbit:jackrabbit-jcr-commons/2.20.13/2.20.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.apache.jackrabbit:jackrabbit-jcr-commons/2.20.13/2.20.14?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 |
   
   ---
   
   ### Configuration
   
    **Schedule**: Branch creation - At any time (no schedule defined), 
Automerge - At any time (no schedule defined).
   
    **Automerge**: Disabled by config. Please merge this manually once you are 
satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry 
checkbox.
   
    **Ignore**: Close this PR and you won't be reminded about this update 
again.
   
   ---
   
- [ ] If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR has been generated by [Mend 
Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository 
job log 
[here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter).
   

   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (SLING-12226) Support continuous incoming distributions in subscriber readiness

2024-01-11 Thread Christian Schneider (Jira) 
Christian Schneider created SLING-12226:
---

 Summary: Support continuous incoming distributions in subscriber 
readiness
 Key: SLING-12226
 URL: https://issues.apache.org/jira/browse/SLING-12226
 Project: Sling
  Issue Type: Improvement
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: Content Distribution Journal Core 0.3.0


Refine readiness check for subscriber to also cover case of continuous incoming 
distributions.
If there are continuous incoming distributions then the readiness checks will 
only report ready after the fallback time of 5 minutes.
Jörg proposed to also have a check how old distribution messages are. If they 
are new enough we should report ready.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)