+1
Thanks for preparing them !
Regards
Felix
Am Dienstag, den 18.01.2011, 10:35 + schrieb Carsten Ziegeler:
Hi,
this is another set of new releases for SLING-6. I think we're nearly
through now...
Most of these releases are minor bug fix releases. But I think it's
better to
[
https://issues.apache.org/jira/browse/SLING-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-1938:
Assignee: Felix Meschberger
Mapping might not consider current scheme
[
https://issues.apache.org/jira/browse/SLING-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984178#action_12984178
]
Felix Meschberger commented on SLING-1938:
--
Further clarification: Consider a
[
https://issues.apache.org/jira/browse/SLING-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984209#action_12984209
]
Carsten Ziegeler commented on SLING-1940:
-
I think the resource path should already
[
https://issues.apache.org/jira/browse/SLING-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1938.
--
Resolution: Fixed
Fixed in Rev. 1061315 by checking potential mappings for a mapping
I have been thinking about an easier way to upgrade our application,
which now consists of something like 100 bundles. We run on multiple
servers, and upgrading them bundle-by-bundle is really tedious.
I know I can update bundles directly from an OSGi repository, via the
web console at
Did you have a look at ace already (http://incubator.apache.org/ace/)?
regards,
Karl
On Thu, Jan 20, 2011 at 4:11 PM, Vidar Ramdal vi...@idium.no wrote:
I have been thinking about an easier way to upgrade our application,
which now consists of something like 100 bundles. We run on multiple
On Thu, Jan 20, 2011 at 4:11 PM, Vidar Ramdal vi...@idium.no wrote:
I have been thinking about an easier way to upgrade our application,
which now consists of something like 100 bundles. We run on multiple
servers, and upgrading them bundle-by-bundle is really tedious.
I know I can update
BindingsValuesProvider implementations can't overwrite non-core properties
during inclusion
---
Key: SLING-1941
URL: https://issues.apache.org/jira/browse/SLING-1941
While troubleshooting SLING-1941, I noticed that it doesn't seem like the
FLUSH key is set. It's definitely not happening explicitly inside
DefaultSlingScript.verifySlingBindings(). And it isn't happening the
service() either.
Is the intent that FLUSH is set by the script itself?
Thanks,
Justin
[
https://issues.apache.org/jira/browse/SLING-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984521#action_12984521
]
Justin Edelson commented on SLING-1941:
---
fixed in r1061592 and r1061593. protected
[
https://issues.apache.org/jira/browse/SLING-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson resolved SLING-1941.
---
Resolution: Fixed
BindingsValuesProvider implementations can't overwrite non-core
12 matches
Mail list logo