[
https://issues.apache.org/jira/browse/SLING-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958395#comment-15958395
]
Konrad Windszus commented on SLING-6772:
[~cziegeler] Would you mind extending
ht
> On 5 Apr 2017, at 18:45, Stefan Seifert wrote:
>
> +1
>
> one finding: org.apache.sling.validation.test-services has a dependency to
> org.apache.sling.commons.json (because the last released
> org.apache.sling.servlets.post still requires it). not sure if this is a
> blocker - it's only a
[
https://issues.apache.org/jira/browse/SLING-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-6772.
-
Resolution: Fixed
Implemented in rev 1790344 with test cases.
The ordering is now:
1. mapp
[
https://issues.apache.org/jira/browse/SLING-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-6772:
Description:
As discussed in [1] we should aim at making Sling configurationless again. One
Stefan Seifert wrote
> +1
>
> one finding: org.apache.sling.validation.test-services has a dependency to
> org.apache.sling.commons.json (because the last released
> org.apache.sling.servlets.post still requires it). not sure if this is a
> blocker - it's only a test service not to be indented
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957514#comment-15957514
]
Chris Millar commented on SLING-6740:
-
[~radu.cotescu]
I've updated my pull request to
+1
one finding: org.apache.sling.validation.test-services has a dependency to
org.apache.sling.commons.json (because the last released
org.apache.sling.servlets.post still requires it). not sure if this is a
blocker - it's only a test service not to be indented to be used outside sling.
stefan
[
https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957039#comment-15957039
]
Julian Sedding commented on SLING-6273:
---
Great! Thanks for your changes, they look g
[
https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956988#comment-15956988
]
Konrad Windszus edited comment on SLING-6273 at 4/5/17 3:04 PM:
[
https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956988#comment-15956988
]
Konrad Windszus commented on SLING-6273:
Thanks, did some more polishing in [r1790
[
https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding resolved SLING-6273.
---
Resolution: Fixed
Documentation committed in [r1790285|https://svn.apache.org/r1790285].
[~kw
[
https://issues.apache.org/jira/browse/SLING-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senol Tas updated SLING-6763:
-
Description:
remove org.apache.sling.commons.json dependency from esx engine and replace
with native buil
Hi,
This is first release of Apache Sling Validation, namely of the modules
validation.api, validation.core and validation.test-services.
We solved quite some issues in this first release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12328980
There are two outstanding issues:
http
[
https://issues.apache.org/jira/browse/SLING-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956844#comment-15956844
]
Konrad Windszus commented on SLING-6662:
bq. We don't have a strict naming pattern
On Wed, 2017-04-05 at 13:12 +0200, Oliver Lietz wrote:
> On Wednesday 05 April 2017 11:56:56 Konrad Windszus wrote:
> > For ITs we sometimes leverage dedicated test bundles (which should
> > only be
> > deployed for the purpose of running the IT). Those test bundles are
> > usually
> > not released
[
https://issues.apache.org/jira/browse/SLING-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956702#comment-15956702
]
Oliver Lietz commented on SLING-6662:
-
We don't have a strict naming pattern and I gue
On Wednesday 05 April 2017 11:56:56 Konrad Windszus wrote:
> For ITs we sometimes leverage dedicated test bundles (which should only be
> deployed for the purpose of running the IT). Those test bundles are usually
> not released (i.e. stay at 1.0.0-SNAPSHOT). But with PaxExam or even with
> the sli
On Wed, Apr 5, 2017 at 11:56 AM, Konrad Windszus wrote:
> ...2. Release the test-services as well?..
+1, I've been doing this for a few modules already and I agree to make
it a general rule.
-Bertrand
On Wed, 2017-04-05 at 11:56 +0200, Konrad Windszus wrote:
> For ITs we sometimes leverage dedicated test bundles (which should
> only be deployed for the purpose of running the IT). Those test
> bundles are usually not released (i.e. stay at 1.0.0-SNAPSHOT). But
> with PaxExam or even with the slin
For ITs we sometimes leverage dedicated test bundles (which should only be
deployed for the purpose of running the IT). Those test bundles are usually not
released (i.e. stay at 1.0.0-SNAPSHOT). But with PaxExam or even with the
slingstart-maven-plugin it is now easily possible to have ITs in th
Let me quickly list the advantages/disadvantages of having a bundle
documentation in the readme.md from my point of view:
Advantages:
- It allows a PR to contain documentation together with the actual script
changes
- The documentation could be versioned as well
- Easy to find
Disadvantages
- T
Hi,
I like the fact that we have a consistent documentation section in our
site. I also like the README.md, it's very much 'in-your-face' for
developers and also for users browsing via Github.
I was thinking for some time whether we can unify them by storing the
canonical information in Github as
[
https://issues.apache.org/jira/browse/SLING-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956445#comment-15956445
]
Konrad Windszus commented on SLING-6273:
[~jsedding] Would you be able to extend
Carsten Ziegeler created SLING-6772:
---
Summary: Provide default mapping for service users
Key: SLING-6772
URL: https://issues.apache.org/jira/browse/SLING-6772
Project: Sling
Issue Type: Imp
[
https://issues.apache.org/jira/browse/SLING-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-6769.
Resolution: Fixed
Assignee: Oliver Lietz
Great, thanks [~olli] . For the record, the S
26 matches
Mail list logo
