[
https://issues.apache.org/jira/browse/SLING-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171175#comment-16171175
]
Radu Cotescu commented on SLING-7134:
-
I have the impression that on Java 9 the Nashor
[
https://issues.apache.org/jira/browse/SLING-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171170#comment-16171170
]
Radu Cotescu commented on SLING-7133:
-
[~rombert], could you please tell me what's the
[
https://issues.apache.org/jira/browse/SLING-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171084#comment-16171084
]
Carsten Ziegeler commented on SLING-7134:
-
Not sure, isn't Nashorn already part of
Hi,
Apparently I was a bit ambitious with the plan to get Sling 10 "done"
in time for the release.
Many issues were fixed, however, we still have some blockers that we
can't get around quickly:
- Tika issue preventing full text search from working [1]
- Sling Models not working [2]
- JAXB not wo
Robert Munteanu created SLING-7135:
--
Summary: Sling Model object can't be instantiated on Java 9
Key: SLING-7135
URL: https://issues.apache.org/jira/browse/SLING-7135
Project: Sling
Issue T
[
https://issues.apache.org/jira/browse/SLING-7134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170698#comment-16170698
]
Robert Munteanu commented on SLING-7134:
[~cziegeler], [~radu.cotescu] - before se
Robert Munteanu created SLING-7134:
--
Summary: Composum does not work with Java 9
Key: SLING-7134
URL: https://issues.apache.org/jira/browse/SLING-7134
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-7133.
Resolution: Fixed
- [r1808775|https://svn.apache.org/r1808775] - added HTL tests with JS and
Robert Munteanu created SLING-7133:
--
Summary: Add minimal HTL tests to launchpad/testing
Key: SLING-7133
URL: https://issues.apache.org/jira/browse/SLING-7133
Project: Sling
Issue Type: Impr
Hi,
On 18 September 2017 at 14:49, Julian Sedding wrote:
> On Mon, Sep 18, 2017 at 2:58 PM, Ian Boston wrote:
> > Hi,
> >
> > On 18 September 2017 at 13:51, Carsten Ziegeler
> > wrote:
> >>
> >> Julian Sedding wrote
> >> > Hi Ian
> >> >
> >> > Would it make sense to remove the AdapterFactory i
[
https://issues.apache.org/jira/browse/SLING-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170075#comment-16170075
]
Justin Edelson commented on SLING-5739:
---
[~kwin] docs have been updated.
> [Sling M
On Mon, Sep 18, 2017 at 2:58 PM, Ian Boston wrote:
> Hi,
>
> On 18 September 2017 at 13:51, Carsten Ziegeler
> wrote:
>>
>> Julian Sedding wrote
>> > Hi Ian
>> >
>> > Would it make sense to remove the AdapterFactory implementation and
>> > instead pass along the URIProvider service(s) using the
>
[
https://issues.apache.org/jira/browse/SLING-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson closed SLING-5739.
-
> [Sling Models] Allow for extensible @Via providers
> ---
[
https://issues.apache.org/jira/browse/SLING-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-5739:
--
Fix Version/s: Sling Models API 1.3.4
Sling Models Impl 1.4.0
> [Sling Models
Hi,
On 18 September 2017 at 14:17, Carsten Ziegeler
wrote:
> Ian Boston wrote
> > Hi,
> >
> > On 18 September 2017 at 13:51, Carsten Ziegeler
> > wrote:
> >
> >> Julian Sedding wrote
> >>> Hi Ian
> >>>
> >>> Would it make sense to remove the AdapterFactory implementation and
> >>> instead pass
[
https://issues.apache.org/jira/browse/SLING-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson reassigned SLING-7124:
-
Assignee: Justin Edelson
> Allow PostConstruct method to return false to indicate that a
[
https://issues.apache.org/jira/browse/SLING-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson resolved SLING-7124.
---
Resolution: Fixed
committed in r1808699
> Allow PostConstruct method to return false to indic
Ian Boston wrote
> Hi,
>
> On 18 September 2017 at 13:51, Carsten Ziegeler
> wrote:
>
>> Julian Sedding wrote
>>> Hi Ian
>>>
>>> Would it make sense to remove the AdapterFactory implementation and
>>> instead pass along the URIProvider service(s) using the
>>> o.a.s.jcr.resource.internal.HelperD
[
https://issues.apache.org/jira/browse/SLING-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-7124:
--
Fix Version/s: Sling Models Impl 1.4.6
> Allow PostConstruct method to return false to indicate
Hi,
On 18 September 2017 at 13:51, Carsten Ziegeler
wrote:
> Julian Sedding wrote
> > Hi Ian
> >
> > Would it make sense to remove the AdapterFactory implementation and
> > instead pass along the URIProvider service(s) using the
> > o.a.s.jcr.resource.internal.HelperData object instead? Accordin
Hi,
I have just updated the patch as the AdapterFactory javadoc was wrong.
It adapts from ResourceResolver -> URIConverter which is an internal
class, so is only active inside the bundle.
The doc said it adapted from Value or Resource -> URI which is wrong.
The HelperData class could be used but
Julian Sedding wrote
> Hi Ian
>
> Would it make sense to remove the AdapterFactory implementation and
> instead pass along the URIProvider service(s) using the
> o.a.s.jcr.resource.internal.HelperData object instead? According to
> its javadoc, it is "used to pass several services/data to the
> re
Hi Ian
Would it make sense to remove the AdapterFactory implementation and
instead pass along the URIProvider service(s) using the
o.a.s.jcr.resource.internal.HelperData object instead? According to
its javadoc, it is "used to pass several services/data to the
resource".
I assume the AdapterFacto
On Thu, 2017-09-14 at 17:58 +0200, Konrad Windszus wrote:
> Some more investigations on that:
>
> The BREE header is deprecated since OSGi 4.3 (https://www.infoq.com/n
> ews/2011/03/osgi-43). I don't think we should generate it any longer.
> Instead we should only rely on the Require-Capability wh
Hi,
Good catch, didn't implement the vital interface.
Put the API into o.a.s.api.resource (o.a.s.resource.api doesn't exist), and
added some doc. While writing that doc realised there was no way of getting
a URI for a private network context (if available) so added a method and
documented.
The comp
Konrad Windszus created SLING-7132:
--
Summary: No longer use the animal-sniffer-plugin with JDK >= 9
Key: SLING-7132
URL: https://issues.apache.org/jira/browse/SLING-7132
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-7129.
Resolution: Fixed
Fix Version/s: Parent 33
Fixed with [r1808677|https://svn.apache.or
Konrad Windszus created SLING-7131:
--
Summary: Move javaversion-maven-plugin to attic
Key: SLING-7131
URL: https://issues.apache.org/jira/browse/SLING-7131
Project: Sling
Issue Type: Task
[
https://issues.apache.org/jira/browse/SLING-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169841#comment-16169841
]
Konrad Windszus commented on SLING-7129:
With this change the newly introduced jav
>-Original Message-
>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Tuesday, September 12, 2017 8:31 PM
>To: dev
>Subject: Re: [RT] Context-Aware Services - Multitenancy for SPI
>implementations
>In my upcoming adaptTo talk I'll mention making resource types
>multi-tena
>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Tuesday, September 12, 2017 7:41 PM
>To: dev@sling.apache.org; Stefan Seifert
>Subject: Re: [RT] Context-Aware Services - Multitenancy for SPI
>implementations
>If I understand correctly, you do the matching
+1
Tommaso
Il giorno ven 15 set 2017 alle ore 12:58 Robert Munteanu
ha scritto:
> On Fri, 2017-09-08 at 22:40 +0200, Oliver Lietz wrote:
> > On Friday 08 September 2017 16:48:24 Stefan Seifert wrote:
> > > in our last discussion [1] our plan was this:
> > >
> > >
> > > > - name pattern for the
32 matches
Mail list logo
