[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-6652:
--
Attachment: SLING-6652.diff
The only problem with this patch is that there is still a warning ou
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929253#comment-15929253
]
Justin Edelson commented on SLING-6652:
---
This appears to be an XY problem. The actua
Hi Dan,
I don't think I'm understanding how that API would work.
You have a single Resource there and a single Class (which I assume is
actually an interface for your use case). Are you saying that for one
Resource, there would be multiple Model classes implementing that same
interface mapped to t
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929029#comment-15929029
]
Justin Edelson commented on SLING-6655:
---
bq. The difference is that its not obvious
uh, my fault - should be fixed in rev. 1787254
stefan
>-Original Message-
>From: Andreas Schaefer [mailto:andreas.schae...@madplanet.com]
>Sent: Thursday, March 16, 2017 10:09 PM
>To: dev
>Cc: Andreas Schaefer
>Subject: Failing Build of current Trunk
>
>Hi
>
>I tried to make sure that m
Hi
I tried to make sure that my Git repo is clean but today I am not able to build
the current Git Repo.
The root pom has this line:
bundles/commons/fscontentparser
but that module was renamed to bundles/jcr/contentparser on commit 103d84f9
Cheers - Andy Schaefer
[
https://issues.apache.org/jira/browse/SLING-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco reassigned SLING-4524:
---
Assignee: Dan Klco
> Provide the properties of the current Resource as a ValueMap via the
> sling:de
[
https://issues.apache.org/jira/browse/SLING-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928903#comment-15928903
]
Dan Klco commented on SLING-4524:
-
I agree with [~radu.cotescu]'s comment, this should pro
I do think though that there's a ton of value in the concept of being able
to tie SlingModels to a resource type. I agree that this API is clunky, but
the idea of limiting based on resourceType in Sling Models was really
missing. I am using this concept for a library I have in progress right now
so
Hi
Shouldn’t the package ‘com.composum.core.pckgmgr’ being added to the Apache
Sling Login Admin Whitelist Configuration Fragment for ‘composum’?
As of now packages cannot be fully handled in composum without whitelisting it
manually.
Cheers - Andy Schaefer Sr.
[
https://issues.apache.org/jira/browse/SLING-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-6656.
-
Resolution: Fixed
[r1787233|https://svn.apache.org/r1787233]
> Wrong language name in GSPScriptEn
Oliver Lietz created SLING-6656:
---
Summary: Wrong language name in GSPScriptEngineFactory
Key: SLING-6656
URL: https://issues.apache.org/jira/browse/SLING-6656
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928701#comment-15928701
]
Dirk Rudolph commented on SLING-6655:
-
The difference is that its not obvious to under
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928680#comment-15928680
]
Dirk Rudolph edited comment on SLING-6652 at 3/16/17 7:21 PM:
--
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928680#comment-15928680
]
Dirk Rudolph commented on SLING-6652:
-
The API change was considered like that because
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928674#comment-15928674
]
Justin Edelson commented on SLING-6655:
---
bq. Ok I see but as far as I can see handle
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928670#comment-15928670
]
Justin Edelson commented on SLING-6652:
---
Looking at the Pull Request and reading the
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928664#comment-15928664
]
Dirk Rudolph commented on SLING-6655:
-
Ok I see but as far as I can see handlebars is
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928664#comment-15928664
]
Dirk Rudolph edited comment on SLING-6655 at 3/16/17 7:06 PM:
--
On Thursday 16 March 2017 15:21:32 Konrad Windszus wrote:
> Some javadocs in
> https://github.com/apache/sling/blob/trunk/testing/org.apache.sling.testing
> .paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L8
> 62 would be really helpful, which explain under which circumsta
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928654#comment-15928654
]
Justin Edelson commented on SLING-6655:
---
Handlebars is the most obvious case where t
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928645#comment-15928645
]
Dirk Rudolph edited comment on SLING-6655 at 3/16/17 6:58 PM:
--
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928646#comment-15928646
]
Justin Edelson commented on SLING-6655:
---
Also, I don't see where SLING-6652 talks ab
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928645#comment-15928645
]
Dirk Rudolph commented on SLING-6655:
-
By example? The only one that would come to my
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928634#comment-15928634
]
Justin Edelson commented on SLING-6655:
---
These methods exist for loosely typed scrip
[
https://issues.apache.org/jira/browse/SLING-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirk Rudolph updated SLING-6655:
Description:
As far as I understood the the whole story behind Sling Models API is/was that
it can
Dirk Rudolph created SLING-6655:
---
Summary: Remove untyped getModelFrom* methods from ModelFactory
Key: SLING-6655
URL: https://issues.apache.org/jira/browse/SLING-6655
Project: Sling
Issue Type
GitHub user Buuhuu opened a pull request:
https://github.com/apache/sling/pull/204
Feature/sling 6652
This pull requests enables 1 to many binding from resourceType to model.
IMHO the implementation is quite ugly because of the way resourceType
binding is defined. In the cu
Lgtm, thanks Stefan!
Carsten
Stefan Seifert wrote
> i've prepare a new PR with *only* a streaming API [1].
> please have a new review on the API part.
>
> it has a very simple ContentHandler interface which reports every resource
> found with its map of properties - ordered as found in the sour
Tommaso Teofili created SLING-6654:
--
Summary: Test distribution has a wrong header
Key: SLING-6654
URL: https://issues.apache.org/jira/browse/SLING-6654
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928410#comment-15928410
]
Justin Edelson commented on SLING-6652:
---
Understood. I was just expressing how this
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928392#comment-15928392
]
Dirk Rudolph commented on SLING-6652:
-
This is not what this is about. See I have a re
[
https://issues.apache.org/jira/browse/SLING-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu reassigned SLING-6651:
---
Assignee: Radu Cotescu
> Improve documentation for htl-maven-plugin
> ---
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928376#comment-15928376
]
Justin Edelson commented on SLING-6652:
---
Sorry, I'm not making myself clear. What I
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928334#comment-15928334
]
Dirk Rudolph commented on SLING-6652:
-
That indeed was my initial idea. Having 2 model
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928330#comment-15928330
]
Justin Edelson commented on SLING-6652:
---
Not necessarily a different implementation
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928263#comment-15928263
]
Justin Edelson edited comment on SLING-6652 at 3/16/17 4:03 PM:
On Thursday 16 March 2017 16:04:12 Konrad Windszus wrote:
> I am blocked for the release by the 0.0.3-SNAPSHOT testing dependency to
> org.apache.sling.testing.paxexam in validation.core. Is this gonna be
> released soon?
Yes, I will do some more releases which should be part of 0.0.4 and Sling 9
i've prepare a new PR with *only* a streaming API [1].
please have a new review on the API part.
it has a very simple ContentHandler interface which reports every resource
found with its map of properties - ordered as found in the source.
to keep the existing unit tests i added the handler that
[
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928282#comment-15928282
]
ASF GitHub Bot commented on SLING-6592:
---
GitHub user stefanseifert opened a pull req
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/203
SLING-6592 switch to stream-based API for ContentParser
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling
feature/SLING-
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928276#comment-15928276
]
Dirk Rudolph commented on SLING-6652:
-
You mean registering jackson exporter again wit
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928263#comment-15928263
]
Justin Edelson commented on SLING-6652:
---
The way I had anticipated this being handle
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6652:
---
Affects Version/s: Sling Models Impl 1.3.0
> Allow multiple adapters for Models with resourceT
I am blocked for the release by the 0.0.3-SNAPSHOT testing dependency to
org.apache.sling.testing.paxexam in validation.core.
Is this gonna be released soon? Otherwise would it be possible to revert to
0.0.2?
Konrad
> On 1 Mar 2017, at 09:03, Konrad Windszus wrote:
>
> Hi everyone,
> I think i
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928170#comment-15928170
]
Oliver Lietz commented on SLING-6653:
-
_when convenience is wanted_: it's "ok" to let
Ok, it sounds like 1) we are fine with deprecating all classes in the
commons.json bundle and do one more release (I'll increase the minor
number of the package version as well) and 2) replace exiting usage
inside sling with Johnzon. I'll start with the deprecation release
asap and then start to pr
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928163#comment-15928163
]
Oliver Lietz commented on SLING-6653:
-
The working directory is not mandatory for any
Some javadocs in
https://github.com/apache/sling/blob/trunk/testing/org.apache.sling.testing.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L862
would be really helpful, which explain under which circumstances you have to
use the methods with the workingDirectory and wh
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928118#comment-15928118
]
Konrad Windszus commented on SLING-6653:
Ok, but then we should at least make the
On Thursday 16 March 2017 13:45:44 Konrad Windszus wrote:
> Maybe this is related to
> https://issues.apache.org/jira/browse/SLING-4649?focusedCommentId=14508857&;
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#commen
> t-14508857. It seems that the Lucene index relies on a
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928007#comment-15928007
]
Oliver Lietz commented on SLING-6653:
-
{{slingLaunchpadOak()}} needs to be public in c
On Thursday 16 March 2017 13:54:23 Konrad Windszus wrote:
> Probably this commit
> https://github.com/apache/sling/blame/trunk/testing/org.apache.sling.testin
> g.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L
> 645 is not correct. The localIndexDir should be IMHO set as
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6653:
---
Description:
The method {{slingLaunchpadOak()}} should never be used directly instead there
s
[
https://issues.apache.org/jira/browse/SLING-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927977#comment-15927977
]
Konrad Windszus commented on SLING-6653:
[~olli] WDYT?
> Make slingLaunchpadOak()
Konrad Windszus created SLING-6653:
--
Summary: Make slingLaunchpadOak() private
Key: SLING-6653
URL: https://issues.apache.org/jira/browse/SLING-6653
Project: Sling
Issue Type: Improvement
On Thursday 16 March 2017 13:31:15 Konrad Windszus wrote:
> Hi,
Hi Konrad,
> it seems that PaxExam based ITs may create folders outside the target folder
> (see
> https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/
> ws/) For Validation the folder
> sling/repository/index/
Probably this commit
https://github.com/apache/sling/blame/trunk/testing/org.apache.sling.testing.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L645
is not correct. The localIndexDir should be IMHO set as absolute path (not
relative!) This is done correctly in
https://
Maybe this is related to
https://issues.apache.org/jira/browse/SLING-4649?focusedCommentId=14508857&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14508857.
It seems that the Lucene index relies on a framework property (named
repository.home) if this is not explicit
Hi,
it seems that PaxExam based ITs may create folders outside the target folder
(see
https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/ws/)
For Validation the folder sling/repository/index/lucene-1488547426482/data was
obviously created by PaxExam.
Usually the reposito
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927784#comment-15927784
]
Konrad Windszus commented on SLING-6652:
Registering multiple models on the same a
[
https://issues.apache.org/jira/browse/SLING-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927761#comment-15927761
]
Robert Munteanu commented on SLING-6519:
GSON would work for me. I think there's a
[
https://issues.apache.org/jira/browse/SLING-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927759#comment-15927759
]
Konrad Windszus commented on SLING-6519:
What about replacing it with Google GSON
[
https://issues.apache.org/jira/browse/SLING-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927754#comment-15927754
]
Robert Munteanu commented on SLING-6519:
We include it in the p2 repo as part of t
[
https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6618:
---
Priority: Blocker (was: Major)
> Specify crx.default as workspace for AEM servers
> -
[
https://issues.apache.org/jira/browse/SLING-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927752#comment-15927752
]
Konrad Windszus commented on SLING-6519:
Since we only consume a dependency being
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927751#comment-15927751
]
Dirk Rudolph commented on SLING-6652:
-
Currently only a warning is logged: "Skipped re
[
https://issues.apache.org/jira/browse/SLING-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927744#comment-15927744
]
Konrad Windszus edited comment on SLING-6345 at 3/16/17 9:51 AM:
---
[
https://issues.apache.org/jira/browse/SLING-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6345.
Resolution: Fixed
Fixed in [r1787148|http://svn.apache.org/r1787148].
> Publishing transfer
Dirk Rudolph created SLING-6652:
---
Summary: Allow multiple Adapters for Models with resourceType
binding
Key: SLING-6652
URL: https://issues.apache.org/jira/browse/SLING-6652
Project: Sling
Iss
[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirk Rudolph updated SLING-6652:
Summary: Allow multiple adapters for Models with resourceType binding
(was: Allow multiple Adapters
[
https://issues.apache.org/jira/browse/SLING-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-535.
Resolution: Won't Do
Sling Dojo moved to attic.
> Align Node and Property Stores with Dojo's upcomin
[
https://issues.apache.org/jira/browse/SLING-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-1723.
-
Resolution: Won't Do
Explorer moved to attic.
> jQuery JCR Explorer - step 2
> --
[
https://issues.apache.org/jira/browse/SLING-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-1859.
-
Resolution: Won't Fix
Explorer moved to attic.
> Multi-value string properties are not displayed
[
https://issues.apache.org/jira/browse/SLING-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-1648:
Affects Version/s: (was: Servlets Post 2.0.4)
Component/s: (was: Servlets)
> Node
[
https://issues.apache.org/jira/browse/SLING-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-1648.
-
Resolution: Fixed
Works with current Sling (Jackrabbit 2.14.0/Oak 1.6.1).
> Node move with :repla
76 matches
Mail list logo
