Preparing to release JCR Base 3.0.6

[Eric Norman]

I'd like to release JCR Base 3.0.6 to unblock work on another issue.

There are currently 2 unresolved/open issues linked to that version in JIRA
( see [1] ).

I don't know the status of the work on those 2 issues.  Are there any
objections to moving those 2 unresolved issues to the next version and
release what is there now as 3.0.6?

1. https://issues.apache.org/jira/projects/SLING/versions/12341119

Regards,
Eric

[jira] [Closed] (SLING-8138) Upgrade to jackrabbit 2.16.x and oak 1.8.x

[Eric Norman (JIRA)]

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

Eric Norman closed SLING-8138.
--

released Testing Sling Mock Oak 2.1.2

> Upgrade to jackrabbit 2.16.x and oak 1.8.x
> --
>
> Key: SLING-8138
> URL: https://issues.apache.org/jira/browse/SLING-8138
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Testing Sling Mock Oak 2.1.0
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Testing Sling Mock Oak 2.1.2
>
>
> In order to test new functionality added in Oak 1.8, the mock-oak module 
> needs to be updated to use the 1.8.x version of oak and the 2.16.x of 
> jackrabbit 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: [RESULT] [VOTE] Release Apache Sling Testing Sling Mock Jackrabbit Oak-based Resource Resolver version 2.1.2

[Stefan Seifert]

>I need someone from the PMC to copy this release to the Sling dist
>directory. Once that is done I will promote this to the central Maven
>repository and update JIRA and the website.

done

stefan

[RESULT] [VOTE] Release Apache Sling Testing Sling Mock Jackrabbit Oak-based Resource Resolver version 2.1.2

[Eric Norman]

Hi,

The vote has passed with the following result :

+1 (binding): Eric Norman, Stefan Seifert, Robert Munteanu, Daniel Klco
+1 (non binding): Jason E. Bailey

I need someone from the PMC to copy this release to the Sling dist
directory. Once that is done I will promote this to the central Maven
repository and update JIRA and the website.

Regards,
Eric

[jira] [Created] (SLING-8171) Adjust https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings to reflect the principal based mapping

[Konrad Windszus (JIRA)]

Konrad Windszus created SLING-8171:
--

 Summary: Adjust 
https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings
 to reflect the principal based mapping
 Key: SLING-8171
 URL: https://issues.apache.org/jira/browse/SLING-8171
 Project: Sling
  Issue Type: Improvement
  Components: Documentation
Reporter: Konrad Windszus
Assignee: Konrad Windszus


The change being introduced by SLING-6963 should be reflected in 
https://sling.apache.org/documentation/the-sling-engine/service-authentication.html#service-user-mappings.
Also it should clearly indicate how to differentiate between principals and jcr 
user ids.

Also the implications like the one outlined in OAK-7952 should be clearly 
mentioned there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [servlets] SLING-8170 - Allow Sling servlets to declare a resource super type

[Konrad Windszus]

I am not sure I do understand 100% your use case:
How are you supposed to do request dispatching to another servlet then? Only in 
case request dispatching is used I see an actual benefit (to only overwrite one 
part of a servlet but not another). There you would need to rely on selectors 
(instead of the script name), right? Maybe you can give a concrete example on 
where you think inheritance of servlets would be useful.
Or is your use case more in the AEM area where dialogs, component definitions, 
... could be reused?

Thanks,
Konrad



> On 11. Dec 2018, at 14:58, Radu Cotescu  wrote:
> 
> Hi,
> 
> I’ve recently opened 2 PRs for Apache Sling API and Apache Sling Servlets 
> Resolver. The goal is the ability to define a way to overlay servlets / 
> delegate to other servlets at runtime [0], similar to what’s already 
> available for scripts. Besides the overlaying functionality, this will allow 
> bundled scripts (optionally precompiled) to be able to delegate rendering to 
> pre-existing servlets / scripts that are not necessarily registered through 
> the new Apache Sling Scripting Bundle Tracker [1].
> 
> Please let me know what you think.
> 
> Regards,
> Radu
> 
> [0] - https://issues.apache.org/jira/browse/SLING-8170 
> 
> [1] - 
> https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker 
> 
> 

Re: [RESULT] [VOTE] Release Apache Sling Servlets Get 2.1.40

[Jason E Bailey]

- Jason

On Tue, Dec 11, 2018, at 11:26 AM, Robert Munteanu wrote:

> Done in r31495. Jason, could you please also update website, Jira, etc?

will do

