[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ramboz updated SLING-6986:
-
Comment: was deleted
(was: PR: https://github.com/apache/sling/pull/245)
> The ResourceResolver
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065728#comment-16065728
]
Julien Ramboz commented on SLING-6986:
--
PR: https://github.com/apache/sling/pull/245
> The
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065724#comment-16065724
]
ASF GitHub Bot commented on SLING-6986:
---
GitHub user ramboz opened a pull request:
GitHub user ramboz opened a pull request:
https://github.com/apache/sling/pull/245
SLING-6986 - The ResourceResolver mock does not test the resource type
hierarchy in isResourceType
Create a simple improvement, where we check:
- the `sling:resourceType` property on the resource
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ramboz updated SLING-6986:
-
Summary: The ResourceResolver mock does not test the resource type
hierarchy in isResourceType
Julien Ramboz created SLING-6986:
Summary: MockResourceResolver does not test the resource type
hierarchy in isResourceType
Key: SLING-6986
URL: https://issues.apache.org/jira/browse/SLING-6986
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ramboz updated SLING-6986:
-
Affects Version/s: Testing ResourceResolver Mock 1.1.18
> MockResourceResolver does not test the
[
https://issues.apache.org/jira/browse/SLING-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Ramboz updated SLING-6986:
-
Component/s: Testing
> MockResourceResolver does not test the resource type hierarchy in
>
Hi,
Yes, this is possible via the SlingRequestProcessor service[1]. You need to
construct "fake" request and response objects which provide the information
needed to execute the script/servlet. You can use [2] for these
request/response objects or roll your own.
Regards,
Justin
[1]
Hi,
Is it possible to dispatch/include a templating file (HTL/JSP) from within
an OSGi service?
Here is the use-case:
1. Nightly schedule job that finds all resources that have expired
2. Create an email with the content of the resources (title/path/links etc)
3. Send the email to a user for
my own +1
On Jun 26, 2017, at 1:55 PM, Antonio Sanso wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/browse/SLING-6972
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1748
>
> You can
Hi,
I have now "finished" the conversion (SLING-6955) with a few TODOs
mentioned at https://github.com/apache/sling-site - mostly the [TOC]
table of contents generation which should be fixed in the next version
of JBake.
The converted website is ready for review at https://sling.apache.org/ng/
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065192#comment-16065192
]
Bertrand Delacretaz commented on SLING-6955:
Thanks for the feedback, I have fixed all the
[
https://issues.apache.org/jira/browse/SLING-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065044#comment-16065044
]
Feike Visser commented on SLING-6504:
-
thanks [~radu.cotescu], let me do that
> Use-api to support
[
https://issues.apache.org/jira/browse/SLING-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-6504:
Fix Version/s: Scripting HTL Engine 1.0.36
> Use-api to support more flexible way to adapt from
[
https://issues.apache.org/jira/browse/SLING-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu reassigned SLING-6504:
---
Assignee: Radu Cotescu
> Use-api to support more flexible way to adapt from different
[
https://issues.apache.org/jira/browse/SLING-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16065034#comment-16065034
]
Radu Cotescu commented on SLING-6504:
-
[~fvisser], the patch looks relatively clean to me. Could you
i'm ok with 1)
we still have the compile and signature check in the poms.
i cannot remember any problems in in the last 1-2 years that where related to
differences between the JDK versions.
stefan
>-Original Message-
>From: Robert Munteanu [mailto:romb...@apache.org]
>Sent: Tuesday,
+1
Andrei Dulvac created SLING-6985:
Summary: [HApi] Migrate to R6 annotations
Key: SLING-6985
URL: https://issues.apache.org/jira/browse/SLING-6985
Project: Sling
Issue Type: Improvement
Hi,
I remain concerned that we are now essentially making "adaptable" as a
reserved attribute. If I'm the only one with this concern, then I'm not
going to stand in the way of this change, but I'd love to see some
affirmative statement from someone else saying "yeah, that's not a big
deal." :)
hi team,
I have made an extension of the data-sly-use api to also adapt from other
objects than Request/Resource.
Example:
As you can see the change has no impact on the syntax or language.
Would be great to receive feedback or to hear how to proceed.
[
https://issues.apache.org/jira/browse/SLING-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064703#comment-16064703
]
Ian Boston edited comment on SLING-6979 at 6/27/17 11:55 AM:
-
Branch underway
[
https://issues.apache.org/jira/browse/SLING-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064703#comment-16064703
]
Ian Boston commented on SLING-6979:
---
Branch underway at https://github.com/ieb/sling/tree/SLING-6979
>
On Tue, 2017-06-20 at 19:09 +0200, Carsten Ziegeler wrote:
> I think that's not possible as includes are handled before removals.
> So
> while you could remove each artifact from that feature separately,
> you
> can't remove the feature completely
> The include handling is a hack (tbh) and we
On Tue, 2017-06-20 at 12:17 +0200, Bertrand Delacretaz wrote:
> Hi Robert,
>
> On Tue, Jun 20, 2017 at 8:43 AM, Robert Munteanu
> wrote:
>
> > ...[feature name=sling]
> > [artifacts runModes=:remove]...
>
> Maybe try with a different feature name? I have a vague memory of
>
On Mon, 2017-06-26 at 11:55 +, Antonio Sanso wrote:
> Please vote to approve this release:
+1
For the record, this is towards version 1.4.0, the subject misses that.
Robert
signature.asc
Description: This is a digitally signed message part
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064570#comment-16064570
]
Robert Munteanu commented on SLING-6955:
Forgot - is there an easy way to keep the JBake binaries
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064562#comment-16064562
]
Robert Munteanu edited comment on SLING-6955 at 6/27/17 9:48 AM:
-
The
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064562#comment-16064562
]
Robert Munteanu commented on SLING-6955:
The conversion looks good overall to me, no major issues
Hi,
In two weeks the ASF Jenkins instance will stop supporting JDK 7 for
Maven jobs (details attached).
There will be an impact for us as we have a large number of jobs
fitting this description.
There are two ways out:
1) Remove the Java 7 jobs, as we're moving towards Java 8 anyway
2) Switch
31 matches
Mail list logo