Felix Meschberger schrieb:
Hi all,
triggered by Paul Noden's JSON import support for the SlingPostServlet,
I have started to think about generalized support for import/export of
repository content. I imagine, that we would have single bundle, which
provides support for import and export of
[
https://issues.apache.org/jira/browse/SLING-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-446:
--
Assignee: Carsten Ziegeler
Move Scheduling to commons
--
[
https://issues.apache.org/jira/browse/SLING-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-450:
--
Assignee: Carsten Ziegeler
Move bundles from sling to extensions
[
https://issues.apache.org/jira/browse/SLING-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-450.
--
Resolution: Fixed
Moved all bundles to extensions
Move bundles from sling to extensions
[
https://issues.apache.org/jira/browse/SLING-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-446.
--
Resolution: Fixed
Moved and refactored to commons package.
Move Scheduling to commons
Initial content loading to target location
--
Key: SLING-453
URL: https://issues.apache.org/jira/browse/SLING-453
Project: Sling
Issue Type: Improvement
Components: Repository
Affects
Hi,
Am Mittwoch, den 14.05.2008, 10:23 +0200 schrieb Carsten Ziegeler:
Hi,
should we also rename the package from core to engine (and everything
else)? I think so, but I just wanted to check before doing :)
Yes, I would say so, too.
In addtion: the core (or engine) bundle provides API.
[
https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado reassigned SLING-453:
---
Assignee: Juan Jose Vazquez Delgado
Initial content loading to
Felix Meschberger wrote:
Hi,
Am Mittwoch, den 14.05.2008, 10:23 +0200 schrieb Carsten Ziegeler:
Hi,
should we also rename the package from core to engine (and everything
else)? I think so, but I just wanted to check before doing :)
Yes, I would say so, too.
In addtion: the core (or
Hi,
On Wed, May 14, 2008 at 11:04 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Jukka Zitting (JIRA) wrote:
Why is the scheduler bundle needed? Can't Sling use Quartz directly?
The scheduler bundle makes scheduling tasks much simpler than directly
using Quartz; it uses Quartz underneath
Hi,
Am Mittwoch, den 14.05.2008, 10:42 +0200 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Hi,
Am Mittwoch, den 14.05.2008, 10:23 +0200 schrieb Carsten Ziegeler:
Hi,
should we also rename the package from core to engine (and everything
else)? I think so, but I just wanted to
[
https://issues.apache.org/jira/browse/SLING-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-449.
--
Resolution: Fixed
Move core to engine and renamed the packages, the artifact id and
[
https://issues.apache.org/jira/browse/SLING-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-451:
--
Assignee: Carsten Ziegeler
Rename current sling directory to servlets
[
https://issues.apache.org/jira/browse/SLING-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-451.
--
Resolution: Fixed
Directory has been renamed.
servlets-get has been renamed to servlets/get and
[
https://issues.apache.org/jira/browse/SLING-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596738#action_12596738
]
Felix Meschberger commented on SLING-422:
-
That is ok.
The modified
in ESP, %= currentNode.x % should output a javascript.compatible Date string
--
Key: SLING-454
URL: https://issues.apache.org/jira/browse/SLING-454
Project: Sling
Felix Meschberger wrote:
...
Sling-Initial-ContentSLING-INFO/content;path:=/root/location/Sling-Initial-Content
Is there any code available for parsing this information? I think it
would make sense to put this into the commons/osgi module, so each and
every bundle can make use of it. We use
Hi,
Am Mittwoch, den 14.05.2008, 16:30 +0200 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
...
Sling-Initial-ContentSLING-INFO/content;path:=/root/location/Sling-Initial-Content
Is there any code available for parsing this information? I think it
would make sense to put this
[
https://issues.apache.org/jira/browse/SLING-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596781#action_12596781
]
Felix Meschberger commented on SLING-422:
-
Implemented changes described above in
Hi,
On Wed, May 14, 2008 at 4:40 PM, Felix Meschberger [EMAIL PROTECTED]
wrote:
I agree, that it would make sense to have this parseHeader code in the
commons/osgi module for multiple uses.
Now, the commons/osgi module has one class only: OsgiUtils. Doy you mean we
should have a
[
https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado updated SLING-453:
Assignee: (was: Juan Jose Vazquez Delgado)
Afaik, until now the
[
https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596880#action_12596880
]
Felix Meschberger commented on SLING-453:
-
Sounds reasonable.
Initial content
Hi,
Am Mittwoch, den 14.05.2008, 18:46 +0200 schrieb Juan José Vázquez
Delgado:
Hi,
On Wed, May 14, 2008 at 4:40 PM, Felix Meschberger [EMAIL PROTECTED]
wrote:
I agree, that it would make sense to have this parseHeader code in the
commons/osgi module for multiple uses.
Now, the
Hi all,
I keep getting this error since a recent update:
Exception while parsing APT content:
org.apache.sling.apt.parser.internal.SlingAptParseExceptionImpl: missing
'}' (500)
The requested URL /jcr-explorer/data/demo/browser.html resulted in an
error in
24 matches
Mail list logo