Re: [RESULT] [VOTE] Release Apache Sling Servlets Get 2.1.40

[Robert Munteanu]

On Tue, 2018-12-11 at 10:31 -0500, Jason E Bailey wrote:
> I will promote this to the central Maven repository. I need someone
> from the PMC to copy this release to the Sling dist directory. 

Done in r31495. Jason, could you please also update website, Jira, etc?

Thanks,

Robert

[jira] [Closed] (SLING-8155) AuthRequestLoginTest and SlingSessionInfoTest fail with org.mozilla.javascript.EvaluatorException: syntax error

[Jason E Bailey (JIRA)]

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

Jason E Bailey closed SLING-8155.
-

> AuthRequestLoginTest and SlingSessionInfoTest fail with 
> org.mozilla.javascript.EvaluatorException: syntax error
> ---
>
> Key: SLING-8155
> URL: https://issues.apache.org/jira/browse/SLING-8155
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Reporter: Robert Munteanu
>Assignee: Jason E Bailey
>Priority: Major
> Fix For: Servlets Get 2.1.40
>
>
> Sometimes after Sling 11 we started getting IT failures does to JS errors 
> when evaluated on the client side, in the ITs:
> {noformat}[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time 
> elapsed: 0.007 s <<< FAILURE! - in 
> org.apache.sling.launchpad.webapp.integrationtest.login.AuthRequestLoginTest
> [ERROR] 
> testForcedLogin(org.apache.sling.launchpad.webapp.integrationtest.login.AuthRequestLoginTest)
>   Time elapsed: 0.007 s  <<< ERROR!
> java.io.IOException: While executing 
> [out.println(data.userID)]:org.mozilla.javascript.EvaluatorException: syntax 
> error (JavascriptEngine#1)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.login.AuthRequestLoginTest.testForcedLogin(AuthRequestLoginTest.java:41)
> Caused by: org.mozilla.javascript.EvaluatorException: syntax error 
> (JavascriptEngine#1)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.login.AuthRequestLoginTest.testForcedLogin(AuthRequestLoginTest.java:41)
> [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.006 
> s <<< FAILURE! - in 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest
> [ERROR] 
> testSessionInfo(org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest)
>   Time elapsed: 0.001 s  <<< ERROR!
> java.io.IOException: While executing [out.println(data.userID + '.' + typeof 
> data.authType)]:org.mozilla.javascript.EvaluatorException: syntax error 
> (JavascriptEngine#1)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest.testSessionInfo(SlingSessionInfoTest.java:35)
> Caused by: org.mozilla.javascript.EvaluatorException: syntax error 
> (JavascriptEngine#1)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest.testSessionInfo(SlingSessionInfoTest.java:35)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[RESULT] [VOTE] Release Apache Sling Servlets Get 2.1.40

[Jason E Bailey]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Daniel Klco, Nicolas Peltier, Oliver Lietz

I will promote this to the central Maven repository. I need someone from the 
PMC to copy this release to the Sling dist directory. 

Thanks
- Jason

On Tue, Dec 4, 2018, at 12:13 PM, Jason E Bailey wrote:
> Hi,
> 
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12344595
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2021/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 2021 /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.
> 
> - Jason

Re: December board report draft

[Jason E Bailey]

Thanks for the link! There is just so much to know about Apache and the rules 
etc.

- Jason

On Tue, Dec 11, 2018, at 4:41 AM, Bertrand Delacretaz wrote:
> Hi,
> 
> On Tue, Dec 11, 2018 at 10:32 AM Robert Munteanu  wrote:
> > ...Depends on the name. Is it presented as an "official" Apache Sling
> > project or is it implied that it is one? If that is the case, this
> > could be an issue...
> 
> http://www.apache.org/foundation/marks/reporting.html#issues has more
> info on this - in general, names like "X for Apache Sling" or "X,
> powered by Apache Sling" are fine, but if they lead to confusion like
> Jason seems to have experienced that's not ok.
> 
> In the vast majority of cases, a friendly reminder from the PMC is
> sufficient for people to change the inappropriate names.
> 
> -Bertrand

Re: [feature-model] Removing features after installation

[David Bosschaert]

Hi Dominik,

On Tue, 11 Dec 2018 at 14:58, Dominik Süß  wrote:

> Hi Karl,
> On Mon, Dec 10, 2018 at 3:15 PM Karl Pauls  wrote:
>
> > Yeah, fwiw, that was the underlying idea - there are no restarts
> > anymore. I guess we might want to consider emphasising this by making
> > it the default to clear the cache on restarts so that you always start
> > from a clean state.
> >
>
> I don't know if this really is the case. You might want to preprovision the
> immutable state and still stop & start without any state change.
> This does allow extremely quickly roling out clones of an immutable
> instance in a containerized environment.
>
>
For situations like this, would you not use Docker to build up your
pre-provisioned state. For example based on the Feature Model.
Then you keep that state in a docker image.
Subsequently you can start (and stop) Docker containers based on that image.

What would the Feature Model need to add for this?

Best regards,

David

Re: [VOTE] Release Apache Sling Testing Sling Mock Jackrabbit Oak-based Resource Resolver version 2.1.2

[Daniel Klco]

+1

On Tue, Dec 11, 2018 at 6:53 AM Robert Munteanu  wrote:

> On Thu, 2018-12-06 at 20:36 -0800, Eric Norman wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
>

Re: [feature-model] Removing features after installation

[Dominik Süß]

Hi Karl,
On Mon, Dec 10, 2018 at 3:15 PM Karl Pauls  wrote:

> Yeah, fwiw, that was the underlying idea - there are no restarts
> anymore. I guess we might want to consider emphasising this by making
> it the default to clear the cache on restarts so that you always start
> from a clean state.
>

I don't know if this really is the case. You might want to preprovision the
immutable state and still stop & start without any state change.
This does allow extremely quickly roling out clones of an immutable
instance in a containerized environment.

Cheers
Dominik

[servlets] SLING-8170 - Allow Sling servlets to declare a resource super type

[Radu Cotescu]

Hi,

I’ve recently opened 2 PRs for Apache Sling API and Apache Sling Servlets 
Resolver. The goal is the ability to define a way to overlay servlets / 
delegate to other servlets at runtime [0], similar to what’s already available 
for scripts. Besides the overlaying functionality, this will allow bundled 
scripts (optionally precompiled) to be able to delegate rendering to 
pre-existing servlets / scripts that are not necessarily registered through the 
new Apache Sling Scripting Bundle Tracker [1].

Please let me know what you think.

Regards,
Radu

[0] - https://issues.apache.org/jira/browse/SLING-8170 

[1] - https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker 

[jira] [Updated] (SLING-8170) Allow Sling servlets to declare a resource super type

[Radu Cotescu (JIRA)]

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

Radu Cotescu updated SLING-8170:

Fix Version/s: API 2.20.0
   Servlets Resolver 2.5.0

> Allow Sling servlets to declare a resource super type
> -
>
> Key: SLING-8170
> URL: https://issues.apache.org/jira/browse/SLING-8170
> Project: Sling
>  Issue Type: Improvement
>  Components: API, Servlets
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.5.0, API 2.20.0
>
>
> In Sling scripts and servlets are equal [0]. However, currently a servlet 
> cannot declare a resource super type property, in order to allow delegation / 
> overlaying at runtime to another servlet, similar to how component scripts 
> can do it through the {{sling:resourceSuperType}} optional property.
> Adding support for another registration property - 
> {{sling.servlet.resourceSuperType}} - that accepts a String as value would 
> allow to introduce a backwards compatible overlaying and inheritance 
> capability. This property should only be considered for the registration 
> together with the {{sling.servlet.resourceTypes}}.
> [0] - 
> https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#fundamental-scripts-and-servlets-are-equal



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-8170) Allow Sling servlets to declare a resource super type

[Radu Cotescu (JIRA)]

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

Radu Cotescu updated SLING-8170:

Affects Version/s: (was: API 2.20.0)
   (was: Servlets Resolver 2.5.0)

> Allow Sling servlets to declare a resource super type
> -
>
> Key: SLING-8170
> URL: https://issues.apache.org/jira/browse/SLING-8170
> Project: Sling
>  Issue Type: Improvement
>  Components: API, Servlets
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.5.0, API 2.20.0
>
>
> In Sling scripts and servlets are equal [0]. However, currently a servlet 
> cannot declare a resource super type property, in order to allow delegation / 
> overlaying at runtime to another servlet, similar to how component scripts 
> can do it through the {{sling:resourceSuperType}} optional property.
> Adding support for another registration property - 
> {{sling.servlet.resourceSuperType}} - that accepts a String as value would 
> allow to introduce a backwards compatible overlaying and inheritance 
> capability. This property should only be considered for the registration 
> together with the {{sling.servlet.resourceTypes}}.
> [0] - 
> https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#fundamental-scripts-and-servlets-are-equal



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-8170) Allow Sling servlets to declare a resource super type

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-8170:
---

 Summary: Allow Sling servlets to declare a resource super type
 Key: SLING-8170
 URL: https://issues.apache.org/jira/browse/SLING-8170
 Project: Sling
  Issue Type: Improvement
  Components: API, Servlets
Affects Versions: Servlets Resolver 2.5.0, API 2.20.0
Reporter: Radu Cotescu
Assignee: Radu Cotescu


In Sling scripts and servlets are equal [0]. However, currently a servlet 
cannot declare a resource super type property, in order to allow delegation / 
overlaying at runtime to another servlet, similar to how component scripts can 
do it through the {{sling:resourceSuperType}} optional property.

Adding support for another registration property - 
{{sling.servlet.resourceSuperType}} - that accepts a String as value would 
allow to introduce a backwards compatible overlaying and inheritance 
capability. This property should only be considered for the registration 
together with the {{sling.servlet.resourceTypes}}.

[0] - 
https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#fundamental-scripts-and-servlets-are-equal



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Support for ACE Restrictions with jackrabbit.accessmanager REST

[Robert Munteanu]

On Thu, 2018-12-06 at 20:56 -0800, Eric Norman wrote:
> Hi Robert,
> 
> Ok, I will give it a try.  Please advise if I mess something up.
> 
> Regards,
> Eric

Everything turned up fine from the first try, that's nice!

Robert

> 
> On Mon, Dec 3, 2018 at 1:39 AM Robert Munteanu 
> wrote:
> 
> > Hi Eric,
> > 
> > On Tue, 2018-11-27 at 17:10 -0800, Eric Norman wrote:
> > > Would someone be able to review the changes done for those issues
> > > and
> > > if
> > > there are no objections to the code changes assist with releasing
> > > those two
> > > bundles?  I've never done that before and I not sure I even have
> > > sufficient
> > > rights to do it.
> > 
> > As a committer you are able to start a release vote, you only need
> > a
> > PMC member at the end to promote the artifacts to dist.apache.org ,
> > see
> > [1] for more details.
> > 
> > In case you would like someone else to run the release feel free to
> > ask
> > when ready, but I would suggest to try it yourself since you have
> > sufficient rights.
> > 
> > Thanks,
> > 
> > Robert
> > 
> > [1]:
> > http://sling.apache.org/documentation/development/release-management.html
> > 
> > 

Re: [VOTE] Release Apache Sling Testing Sling Mock Jackrabbit Oak-based Resource Resolver version 2.1.2

[Robert Munteanu]

On Thu, 2018-12-06 at 20:36 -0800, Eric Norman wrote:
> Please vote to approve this release:

+1

Robert


signature.asc
Description: This is a digitally signed message part

Re: December board report draft

[Bertrand Delacretaz]

Hi,

On Tue, Dec 11, 2018 at 10:32 AM Robert Munteanu  wrote:
> ...Depends on the name. Is it presented as an "official" Apache Sling
> project or is it implied that it is one? If that is the case, this
> could be an issue...

http://www.apache.org/foundation/marks/reporting.html#issues has more
info on this - in general, names like "X for Apache Sling" or "X,
powered by Apache Sling" are fine, but if they lead to confusion like
Jason seems to have experienced that's not ok.

In the vast majority of cases, a friendly reminder from the PMC is
sufficient for people to change the inappropriate names.

-Bertrand

Re: December board report draft

[Robert Munteanu]

Hi Jason,

On Mon, 2018-12-10 at 11:58 -0500, Jason E Bailey wrote:
> Got a question. Sling has the TM mark against it. I ran across
> someone on NPM who is making stuff for Sling, which is cool, but he
> also has a Sling name which initially made me think it was part of
> the dev team.
> 
> Is that an issue?

Depends on the name. Is it presented as an "official" Apache Sling
project or is it implied that it is one? If that is the case, this
could be an issue.

Thanks,

Robert

[jira] [Assigned] (SLING-8169) Bundle Import/Export Analyser needs to take API Regions into account

[David Bosschaert (JIRA)]

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

David Bosschaert reassigned SLING-8169:
---

Assignee: David Bosschaert

> Bundle Import/Export Analyser needs to take API Regions into account
> 
>
> Key: SLING-8169
> URL: https://issues.apache.org/jira/browse/SLING-8169
> Project: Sling
>  Issue Type: New Feature
>  Components: Feature Model
>Reporter: David Bosschaert
>Assignee: David Bosschaert
>Priority: Major
>
> The Bundle Import/Export analyser needs to take into account that certain 
> package may not be visible because of the API Regions. It needs to be 
> extended to support this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)