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/77
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: forced: by IRC user
Robert Munteanu created SLING-3307:
--
Summary: Updated launchpad bundle list is not reflected after
upgrade
Key: SLING-3307
URL: https://issues.apache.org/jira/browse/SLING-3307
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862914#comment-13862914
]
Robert Munteanu commented on SLING-3307:
I've attached [^SLING-3307-repro.zip|a sa
[
https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862913#comment-13862913
]
Bertrand Delacretaz commented on SLING-3307:
We used to have a different upgra
[
https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3307:
---
Attachment: SLING-3307-repro.zip
> Updated launchpad bundle list is not reflected after upgra
On Fri, Jan 3, 2014 at 3:50 PM, Carsten Ziegeler wrote:
> ...I'm wondering if we still need the FeatureProvider? A Feature could be an
> OSGi service by itself
I agree, Feature then just needs a boolean isEnabled(ProviderContext
context) method.
The downside is that you then need one Feature
The Buildbot has detected a restored build on builder sling-trunk-oak while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk-oak/builds/78
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: downstream
Build
Hi,
I had a look at contrib/extensions/feature-flags and I'm wondering
about how to cope with a potentially null ClientContext.
IIUC the usage scenario is
1) Call Features.createClientContext(...) somewhere
2) Rendering or other code can then call
Features.getCurrentClientContext().isEnabled("f
(snip...)
>
> 2014 - a whishlist
> --
> - Documentation: This is nothing new and although it recently wasn't topic
> on the mailinglist this topic gets more and more important. Everytime I try
> to onboard a new dev on Slingbased projects I realize there is more and
> more of funct
anyone :) ?
On Dec 19, 2013, at 10:02 AM, Antonio Sanso wrote:
> hi *,
>
> in SLING-3290 [0] I have started to write some performance test regarding
> long startup time with many vanityPath or alias.
>
> As you might see from the attached graph the startup time increases
> considerably with
Hi,
On Mon, Jan 6, 2014 at 1:27 PM, Robert Munteanu wrote:
> ...So, are there any takers on coming up with more structured
> documentation, something like 'Essential Apache Sling' or 'Apache
> Sling in Action'? I would be one, but obviously lack the expertise to
> do this just by myself - and pro
On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso wrote:
> anyone :) ?...
I see only observations in
https://issues.apache.org/jira/browse/SLING-3290, what are you looking
for?
If it's agreement that long startup times are bad, I do agree ;-)
-Bertrand
On Jan 6, 2014, at 2:10 PM, Bertrand Delacretaz wrote:
> On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso wrote:
>> anyone :) ?...
>
> I see only observations in
> https://issues.apache.org/jira/browse/SLING-3290, what are you looking
> for?
>
right :)
It would be nice to try to come with an a
Hi,
On Mon, Jan 6, 2014 at 8:18 AM, Antonio Sanso wrote:
>
> On Jan 6, 2014, at 2:10 PM, Bertrand Delacretaz
> wrote:
>
>> On Mon, Jan 6, 2014 at 2:03 PM, Antonio Sanso wrote:
>>> anyone :) ?...
>>
>> I see only observations in
>> https://issues.apache.org/jira/browse/SLING-3290, what are you
On Mon, Jan 6, 2014 at 3:00 PM, Justin Edelson wrote:
> ...My personal opinion is that supporting 10k vanity paths is a non-goal,
> but that's just me :)...
I would agree but users are creative sometimes ;-)
Worst case, we might provide a way to disable the default vanity paths
handling complete
The Buildbot has detected a new failure on builder sling-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/99
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp
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/100
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source S
On Wed, Jan 1, 2014 at 2:27 PM, Dominik Süß wrote:
>
> - DevOps optimization: this includes setup, patching, monitoring and
> scalling of installations. Ian did start a corresponding thread in November
> and I hope this discussion will be pickedup to really fulfill the promise
> of a horizontally
18 matches
Mail list logo
