Hi,
On Thu, Sep 27, 2018 at 9:37 AM Christian Schneider
wrote:
> ...I agree we should offer to move health checks to felix.
> As this will be a breaking change anyway I propose we take the chance to
> review the API...
Why would that be a breaking change?
Changing package names to
[
https://issues.apache.org/jira/browse/SLING-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco resolved SLING-7957.
-
Resolution: Fixed
Assignee: Dan Klco
Fixed in
[
https://issues.apache.org/jira/browse/SLING-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco resolved SLING-7958.
-
Resolution: Fixed
Fixed in
Please confirm you are joking. :)
On Thu, Sep 27, 2018, 14:04 Karl Pauls wrote:
> Na, that would be boring ;-)
>
> regards,
>
> Karl
>
>
> On Thu, Sep 27, 2018 at 1:55 PM Radu Cotescu wrote:
> >
> > Hi Karl,
> >
> > Could you please make sure that when you create them they are:
> >
> >
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Description:
The following features from either standard JCR 2.0 or extended docview
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Summary: ContentParser: Complete support for (Extended) DocView (was:
ContentParser:
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Description:
The following features from either standard JCR 2.0 or extended docview
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Description:
The following features from either standard JCR 2.0 or extended docview
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Comment: was deleted
(was: The first feature is not 100% compatible with the current
Team,
I was going to suggest that we link to the Github sites from the Downloads
page, but while i was testing the concept, I found some major issues with
the list of downloads. There are 34 different downloads which do not map to
a GitHub repository.
Based on some analysis, I believe the
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630459#comment-16630459
]
Konrad Windszus edited comment on SLING-7959 at 9/27/18 1:57 PM:
-
The
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630459#comment-16630459
]
Konrad Windszus edited comment on SLING-7959 at 9/27/18 1:56 PM:
-
The
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630459#comment-16630459
]
Konrad Windszus edited comment on SLING-7959 at 9/27/18 1:55 PM:
-
The
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630459#comment-16630459
]
Konrad Windszus commented on SLING-7959:
The first feature is not 100% compatible with the
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Description:
The following features from extended docview
[
https://issues.apache.org/jira/browse/SLING-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7959:
---
Affects Version/s: (was: JCR ContentLoader 2.2.6)
JCR Content
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630267#comment-16630267
]
Konrad Windszus edited comment on SLING-5922 at 9/27/18 1:47 PM:
-
After
Konrad Windszus created SLING-7959:
--
Summary: ContentParser: Complete support for Extended DocView
Key: SLING-7959
URL: https://issues.apache.org/jira/browse/SLING-7959
Project: Sling
Issue
I agree we should offer to move health checks to felix.
As this will be a breaking change anyway I propose we take the chance to
review the API and impl and eventually do changes before a first release at
felix.
Christian
Am Mo., 24. Sep. 2018 um 18:05 Uhr schrieb Georg Henzler <
Dan Klco created SLING-7958:
---
Summary: Add Note in Documentation on Name of Site Configuration
Key: SLING-7958
URL: https://issues.apache.org/jira/browse/SLING-7958
Project: Sling
Issue Type:
Dan Klco created SLING-7957:
---
Summary: CMS - Reference - Fix Path of Reference App Template
Key: SLING-7957
URL: https://issues.apache.org/jira/browse/SLING-7957
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630303#comment-16630303
]
ASF GitHub Bot commented on SLING-7941:
---
bosschaert commented on issue #4: SLING-7941 - Use
bosschaert commented on issue #4: SLING-7941 - Use streaming APIs to marshall
the Feature to JSON
URL:
https://github.com/apache/sling-org-apache-sling-feature-io/pull/4#issuecomment-425071605
Thanks @simonetripodi I rebased and squashed your commits to make it easier
to see the changes.
[
https://issues.apache.org/jira/browse/SLING-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630301#comment-16630301
]
ASF GitHub Bot commented on SLING-7941:
---
bosschaert closed pull request #4: SLING-7941 - Use
bosschaert closed pull request #4: SLING-7941 - Use streaming APIs to marshall
the Feature to JSON
URL: https://github.com/apache/sling-org-apache-sling-feature-io/pull/4
This is an automated message from the Apache Git
Na, that would be boring ;-)
regards,
Karl
On Thu, Sep 27, 2018 at 1:55 PM Radu Cotescu wrote:
>
> Hi Karl,
>
> Could you please make sure that when you create them they are:
>
> sling-org-apache-sling-jcr-packageinit
> sling-org-apache-sling-feature-extension-content
>
> This would preserve
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630267#comment-16630267
]
Konrad Windszus edited comment on SLING-5922 at 9/27/18 12:00 PM:
--
After
Hi Karl,
Could you please make sure that when you create them they are:
sling-org-apache-sling-jcr-packageinit
sling-org-apache-sling-feature-extension-content
This would preserve consistency with the already 280+ existing modules.
Cheers,
Radu
> On 27 Sep 2018, at 12:48, Karl Pauls wrote:
>
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630267#comment-16630267
]
Konrad Windszus edited comment on SLING-5922 at 9/27/18 11:53 AM:
--
After
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5922:
---
Comment: was deleted
(was: The implementation should try to reuse the classes from
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630267#comment-16630267
]
Konrad Windszus edited comment on SLING-5922 at 9/27/18 11:50 AM:
--
After
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5922:
---
Affects Version/s: Testing Sling Mock 2.3.4
> allow sling mock to load content from jcrvlt's
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630267#comment-16630267
]
Konrad Windszus commented on SLING-5922:
After checking more I think
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630257#comment-16630257
]
Konrad Windszus edited comment on SLING-5922 at 9/27/18 11:39 AM:
--
The
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630257#comment-16630257
]
Konrad Windszus commented on SLING-5922:
The implementation should try to reuse the classes from
[
https://issues.apache.org/jira/browse/SLING-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630258#comment-16630258
]
ASF GitHub Bot commented on SLING-7941:
---
simonetripodi commented on issue #4: SLING-7941 - Use
simonetripodi commented on issue #4: SLING-7941 - Use streaming APIs to
marshall the Feature to JSON
URL:
https://github.com/apache/sling-org-apache-sling-feature-io/pull/4#issuecomment-425058241
thanks for the clarification @bosschaert , I should have successfully
managed to rebase and
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5922:
---
Component/s: JCR
> allow sling mock to load content from jcrvlt's xml
>
[
https://issues.apache.org/jira/browse/SLING-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5922:
---
Affects Version/s: JCR Content Parser 1.2.6
> allow sling mock to load content from jcrvlt's
[
https://issues.apache.org/jira/browse/SLING-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630197#comment-16630197
]
ASF GitHub Bot commented on SLING-7941:
---
bosschaert commented on issue #4: SLING-7941 - Use
bosschaert commented on issue #4: SLING-7941 - Use streaming APIs to marshall
the Feature to JSON
URL:
https://github.com/apache/sling-org-apache-sling-feature-io/pull/4#issuecomment-425048243
Hi @simonetripodi yes, a change was made to limit includes to a single one.
So
All,
I'm planning to create two new repositories namely,
org.apache.sling.jcr.packageinit
org.apache.sling.feature.extension.content
for the two modules currently in the whiteboard at:
https://github.com/apache/sling-whiteboard/tree/master/packageinit
[
https://issues.apache.org/jira/browse/SLING-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630052#comment-16630052
]
ASF GitHub Bot commented on SLING-7941:
---
simonetripodi commented on issue #4: SLING-7941 - Use
simonetripodi commented on issue #4: SLING-7941 - Use streaming APIs to
marshall the Feature to JSON
URL:
https://github.com/apache/sling-org-apache-sling-feature-io/pull/4#issuecomment-425024554
hi there @bosschaert ,
unfortunately once fixed the rebase, there is an API conflict
[
https://issues.apache.org/jira/browse/SLING-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629891#comment-16629891
]
Carsten Ziegeler commented on SLING-7934:
-
Some more questions:
- is the same JSONObject instance
45 matches
Mail list logo
