[
https://issues.apache.org/jira/browse/SLING-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-41.
--
Resolution: Fixed
First I added another implementation of the Content interface:
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532592
]
Felix Meschberger commented on SLING-31:
Hmm, the BundleDeployFileMojo has a Java five attribute (@Override)
Potential NullPointerException when initializing Components
---
Key: SLING-42
URL: https://issues.apache.org/jira/browse/SLING-42
Project: Sling
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532632
]
Felix Meschberger commented on SLING-31:
Thanks for the hint. I will update the the Sling parent pom to reer
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-31:
--
Assignee: Felix Meschberger
maven-sling-plugin: build failure caused by
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-31:
--
Attachment: pom.diff
Maven 2.07, I only had Maven Plugin Plugin 2.0 in my local m2 repo.
Adding Maven
[
https://issues.apache.org/jira/browse/SLING-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-31.
Resolution: Fixed
Fix Version/s: 2.0.0
Added
plugin
[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532653
]
Felix Meschberger commented on SLING-40:
Removed the old interfaces in the org.apache.sling.core.mapper
[
https://issues.apache.org/jira/browse/SLING-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-40.
--
Resolution: Fixed
This issue can be closed as the service has been implemented and the old
Hi all,
As we are new to the incubator, we have to report monthly and the
reports are due again :-)
I created a page on our wiki [1] to catch what we ultimately would
report. Please add anything you might feel needed such that we can
finalize the report by Oct. 10.
Thanks and Regards
Felix
[1]
Extend the sling-app project by support to build a complete jar file
Key: SLING-43
URL: https://issues.apache.org/jira/browse/SLING-43
Project: Sling
Issue Type:
[
https://issues.apache.org/jira/browse/SLING-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-43.
--
Resolution: Fixed
Commited the extend pom with a new build profile full, which builds said JAR
Felix Meschberger wrote:
Hi all,
Upon replying to Edgar's question regarding writing Content, I came to
thinking, that the ContentManager is a core interface of Sling and
probably should be made available more prominently. The most prominent
location for an interface in Sling would be the
On 5 Oct 2007, at 15:56, Felix Meschberger wrote:
What do you think of moving the o.a.s.content.ContentManager interface
to the Sling API and provide it through the ComponentRequest
instead of
having to access a request attribute:
public interface ComponentRequest extends
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because we initially did not extend
HttpServletRequest but
On 5 Oct 2007, at 17:30, Felix Meschberger wrote:
Hi Torgeir,
Am Freitag, den 05.10.2007, 17:25 +0100 schrieb Torgeir Veimo:
Having done some work recently with Day Communique, one of the
annoying things was that it subclasses HttpServletRequest.
Can you please elaborate on this ? Because
16 matches
Mail list logo
