[
https://issues.apache.org/jira/browse/SLING-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5518.
---
> Get resource resolver from bindings by using SlingBindings.RESOLVER
> --
[
https://issues.apache.org/jira/browse/SLING-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5663.
---
> Make Thymeleaf TemplateEngine available as service
> --
[
https://issues.apache.org/jira/browse/SLING-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5351.
---
> Thymeleaf fails loading version from properties
> ---
>
>
[
https://issues.apache.org/jira/browse/SLING-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-4884.
---
> remove embedded CaptureResponseWrapper
> --
>
> Key:
[
https://issues.apache.org/jira/browse/SLING-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-5075.
---
> Upgrade Thymeleaf to 3.0
>
>
> Key: SLING-5075
>
Hi,
the vote has passed with the following result:
+1 (binding): Carsten Ziegeler, Stefan Egli, Oliver Lietz
I will copy this release to the Sling dist directory and promote the artifacts
to the central Maven repository.
Thanks for voting!
O.
[
https://issues.apache.org/jira/browse/SLING-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-5820.
Resolution: Fixed
fixed in r1751343
> AvroContentSerializer's DataFileWriter should not be
Tommaso Teofili created SLING-5820:
--
Summary: AvroContentSerializer's DataFileWriter should not be
cached
Key: SLING-5820
URL: https://issues.apache.org/jira/browse/SLING-5820
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-4752:
Fix Version/s: (was: API 2.12.0)
API 2.13.0
> New resource query API
> --
Hi,
I am reactivating the thread as we really would like to successfully
mutualize the merging of resources [1] in some particular cases as well.
The following use case [0] implies:
- Merging of two semantically related resources that do not share a
relative path
- The location of the two reso
> On 04 Jul 2016, at 14:34, Oliver Lietz wrote:
>
> On Monday 04 July 2016 14:17:13 Konrad Windszus wrote:
>> On 04 Jul 2016, at 14:03, Oliver Lietz wrote:
>>> On Monday 04 July 2016 10:04:10 Carsten Ziegeler wrote:
Konrad Windszus wrote
> It was changed from 2.1.1 to 2.2.0 in r1
On Monday 04 July 2016 14:17:13 Konrad Windszus wrote:
> On 04 Jul 2016, at 14:03, Oliver Lietz wrote:
> > On Monday 04 July 2016 10:04:10 Carsten Ziegeler wrote:
> >> Konrad Windszus wrote
> >>
> >>> It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but
> >>> there
> >>> was a rel
[
https://issues.apache.org/jira/browse/SLING-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361234#comment-15361234
]
Bertrand Delacretaz commented on SLING-5819:
Good point - I have renamed that
On 04 Jul 2016, at 14:03, Oliver Lietz wrote:
>
> On Monday 04 July 2016 10:04:10 Carsten Ziegeler wrote:
>> Konrad Windszus wrote
>>
>>> It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but there
>>> was a release in between. Therefore the change from 2.2.0 to 2.3.0 for
>>> SLIN
[
https://issues.apache.org/jira/browse/SLING-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu reassigned SLING-5314:
---
Assignee: Radu Cotescu
> Support setting the basename for the resource bundle backing the Sig
[
https://issues.apache.org/jira/browse/SLING-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-5314:
Fix Version/s: Scripting Sightly Engine 1.0.20
> Support setting the basename for the resource bundl
On Monday 04 July 2016 10:04:10 Carsten Ziegeler wrote:
> Konrad Windszus wrote
>
> > It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but there
> > was a release in between. Therefore the change from 2.2.0 to 2.3.0 for
> > SLING-5665 seems right to me.
> Yes, sorry for the noise -
[
https://issues.apache.org/jira/browse/SLING-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361216#comment-15361216
]
Oliver Lietz commented on SLING-5819:
-
[~bdelacretaz], module is now named {{org.apach
[
https://issues.apache.org/jira/browse/SLING-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361209#comment-15361209
]
Bertrand Delacretaz commented on SLING-5800:
The vote for the org.apache.sling
[
https://issues.apache.org/jira/browse/SLING-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-5819.
Resolution: Fixed
Fixed in revision 1751251
> repoinit JCR module should not export
Bertrand Delacretaz created SLING-5819:
--
Summary: repoinit JCR module should not export visitor +
initializer classes
Key: SLING-5819
URL: https://issues.apache.org/jira/browse/SLING-5819
Project
Nicolas Peltier created SLING-5818:
--
Summary: make sling pipe writer a persistent configuration
Key: SLING-5818
URL: https://issues.apache.org/jira/browse/SLING-5818
Project: Sling
Issue Typ
[
https://issues.apache.org/jira/browse/SLING-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-5554:
Fix Version/s: Scripting Sightly Engine 1.0.20
> Sightly: allow calling data-sly-use with a resource
[
https://issues.apache.org/jira/browse/SLING-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-5554.
-
Resolution: Duplicate
Assignee: Radu Cotescu
> Sightly: allow calling data-sly-use with a re
Konrad Windszus wrote
> It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but there
> was a release in between.
> Therefore the change from 2.2.0 to 2.3.0 for SLING-5665 seems right to me.
Yes, sorry for the noise - somehow FishEye displayed the change as
directly from 2.1.1 to 2.3
On 02/07/16 14:19, "Oliver Lietz" wrote:
>I would like to have new releases of base, impl and oak. Are they on
>anyones
>TODO list or should I go ahead? They have some unresolved issues which I
>would
>"unschedule".
+1
(I've added next versions and moved the open tickets there)
Cheers,
Stefan
[
https://issues.apache.org/jira/browse/SLING-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-4135:
---
Fix Version/s: (was: Discovery Impl 1.2.8)
Discovery Impl 1.2.10
> Make discove
[
https://issues.apache.org/jira/browse/SLING-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-5060:
---
Fix Version/s: (was: Discovery Impl 1.2.8)
Discovery Impl 1.2.10
> use virtual
[
https://issues.apache.org/jira/browse/SLING-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-4380:
---
Fix Version/s: (was: Discovery Impl 1.2.8)
Discovery Impl 1.2.10
> Use sling mo
[
https://issues.apache.org/jira/browse/SLING-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-5732:
---
Fix Version/s: (was: Discovery Base 1.1.4)
Discovery Base 1.1.6
> [discovery] A
[
https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-5231:
---
Fix Version/s: (was: Discovery Oak 1.2.8)
(was: Discovery Base 1.1.4)
[
https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-5231:
--
Assignee: Stefan Egli
> Remove getAdministrativeResourceResolver() usage from Discovery compone
[
https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated SLING-5231:
---
Fix Version/s: Discovery Impl 1.2.10
> Remove getAdministrativeResourceResolver() usage from Discovery
It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but there was
a release in between.
Therefore the change from 2.2.0 to 2.3.0 for SLING-5665 seems right to me.
Konrad
> On 04 Jul 2016, at 09:13, Konrad Windszus wrote:
>
> I changed the package version of org.apache.sling.api.sc
On 02/07/16 13:37, "Oliver Lietz" wrote:
>On Friday 01 July 2016 21:56:32 Oliver Lietz wrote:
>> Hi,
>>
>> we solved 2 issues in this release:
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12333672
>
>Well, 6 issues.
...and SLING-5685 is still open but presumably that's ok as its
I changed the package version of org.apache.sling.api.scripting from 2.2.0 to
2.3.0 in r1739719 for the semantic change in SLING-5665.
Which package was previously at 2.1.1?
Konrad
> On 04 Jul 2016, at 08:21, Carsten Ziegeler wrote:
>
> I think SLING-5665 is a clarification of the javadocs in t
36 matches
Mail list logo