[
https://issues.apache.org/jira/browse/SLING-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-529.
---
Resolution: Fixed
Fixed in Rev. 667371.
Now global configuration sets the value for the
JspScriptEngineFactory throws NullPointerException on deactivate
Key: SLING-530
URL: https://issues.apache.org/jira/browse/SLING-530
Project: Sling
Issue Type: Bug
Hi,
On Thu, Jun 12, 2008 at 1:45 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
In Rev. 667038 I just commited a proposal to commons/log bundle [1] to
what we have been discussing:
Looks good.
- The disclaimer is not part of the README.txt (yet), maybe
this should be added as a section
On Jun 13, 2008, at 12:54 AM, Jukka Zitting wrote:
- The src/main/resources/META-INF(LICENSE file has no reference
to the LICENSE.slf4j file
The LICENSE.* files seem pretty obvious, so I'm not sure if the
reference is really needed. I'd say we either leave it as is (no
references), or include
launcher/app: Restarting the OPS4J Pax Server fails
---
Key: SLING-531
URL: https://issues.apache.org/jira/browse/SLING-531
Project: Sling
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/SLING-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-531.
---
Resolution: Fixed
Fixed in Rev. 667440.
The launcher/app now includes the Servlet API and
Hi,
It seems that there has been a change in the default scope of the http
client and in addition the transitive dependency on commons loggin has
been removed. Fixing this now with SLING-532.
Regards
Felix
Am Donnerstag, den 12.06.2008, 17:51 +0200 schrieb Alexander
Klimetschek:
Hi Sling
[
https://issues.apache.org/jira/browse/SLING-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-532.
---
Resolution: Fixed
Fixed scope and missing dependency in Rev. 667511. Works now.
Latest
Latest maven-sling-plugin fails to run due to missing dependencies
--
Key: SLING-532
URL: https://issues.apache.org/jira/browse/SLING-532
Project: Sling
Issue Type: Bug
Hi,
I think we should require the latest maven version 2.0.9, as this one
seems to be more stable than 2.0.7.
If noone objects, I'll update the parent pom before the release.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Hi,
Am Freitag, den 13.06.2008, 14:56 +0200 schrieb Carsten Ziegeler:
Hi,
I think we should require the latest maven version 2.0.9, as this one
seems to be more stable than 2.0.7.
Does it help fix the OutOfMemoryError issue we have ?
If not, I would not require 2.0.9 for now as our build
Thanks, it works now. Only changing Sling Logging Configuration
(org.apache.sling.commons.log.LogManager) worked, changing the log
level in Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config) did have no
effect.
Regards,
Alex
2008/6/13 Felix Meschberger
Hi,
Am Freitag, den 13.06.2008, 15:13 +0200 schrieb Alexander Klimetschek:
Thanks, it works now. Only changing Sling Logging Configuration
(org.apache.sling.commons.log.LogManager) worked,
This is the global configuration
changing the log
level in Sling Logging Logger Configuration
Felix Meschberger wrote:
Does it help fix the OutOfMemoryError issue we have ?
No, it doesn't.
If not, I would not require 2.0.9 for now as our build just as well
works with 2.0.7.
Hmm, not sure - yes, it works with 2.0.7 - but it seems that people new
to maven haven less problems if they
[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-522:
---
Fix Version/s: (was: 2.0.1)
2.1.0
Moving this to a later release for
[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604897#action_12604897
]
Carsten Ziegeler commented on SLING-522:
The problem is the detection of the
Hi,
I've changed the handling of the notice/licence files as discussed
recently. Each module has now a readme as well.
So I think it's time to review this stuff and fix what needs to be fixed
for a release. I hope we get through all of this by monday and can
finally release Sling :)
Most
[
https://issues.apache.org/jira/browse/SLING-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-521.
--
Resolution: Fixed
We have reverted, so we can close this issue.
Revert to hand written notice
[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604905#action_12604905
]
Julian Sedding commented on SLING-522:
--
Agreed,. The explicit hint will allow for the
Support mulit-value type hints (eg. @TypeHint=String[])
---
Key: SLING-533
URL: https://issues.apache.org/jira/browse/SLING-533
Project: Sling
Issue Type: New Feature
Components:
[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604911#action_12604911
]
Alexander Klimetschek commented on SLING-522:
-
I have the same problem (same use
[
https://issues.apache.org/jira/browse/SLING-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-533:
Summary: Support multi-value type hints (eg. @TypeHint=String[]) (was:
Support
[
https://issues.apache.org/jira/browse/SLING-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605013#action_12605013
]
Eric Norman commented on SLING-522:
---
I encountered this issue as well. My solution was
Multi-Value Reference properties are not exposed to scripting the same way as
single-value reference properties
---
Key: SLING-534
URL:
24 matches
Mail list logo
