The Buildbot has detected a restored build on builder sling-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/60
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3278:
---
Attachment: SLING-3278-bertrand.patch
Thanks for your patch! Lots of good ideas in
[
https://issues.apache.org/jira/browse/SLING-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3281:
---
Attachment: SLING-3281.3.patch
third patch also adding unit test for
Hi,
On Wed, Dec 11, 2013 at 10:00 AM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
...I suggest disabling the Jenkins builds - not deleting them for
now, but just turning them off
In the meantime, as noted in SLING-920 (thanks Robert!) some of the
build slaves have been upgraded to
[
https://issues.apache.org/jira/browse/SLING-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-2729.
--
Resolution: Fixed
Performance Testing suite: Modified ReportLogger to log the test case name
[
https://issues.apache.org/jira/browse/SLING-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850426#comment-13850426
]
Antonio Sanso commented on SLING-2729:
--
thanks [~andrei.dulvac] I have applied your
[
https://issues.apache.org/jira/browse/SLING-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-2727.
--
Resolution: Fixed
Allow PerformanceRunner to run tests provided by a factory method
[
https://issues.apache.org/jira/browse/SLING-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850431#comment-13850431
]
Antonio Sanso commented on SLING-2727:
--
thanks [~andrei.dulvac] I applied your patch
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.installer.it/440/
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/440/
See https://builds.apache.org/job/sling-trunk-1.7/440/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.commons.log/2070/
See https://builds.apache.org/job/sling-trunk-1.6/2070/changes
The Buildbot has detected a new failure on builder sling-trunk-oak while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk-oak/builds/50
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: downstream
Build
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/441/
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.installer.it/441/
See https://builds.apache.org/job/sling-trunk-1.7/441/changes
See https://builds.apache.org/job/sling-trunk-1.6/2071/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.commons.log/2071/
[
https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850757#comment-13850757
]
Robert Munteanu commented on SLING-2798:
Two comments here:
1. The code was
Hi,
I was looking at SLING-2881 [0] and reading the docu at [1]. the i18n
code has 1 queries, one is:
1) //element(*,mix:language)
and the other is
2)
//element(*,mix:language)[@jcr:language='en']//element(*,sling:Message)[@sling:message]/(@sling:key|@sling:message)
the first one is to find
Hi,
I was looking at SLING-2881 [0] and reading the docu at [1]. the i18n
code has 1 queries, one is:
1) //element(*,mix:language)
and the other is
2)
//element(*,mix:language)[@jcr:language='en']//element(*,sling:Message)[@sling:message]/(@sling:key|@sling:message)
the first one is to find
On 17.12.2013, at 14:05, Tobias Bocanegra tri...@apache.org wrote:
I was looking at SLING-2881 [0] and reading the docu at [1]. the i18n
code has 1 queries, one is:
1) //element(*,mix:language)
Unfortunately this is too broad, mix:language can be many nodes, depending on
the application.
Hi,
I try to compile the i18n support, but a SNAPSHOT dependency:
dependency
groupIdorg.apache.sling/groupId
artifactIdorg.apache.sling.paxexam.util/artifactId
version1.0-SNAPSHOT/version
scopetest/scope
/dependency
is missing. It
Georg Henzler created SLING-3293:
Summary: Make HC compatible to CQ 5.5/5.6/5.6.1
Key: SLING-3293
URL: https://issues.apache.org/jira/browse/SLING-3293
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-3293:
-
Attachment: missing-meta-data.PNG
Make HC compatible to CQ 5.5/5.6/5.6.1
[
https://issues.apache.org/jira/browse/SLING-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851131#comment-13851131
]
Carsten Ziegeler commented on SLING-3293:
-
I think we shouldn't go down this road
[
https://issues.apache.org/jira/browse/SLING-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851151#comment-13851151
]
Georg Henzler commented on SLING-3293:
--
Upgrading the metatype service
[
https://issues.apache.org/jira/browse/SLING-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851159#comment-13851159
]
Carsten Ziegeler commented on SLING-3293:
-
This shouldn't cause any side effects.
[
https://issues.apache.org/jira/browse/SLING-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-2881:
Attachment: sling-2881.r1551665.patch
proposed patch that implements alex's suggestion.
+1 I like the dictionary approach better as it reduces the amount of
complex queries.
for backward compatibility the resource bundle provider should
initially do a query for the new dictionaries and if found, go into
'dictionary' mode. if not, it would fall back to the old
mix:language approach.
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851212#comment-13851212
]
Alexander Klimetschek commented on SLING-3025:
--
This has been fixed by
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-3278:
-
Attachment: SLING-3278-hc.webconsole-2013-12-18.patch
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851218#comment-13851218
]
Georg Henzler commented on SLING-3278:
--
Hi Bertrand,
now we have two competing
On 17.12.2013, at 17:03, Tobias Bocanegra tri...@apache.org wrote:
+1 I like the dictionary approach better as it reduces the amount of
complex queries.
for backward compatibility the resource bundle provider should
initially do a query for the new dictionaries and if found, go into
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851397#comment-13851397
]
Carsten Ziegeler commented on SLING-3278:
-
Hi thanks for your patch -
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3025:
Component/s: (was: Console)
(was: Engine)
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3025.
-
Resolution: Fixed
Navigating to /system/console/servletresolver causes error 500
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-3025.
---
Navigating to /system/console/servletresolver causes error 500
What about if we add the migration code to the bundle?
2013/12/18 Alexander Klimetschek aklim...@adobe.com
On 17.12.2013, at 17:03, Tobias Bocanegra tri...@apache.org wrote:
+1 I like the dictionary approach better as it reduces the amount of
complex queries.
for backward
On 17.12.2013, at 22:03, Carsten Ziegeler cziege...@apache.org wrote:
What about if we add the migration code to the bundle?
Hmm, interesting :) Not sure though if we should modify content from such a
bundle. And how do we know that we already did the migration and don't run the
migration
The bundle can either set a marker in the repository or a file in the
bundle private date; the repository is the better place as this can be used
in a clustered installation to avoid duplicate or concurrent migration
Carsten
2013/12/18 Alexander Klimetschek aklim...@adobe.com
On 17.12.2013,
Hi,
On Wed, Dec 18, 2013 at 12:48 AM, Tobias Bocanegra tri...@apache.org wrote:
I try to compile the i18n support, but a SNAPSHOT dependency:
...
artifactIdorg.apache.sling.paxexam.util/artifactId
is missing...
It's in contrib/extensions/sling-pax-util - I'll work on getting it
43 matches
Mail list logo
