Carsten Ziegeler created SLING-6792:
---
Summary: Attached provisioning model should be the raw model
Key: SLING-6792
URL: https://issues.apache.org/jira/browse/SLING-6792
Project: Sling
Issue
Hi,
We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12339751
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1687/
You can use this UNIX script to download the release and verify the
signatures:
http://svn.apach
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6792.
-
Resolution: Fixed
Fixed in rev 1792698
> Attached provisioning model should be the raw mo
It seems option 2 is our favorite here:
> 2) Release the new api as 2.0 under a different symbolic name allowing
> our users to have new and old side by side. In that case we would need
> to deprecate 1.x and users should upgrade over time.
>
Now, I personally still think we should not add a new
Carsten Ziegeler wrote
> It seems option 2 is our favorite here:
>> 2) Release the new api as 2.0 under a different symbolic name allowing
>> our users to have new and old side by side. In that case we would need
>> to deprecate 1.x and users should upgrade over time.
>>
>
> Now, I personally stil
+1 (non binding)
2017-04-26 9:03 GMT+02:00 Carsten Ziegeler :
> Hi,
>
> We solved 2 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12339751
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1687/
>
> You can use this
+1
Cheers,
Stefan
On 26/04/17 09:03, "Carsten Ziegeler" wrote:
>Hi,
>
>We solved 2 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12339751
>
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1687/
>
>You can use this UN
+1
[
https://issues.apache.org/jira/browse/SLING-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-6700:
--
Fix Version/s: Commons Johnzon 1.0.0
> Implement johnzon bundle
>
>
>
Hi,
This is the first release (1 issue):
https://issues.apache.org/jira/browse/SLING/fixforversion/12340459
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1688/
You can use this UNIX script to download the release and verify the signatures:
http://svn.apach
+1
[
https://issues.apache.org/jira/browse/SLING-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-5387:
---
Assignee: Carsten Ziegeler
> Provide support for running singleton jobs on non leader
[
https://issues.apache.org/jira/browse/SLING-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984393#comment-15984393
]
Carsten Ziegeler commented on SLING-5387:
-
I think there are four scenarios:
a) an
+1
regards,
Karl
On Wed, Apr 26, 2017 at 10:43 AM, Stefan Seifert wrote:
> Hi,
>
> This is the first release (1 issue):
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340459
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1688/
>
> You
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
Carsten Ziegeler created SLING-6793:
---
Summary: Remove unused methods from XSSAPI
Key: SLING-6793
URL: https://issues.apache.org/jira/browse/SLING-6793
Project: Sling
Issue Type: Improvement
Carsten Ziegeler created SLING-6794:
---
Summary: Inconsistent handling of default configuration
Key: SLING-6794
URL: https://issues.apache.org/jira/browse/SLING-6794
Project: Sling
Issue Type
[
https://issues.apache.org/jira/browse/SLING-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984469#comment-15984469
]
Stefan Egli commented on SLING-5387:
Not sure if taking just the first two characters
On Wed, 2017-04-26 at 08:43 +, Stefan Seifert wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
On Tuesday 25 April 2017 14:09:51 Carsten Ziegeler wrote:
> I'm moving this into a separate thread to make the discussion easier.
>
> With the current state of the xss module, we would break every consumer
> and require her to upgrade code (release their own modules depending on
> XSS etc). As xss
[
https://issues.apache.org/jira/browse/SLING-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6787.
-
Resolution: Fixed
Assignee: Carsten Ziegeler
Applied the patch in rev 1792724.
For t
[
https://issues.apache.org/jira/browse/SLING-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6794.
-
Resolution: Fixed
Assignee: Carsten Ziegeler
Fixed in rev 1792725
> Inconsistent ha
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983008#comment-15983008
]
Konrad Windszus edited comment on SLING-6791 at 4/26/17 11:26 AM:
--
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983008#comment-15983008
]
Konrad Windszus edited comment on SLING-6791 at 4/26/17 11:27 AM:
--
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984629#comment-15984629
]
Carsten Ziegeler commented on SLING-6791:
-
I think servlets resolver should use tw
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-6791:
Fix Version/s: Servlets Resolver 2.4.12
> Servlet Resolver Test does no longer find scripts
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6791.
-
Resolution: Fixed
Assignee: Carsten Ziegeler
Fixed in rev 1792737 and rev 1792738
>
Carsten Ziegeler created SLING-6795:
---
Summary: Use DS to track scheduled services
Key: SLING-6795
URL: https://issues.apache.org/jira/browse/SLING-6795
Project: Sling
Issue Type: Improvemen
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984676#comment-15984676
]
Konrad Windszus commented on SLING-6791:
Thanks [~cziegeler]. I would prefer thoug
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984676#comment-15984676
]
Konrad Windszus edited comment on SLING-6791 at 4/26/17 12:09 PM:
--
Konrad Windszus created SLING-6796:
--
Summary: Servlet Resolver Test: Warn about non-existing resources
Key: SLING-6796
URL: https://issues.apache.org/jira/browse/SLING-6796
Project: Sling
Is
[
https://issues.apache.org/jira/browse/SLING-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6796.
Resolution: Fixed
Fix Version/s: Servlets Resolver 2.4.12
Fixed in [r1792739|https://
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984692#comment-15984692
]
Carsten Ziegeler commented on SLING-6791:
-
[~kwin] Feel free to improve it
> Serv
[
https://issues.apache.org/jira/browse/SLING-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6795.
-
Resolution: Fixed
Changed in rev 1792740
> Use DS to track scheduled services
> -
Oliver Lietz wrote
> On Tuesday 25 April 2017 14:09:51 Carsten Ziegeler wrote:
>> I'm moving this into a separate thread to make the discussion easier.
>>
>> With the current state of the xss module, we would break every consumer
>> and require her to upgrade code (release their own modules dependi
I guess Oliver Lietz meant, changing the symbolic name for the old version and
keep the symbolic name for the new version, but having both bundles as
full-fledged independent bundles. That way the dependencies are easier to
upgrade in the pom.xml.
> On 26. Apr 2017, at 14:47, Carsten Ziegeler
[
https://issues.apache.org/jira/browse/SLING-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984747#comment-15984747
]
Carsten Ziegeler commented on SLING-6621:
-
It seems only some components have been
Konrad Windszus wrote
> I guess Oliver Lietz meant, changing the symbolic name for the old version
> and keep the symbolic name for the new version, but having both bundles as
> full-fledged independent bundles. That way the dependencies are easier to
> upgrade in the pom.xml.
Dependencies are
Github user JEBailey closed the pull request at:
https://github.com/apache/sling/pull/218
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Carsten Ziegeler created SLING-6797:
---
Summary: Deprecate scheduling a job on a specific Sling instance
Key: SLING-6797
URL: https://issues.apache.org/jira/browse/SLING-6797
Project: Sling
I
[
https://issues.apache.org/jira/browse/SLING-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6797.
-
Resolution: Fixed
Deprecated in rev 1792743
> Deprecate scheduling a job on a specific Sl
On Wednesday 26 April 2017 14:57:26 Konrad Windszus wrote:
> I guess Oliver Lietz meant, changing the symbolic name for the old version
> and keep the symbolic name for the new version, but having both bundles as
> full-fledged independent bundles. That way the dependencies are easier to
> upgrade
[
https://issues.apache.org/jira/browse/SLING-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6798:
---
Component/s: Servlets
> Only start the SlingServletResolver once all service user mappings are
Konrad Windszus created SLING-6798:
--
Summary: Only start the SlingServletResolver once all service user
mappings are there
Key: SLING-6798
URL: https://issues.apache.org/jira/browse/SLING-6798
Projec
Hi,
based on the discussions in the "move o.a.s.xss.JsonUtil into a
separate package" and the "Versioning of o.a.s.xss" threads I would
like to get consensus on the following way forward:
- create a new bundle xss.compat based on the last release of the xss bundle,
- deprecate all classes in its
[
https://issues.apache.org/jira/browse/SLING-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6798.
Resolution: Fixed
Fix Version/s: Servlets Resolver 2.4.12
Fixed in [r1792750|https://
[
https://issues.apache.org/jira/browse/SLING-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984909#comment-15984909
]
Konrad Windszus commented on SLING-6791:
Moved the service user mapping configurat
+1
regards,
Karl
On Wed, Apr 26, 2017 at 4:36 PM, Karl Pauls wrote:
> Hi,
>
> based on the discussions in the "move o.a.s.xss.JsonUtil into a
> separate package" and the "Versioning of o.a.s.xss" threads I would
> like to get consensus on the following way forward:
>
> - create a new bundle xss
Sounds good to me, +1
Carsten
Karl Pauls wrote
> Hi,
>
> based on the discussions in the "move o.a.s.xss.JsonUtil into a
> separate package" and the "Versioning of o.a.s.xss" threads I would
> like to get consensus on the following way forward:
>
> - create a new bundle xss.compat based on the
+1
>-Original Message-
>From: Karl Pauls [mailto:karlpa...@gmail.com]
>Sent: Wednesday, April 26, 2017 4:36 PM
>To: dev@sling.apache.org
>Subject: [VOTE] XSSAPI
>
>Hi,
>
>based on the discussions in the "move o.a.s.xss.JsonUtil into a
>separate package" and the "Versioning of o.a.s.xss" th
51 matches
Mail list logo
