On Wed, 2017-05-10 at 14:22 +, Stefan Seifert wrote:
> Please vote to approve this new logo:
+1
(And yay for consensus on something UI-related :-) )
Robert
signature.asc
Description: This is a digitally signed message part
Hi Andy,
On Wed, 2017-05-10 at 15:58 -0700, Andreas Schaefer Sr. wrote:
> Hi Robert
>
> A client for the IntelliJ plugin asked why he cannot edit a
> _rep_policy.xml file and deploy it. Debugging the issue
> I see a Constraint Violation because rep:policy is protected. I
> tested this will Eclips
my own +1
On May 10, 2017, at 11:04 AM, Antonio Sanso wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING-6053
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1716/
>
> You can use this UNIX script to dow
Hi Robert
A client for the IntelliJ plugin asked why he cannot edit a _rep_policy.xml
file and deploy it. Debugging the issue
I see a Constraint Violation because rep:policy is protected. I tested this
will Eclipse and it does work their
either.
I assume that for rep:policy changes the user nee
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
+1
Thanks Chris!!!
On Wed, May 10, 2017 at 11:08 AM Stefan Seifert
wrote:
> +1
>
>
>
+1
+1
On Wed, 10 May 2017 at 16:23 Stefan Seifert wrote:
>
> Please vote to approve this new logo:
>
> [ ] +1 Approve the new logo
> [ ] 0 Don't care
> [ ] -1 Don't approve, because ...
>
> This majority vote is open for at least 72 hours.
>
+1
On May 10, 2017, at 4:22 PM, Stefan Seifert wrote:
> since 2012 we try to update our sling logo because we are required to include
> a "TM" in it (see [1]).
>
> a few weeks ago chris millar contributed a new sling logo with these changes:
> 1. It uses the new Apache feather
> 2. The shoulder
+1
On Wed, May 10, 2017 at 10:25 AM, Konrad Windszus wrote:
> +1
> > On 10. May 2017, at 16:22, Stefan Seifert
> wrote:
> >
> > since 2012 we try to update our sling logo because we are required to
> include a "TM" in it (see [1]).
> >
> > a few weeks ago chris millar contributed a new sling lo
+1
> On 10. May 2017, at 16:22, Stefan Seifert wrote:
>
> since 2012 we try to update our sling logo because we are required to include
> a "TM" in it (see [1]).
>
> a few weeks ago chris millar contributed a new sling logo with these changes:
> 1. It uses the new Apache feather
> 2. The should
[
https://issues.apache.org/jira/browse/SLING-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-6848:
---
Attachment: SLING-6848.0.patch
attaching draft patch.
> Package level monitoring should be on
[
https://issues.apache.org/jira/browse/SLING-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert reassigned SLING-2696:
-
Assignee: Stefan Seifert (was: Oliver Lietz)
> Comply with project branding guidelines
>
Tommaso Teofili created SLING-6848:
--
Summary: Package level monitoring should be only enabled
consciously
Key: SLING-6848
URL: https://issues.apache.org/jira/browse/SLING-6848
Project: Sling
since 2012 we try to update our sling logo because we are required to include a
"TM" in it (see [1]).
a few weeks ago chris millar contributed a new sling logo with these changes:
1. It uses the new Apache feather
2. The shoulder of the G matches the width of the upper horizontal rule
3. The curv
Konrad Windszus wrote
> I am not sure either, I would like to hear the opinions of some other Sling
> committers on this.
I think we're talking about edge cases here and the cost of doing the
resolution / mapping is too high - and it would punish all requests.
In addition, the only way to make th
I am not sure either, I would like to hear the opinions of some other Sling
committers on this.
Konrad
> On 10. May 2017, at 14:25, Antonio Sanso wrote:
>
> hi Konrad
>
> On May 10, 2017, at 2:16 PM, Konrad Windszus wrote:
>
>> Hi Antonio,
>> Sorry for the confusion, I was wrongly assuming t
hi Konrad
On May 10, 2017, at 2:16 PM, Konrad Windszus wrote:
> Hi Antonio,
> Sorry for the confusion, I was wrongly assuming that you fixed my original
> concern without checking further in the code.
> But in fact there are still unexpected corner cases which cover the wrong
> nodes (see my l
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004589#comment-16004589
]
Konrad Windszus commented on SLING-6053:
Yes right, but the current behaviour is m
Hi Antonio,
Sorry for the confusion, I was wrongly assuming that you fixed my original
concern without checking further in the code.
But in fact there are still unexpected corner cases which cover the wrong nodes
(see my last comments in SLING-6053).
Not sure how to proceed here, but the previou
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004565#comment-16004565
]
Antonio Sanso commented on SLING-6053:
--
[~kwin]
on top
bq. Therefore the longest m
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004561#comment-16004561
]
Antonio Sanso commented on SLING-6053:
--
[~kwin] said that the committed patch and the
hi Konrad,
I am confused now since you were in favor for it in the first place …
https://issues.apache.org/jira/browse/SLING-6053?focusedCommentId=16000473&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16000473
regards
antonio
On May 10, 2017, at 11:21 AM, Konra
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004543#comment-16004543
]
Antonio Sanso commented on SLING-6053:
--
[~kwin] gotcha now. Sorry if it took so long.
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004535#comment-16004535
]
Konrad Windszus commented on SLING-6053:
But in my example there are only two appl
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004521#comment-16004521
]
Antonio Sanso commented on SLING-6053:
--
[~kwin] you probably you might want to give a
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004498#comment-16004498
]
Konrad Windszus commented on SLING-6053:
But {{isNodeRequiresAuthHandler("/resourc
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004498#comment-16004498
]
Konrad Windszus edited comment on SLING-6053 at 5/10/17 11:22 AM:
--
[
https://issues.apache.org/jira/browse/SLING-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6847.
-
Resolution: Fixed
Removed in rev 1794698
> JcrResource is not adaptable to PersistableVal
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004423#comment-16004423
]
Antonio Sanso commented on SLING-6053:
--
[~kwin]
bq. . Then the AuthenticationHolder
Carsten Ziegeler created SLING-6847:
---
Summary: JcrResource is not adaptable to PersistableValueMap
Key: SLING-6847
URL: https://issues.apache.org/jira/browse/SLING-6847
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004383#comment-16004383
]
Konrad Windszus commented on SLING-6053:
Then the other way round, lets say {{/}}
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004373#comment-16004373
]
Antonio Sanso commented on SLING-6053:
--
[~kwin] well I wonder how would be the settin
Sorry for insisting on it, but I am still not 100% convinced the patch for
SLING-6053 works correctly.
See my comment in
https://issues.apache.org/jira/browse/SLING-6053?focusedCommentId=16004357&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16004357.
The general
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004357#comment-16004357
]
Konrad Windszus commented on SLING-6053:
[~asanso] IIUC then
https://github.com/a
+1
On May 9, 2017, at 5:59 PM, Karl Pauls wrote:
> I would like to call a vote on the following release,
>
> JUnit Scriptable Tests Provider 1.0.12
> We solved 1 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12329147/
>
> Staging repository:
> https://repos
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING-6053
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1716/
You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/slin
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-6053.
--
Resolution: Fixed
Fix Version/s: Auth Core 1.3.26
> SlingAuthenticator identifies wrong s
+1
[
https://issues.apache.org/jira/browse/SLING-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004335#comment-16004335
]
Antonio Sanso commented on SLING-6053:
--
[~kwindszus] I added a test that covers your
41 matches
Mail list logo
