notes about the opinions of the participants at the "Committer Round Table" at
adaptTo() in berlin this year:
- karl reported there are some problem around J2EE packages that where includes
in J2SE 8, but no longer (by default) in J2SE 9
- this affects the felix system bundle exports, but also
notes about the opinions of the participants at the "Committer Round Table" at
adaptTo() in berlin this year:
- in the talk from dominik and karl [1] the new draft of a "sling feature"
(working title) was mentioned/introduced, which may/should be the replacement
for the currently separated
notes about the opinions of the participants at the "Committer Round Table" at
adaptTo() in berlin this year:
- the migration to jbake and git is ready and feels "good enough" to do the
real switch
- bertrand already started the mail poll to aks if someone has objections
- open issues: toc is
notes about the opinions of the participants at the "Committer Round Table" at
adaptTo() in berlin this year:
status report from robert:
- scripts to split existing svn repo in multiple git repos including (most of)
the history are ready
- history is not correctly preserved for modules that
yesterday the "Sling Committer Round Table" took place at the adaptTo() 2017
conference.
i took notes about the topics we discussed and will open a separate mail thread
for each topic with the prefix "[adaptTo-CRT]".
participants where: Nicolas, Carsten, Justin, Karl, Bertrand, Robert, Oliver,
the slides of the adaptTo() 2017 conference in berlin are now online - 24 talks
plus lightning talks, 200 participants.
you find the slides and code samples here:
https://adapt.to/2017/schedule
and some images... (more to follow)
https://adapt.to/2017/en/conference/gallery.html
this year we
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182819#comment-16182819
]
Carsten Ziegeler commented on SLING-7157:
-
Sure, that's possible as well. It depends on who ever
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182799#comment-16182799
]
Konrad Windszus commented on SLING-7157:
Wouldn't it be better to rely on the default
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182494#comment-16182494
]
Carsten Ziegeler commented on SLING-7157:
-
Fixed Commons Log in rev 1809842
>
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182488#comment-16182488
]
Bertrand Delacretaz edited comment on SLING-6955 at 9/27/17 12:37 PM:
--
[
https://issues.apache.org/jira/browse/SLING-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182488#comment-16182488
]
Bertrand Delacretaz commented on SLING-6955:
I have added client-side automatic table of
Hi,
On Wed, Sep 27, 2017 at 11:46 AM, Konrad Windszus wrote:
> ..With that stop-gap solution I am +1 on the replacement as
> well (although the TOC wouldn't be exposed on the GH mirror)...
Ok thanks!
I have implemented the toc.js generation based on Robert's idea, for
all
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: (was: DataSource Provider 1.0.0)
> metatype.properties file must not be
[
https://issues.apache.org/jira/browse/SLING-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-4397:
Fix Version/s: (was: DataSource Provider 1.0.0)
DataSource Provider
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: (was: DataSource Provider 1.0.2)
> metatype.properties file must not be
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: (was: Discovery Oak 1.2.12)
> metatype.properties file must not be in
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: (was: Discovery Oak 1.2.20)
> metatype.properties file must not be in
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182472#comment-16182472
]
Carsten Ziegeler commented on SLING-7157:
-
Fixed Commons Threads in rev 1809836
>
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: JCR Installer 3.1.28
SLF4J MDC Filter 1.0.2
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: DataSource Provider 1.0.4
SLF4J MDC Filter 1.0.0
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: JCR Webdav 2.3.10
JCR Davex 1.3.10
JCR
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Description:
According to the spec the metatype.properties file must not be inside the
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: JCR Web Console 1.0.2
JCR Registration 1.0.2
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: Settings 1.3.10
> metatype.properties file must not be in OSGI-INF/metatype
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: Discovery Impl 1.2.12
Discovery Oak 1.2.18
>
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: Commons Threads 3.2.10
Commons Log 5.0.4
>
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: Settings 1.3.8
> metatype.properties file must not be in
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: Discovery Oak 1.2.22
Discovery Oak 1.2.20
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Fix Version/s: Auth Core 1.4.2
Form Based Authentication 1.0.10
>
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: Form Based Authentication 1.0.8
Auth Core 1.4.0
>
[
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-7157:
Affects Version/s: Commons Threads 3.2.6
Commons Log 5.0.2
>
Carsten Ziegeler created SLING-7157:
---
Summary: metatype.properties file must not be in OSGI-INF/metatype
Key: SLING-7157
URL: https://issues.apache.org/jira/browse/SLING-7157
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182330#comment-16182330
]
Tobias Bocanegra commented on SLING-7155:
-
bq. Ok, but as mentioned before, precompiling the
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182316#comment-16182316
]
Tobias Bocanegra commented on SLING-7155:
-
one use case could be to pre-compile the scripts, so
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182323#comment-16182323
]
Radu Cotescu commented on SLING-7155:
-
Ok, but as mentioned before, precompiling the classes is
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182302#comment-16182302
]
Radu Cotescu commented on SLING-7155:
-
[~tripod], what exactly do you expect the plugin to generate?
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-7155:
Description:
It would be cool if the HTL Maven Plugin could precompile the HTL scripts,
similar to
[
https://issues.apache.org/jira/browse/SLING-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7155:
---
Affects Version/s: HTL Maven Plugin 1.0.8
> htl-maven-plugin: Add option to precompile the
> On 27. Sep 2017, at 11:43, Bertrand Delacretaz wrote:
>
> On Wed, Sep 27, 2017 at 10:42 AM, Robert Munteanu wrote:
>> ... As for the TOC, we can have a stop-gap solution with something like [1]
>> until we get proper support in JBake...
>
>
On Wed, Sep 27, 2017 at 10:42 AM, Robert Munteanu wrote:
>... As for the TOC, we can have a stop-gap solution with something like [1]
> until we get proper support in JBake...
That's a great idea.
The problem if we wait more to activate the website is that resyncing
to the
We can still generate a TOC manually - see
https://github.com/Adobe-Marketing-Cloud/htl-spec/blob/master/SPECIFICATION.md#contents
.
On Wed, 27 Sep 2017 at 10:49 Carsten Ziegeler wrote:
> I see your point with the TOC, the question is should we put the whole
> effort on
[
https://issues.apache.org/jira/browse/SLING-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-7156.
---
Resolution: Fixed
Done in r1809819.
> SlingTldLocationsCache makes invalid assumptions about bundle
Karl Pauls created SLING-7156:
-
Summary: SlingTldLocationsCache makes invalid assumptions about
bundle entry URL's
Key: SLING-7156
URL: https://issues.apache.org/jira/browse/SLING-7156
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182220#comment-16182220
]
Tomek Rękawek commented on SLING-7149:
--
[~joerghoh], yes, the new Sling Query 4.0.0 requires Java 8.
[
https://issues.apache.org/jira/browse/SLING-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182219#comment-16182219
]
Jörg Hoh commented on SLING-7149:
-
Hi Tomek,
does this mean, that Sling Query now requires Java 8 to run?
I see your point with the TOC, the question is should we put the whole
effort on hold because of this?
I'm leaning more to do the migration now, and one TOC support is there
we can use it. WIthout a TOC still all info is on the side and a search
brings you to the right place. I personally rarely
On Wed, 2017-09-27 at 10:33 +0200, Konrad Windszus wrote:
> I think we should include some hints which markdown format is
> supposed to be used.
> Currently I guess it is only https://daringfireball.net/projects/mark
> down/syntax but in the future once flexmark-java is included it is
> ought to
I think we should include some hints which markdown format is supposed to be
used.
Currently I guess it is only
https://daringfireball.net/projects/markdown/syntax but in the future once
flexmark-java is included it is ought to be http://spec.commonmark.org/0.28/ or
whatever version is current
Il giorno mer 27 set 2017 alle ore 09:12 Bertrand Delacretaz <
bdelacre...@apache.org> ha scritto:
> Hi Tommaso,
>
> On Wed, Sep 27, 2017 at 9:00 AM, Tommaso Teofili
> wrote:
> > ...In Sling however it might be too much to require to fire a PR for
> each and
> > every
[
https://issues.apache.org/jira/browse/SLING-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182166#comment-16182166
]
Carsten Ziegeler commented on SLING-7154:
-
We had a LRU cache initially but had to remove it as it
+1
Stefan Seifert wrote
> +1
>
> small issues that may still be present can be fixed later, i think we have no
> showstoppers.
>
> stefan
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
Tobias Bocanegra created SLING-7155:
---
Summary: htl-maven-plugin: Add option to precompile the HTL scripts
Key: SLING-7155
URL: https://issues.apache.org/jira/browse/SLING-7155
Project: Sling
Hi Tommaso,
On Wed, Sep 27, 2017 at 9:00 AM, Tommaso Teofili
wrote:
> ...In Sling however it might be too much to require to fire a PR for each and
> every commit, given the amount of active committers and commits we have on
> a weekly basis...
Do you mean that gitbox
sorry for the late replies, however moving from wip to gitbox was not hard
at all, Infra helped us and it went smooth.
With gitbox in OpenNLP we simply create a PR, check Travis results and
eventually click the "merge PR" button from github, which is fairly
different from most of the other ASF
54 matches
Mail list logo