[
https://issues.apache.org/jira/browse/SLING-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed SLING-471.
---
Perfect, thanks for fixing the slf4j version I missed.
> LogService to implement JCL 1.
[
https://issues.apache.org/jira/browse/SLING-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson updated SLING-471:
Attachment: SLING-471.patch
A patch using the recently release SLF4J 1.5.2 which contains
[
https://issues.apache.org/jira/browse/SLING-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601147#action_12601147
]
Niklas Gustavsson commented on SLING-472:
-
Btw, will a new snapshot be publi
[
https://issues.apache.org/jira/browse/SLING-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed SLING-472.
---
Works like a charm, thanks!
> Let ServletContextResourceProvider fall back to loading from
[
https://issues.apache.org/jira/browse/SLING-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600476#action_12600476
]
Niklas Gustavsson commented on SLING-472:
-
On Wed, May 28, 2008 at 3:15 PM, F
On Tue, May 27, 2008 at 12:19 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Dienstag, den 27.05.2008, 11:29 +0200 schrieb Niklas Gustavsson:
> I have applied your patch to my local checkout and currently am
> investigating it. I think it does make sense at first sight.
&g
On Fri, May 23, 2008 at 11:41 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Freitag, den 23.05.2008, 11:35 +0200 schrieb Niklas Gustavsson:
>> I would also add that the static fields might actually be used by
>> clients who want to configure the JCL behavior.
>
>
On Fri, May 23, 2008 at 11:16 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Looking at this report, there is one method - objectId(Object) - which
> is not clearly destined at creating a LogFactory implementation.
>
> So my question with respect to JCL is: Do these bundles really require
> 1.1
[
https://issues.apache.org/jira/browse/SLING-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599303#action_12599303
]
Niklas Gustavsson commented on SLING-471:
-
A CLIRR diff between 1.0.4 and 1
[
https://issues.apache.org/jira/browse/SLING-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed SLING-470.
---
Perfect, thanks
> ClassLoaderResourceProvider loads from a hardcoded path rather than the
[
https://issues.apache.org/jira/browse/SLING-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson updated SLING-472:
Attachment: SLING-472.patch
A suggested patch, needs detailed review from more experienced
Type: Improvement
Components: Launchpad
Affects Versions: 2.0.0
Reporter: Niklas Gustavsson
Let ServletContextResourceProvider search on the class path if resources are
not found from the servlet context. This allows the launcher/base JAR to be
used directly within a
Reporter: Niklas Gustavsson
Some bundles have dependencies to org.apache.commons-logging 1.1.1 while
LogService only provides 1.0.4. Could LogService provide support for 1.1.1?
SLF4J which is currently used only provides support for 1.0.4 so a different
solution would be required
[
https://issues.apache.org/jira/browse/SLING-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed SLING-469.
---
Looks good, thanks!
> LogService logger to implement LocationAwareLog
/SLING-470
Project: Sling
Issue Type: Bug
Components: Launchpad
Reporter: Niklas Gustavsson
Attachments: SLING-470.patch
ClassLoaderResourceProvider.getChildren takes a path parameter but uses a
hardcoded Sling.CONFIG_PROPERTIES.
--
This
[
https://issues.apache.org/jira/browse/SLING-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson updated SLING-470:
Attachment: SLING-470.patch
> ClassLoaderResourceProvider loads from a hardcoded p
[
https://issues.apache.org/jira/browse/SLING-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson updated SLING-469:
Attachment: SLING-469.patch
Implements LocationAwareLogger. Note that this extends the data
Log
Affects Versions: 2.0.0
Reporter: Niklas Gustavsson
Some libraries (specifically Spring in this case) requires that the logger is
an LocationAwareLogger or it will fail. LocationAwareLogger is a logger that
can log the FQCN and extends the Logger interface that is currently
Hey
On Thu, Apr 17, 2008 at 9:46 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Yes, this is correct. The webapp launcher is a Sling speciality, so to
> say.
Good, so I'm not completely lost then :-) Anyways, the webapp launcher
is fine the way it is now, but since it's a pretty general OSG
On Wed, Apr 16, 2008 at 5:54 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> What you of course can do, if you only need the console, is to use the
> Felix main programm and add the console as well as any additional
> requirements there. To run the console, you do not need anything from
> th
On Wed, Apr 16, 2008 at 1:22 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> I'm currently using the launchpad/webapp to build my own webapp. All I need
> from the webapp are the configuration files for Sling and the classes which
> launch Sling; no bundles etc.
> Now, this works, but unfortuna
Felix Meschberger wrote:
Hi Niklas,
This is a result of incorrectly packing the launcher application. The
Felix framework overwrites some classes in the OSGi libraries. Yet these
overwrites were again overwritten by the original classes when packaging
the launcher.
I deployed a modified pom.xml
Hi
OSGi nood, so bare with me :-)
I'm trying to deploy bundles built on Spring-DM in Sling but run into
troubles using osgi:reference construct. Looks like the Spring-DM
implementation tries to use FrameworkUtil but runs into class loading
issues. When starting up Sling using mvn jetty:run I
23 matches
Mail list logo
