[jira] Created: (SLING-865) Source Tree Restructuring

Source Tree Restructuring - Key: SLING-865 URL: https://issues.apache.org/jira/browse/SLING-865 Project: Sling Issue Type: Task Components: Extensions Reporter: Carsten Ziegeler

Re: [VOTE] Apply patch for SLING-864

+1 for applying. Carsten -- Carsten Ziegeler cziege...@apache.org

Re: [Fwd: [groovy-dev] Groovy 1.6 is released!]

+1 to include Groovy. Carsten -- Carsten Ziegeler cziege...@apache.org

[IMP] Source Tree Restructuring

Hi, I'll start with SLING-865 which might break the build during the changes. I'll let you know as soon as everything should be working again. Carsten -- Carsten Ziegeler cziege...@apache.org

Re: glassfishv3-prelude sling incubator-4

Hi John, John Langley schrieb: Just FYI... I tried loading the launchpad webapp into glassfishv3-prelude this afternoon and it threw exception stack included below. My guess is that this is related to there being different versions of the org.apache.felix.framework.Felix because

[jira] Created: (SLING-866) Shield Sling from the classes and resources in the environment

Shield Sling from the classes and resources in the environment -- Key: SLING-866 URL: https://issues.apache.org/jira/browse/SLING-866 Project: Sling Issue Type: Improvement

[jira] Updated: (SLING-866) Shield Sling from the classes and resources in the environment

[ https://issues.apache.org/jira/browse/SLING-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-866: Description: As noted in [1], Sling suffers from leaking classes from the environment. This

Re: [IMP] Source Tree Restructuring

Ok, I'm through with the changes. Trunk compiles for me and the integration tests are running fine. I guess the integration tests in the contrib part need more cleanup. If you experience any problems, just let us know. Thanks Carsten Carsten Ziegeler wrote: Hi, I'll start with SLING-865

Re: [IMP] Source Tree Restructuring

Hi Carsten, Many thanks. Regards Felix Carsten Ziegeler schrieb: Ok, I'm through with the changes. Trunk compiles for me and the integration tests are running fine. I guess the integration tests in the contrib part need more cleanup. If you experience any problems, just let us know.

Re: glassfishv3-prelude sling incubator-4

Hi John, Yet another reply ;-) In Rev. 746794 I have added a LauncherClassLoader which helps using Sling inside Glassfish (at least in my simple setup here). Regards Felix John Langley schrieb: Just FYI... I tried loading the launchpad webapp into glassfishv3-prelude this afternoon and

[jira] Resolved: (SLING-866) Shield Sling from the classes and resources in the environment

[ https://issues.apache.org/jira/browse/SLING-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-866. - Resolution: Fixed Created a LauncherClassLoader (extends URLClassLoader) in Rev. 746794,

Sling Parent POM (was: felix.service.urlhandlers disabled?)

Hi, John Langley schrieb: Any chance that the sling project will being using the apache snapshot repository? Currently the README.txt in the trunk root instructs to add the Apache Snapshot repository to the local settings.xml. I agree with John, that we should add this declaration to the

Re: [IMP] Source Tree Restructuring

If you experience any problems, just let us know. No problems. Works for me (Mac OS X 10.5.6 / Java 1.6.0_07). Thanks BR, Juanjo.

Re: How to bind session to a newly logged in session

I tried that ?sling:authRequestLogin but since anonymous does not have read access to that node I get a 404. The problem is even when I log into the CRX content explorer with a username that has access to my node, I still get a 404 if I try to surf it as this user. How can I make the

Re: How to bind session to a newly logged in session

Hi Josh, Joshua Oransky schrieb: I tried that ?sling:authRequestLogin but since anonymous does not have read access to that node I get a 404. The problem is even when I log into the CRX content explorer with a username that has access to my node, I still get a 404 if I try to surf it as this