[jira] Created: (SLING-1694) Instantiate adapter factories lazy
Instantiate adapter factories lazy -- Key: SLING-1694 URL: https://issues.apache.org/jira/browse/SLING-1694 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Adapter 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Adapter 2.0.6 The adapter factories can be instantiated lazy to reduce service instantiation on startup and improve overall startup performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1694) Instantiate adapter factories lazy
[ https://issues.apache.org/jira/browse/SLING-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1694. - Resolution: Fixed Changed in revision 989023 > Instantiate adapter factories lazy > -- > > Key: SLING-1694 > URL: https://issues.apache.org/jira/browse/SLING-1694 > Project: Sling > Issue Type: Improvement > Components: Extensions >Affects Versions: Adapter 2.0.4 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: Adapter 2.0.6 > > > The adapter factories can be instantiated lazy to reduce service > instantiation on startup and improve overall startup performance -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
osgi.installer integration tests are hanging
Hi With the newest trunk the osgi.installer integration tests are hanging, without displaying an error. best regards mike output from maven: __ ___ \__ \_ ___ ___ \_ _/__ _ | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ || / __ \_>< |\>< / __ \| Y Y \ ||( /__/\_ \ /___ /__/\_ \( /__|_| / \/ \/ \/ \/ \/ \/ Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org 25.08.2010 14:14:09.083 *INFO* [main] org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test testRemoveResourc eAndRestart [felix](org.apache.sling.osgi.installer.it.RemovedResourceDetectionTest) 25.08.2010 14:14:09.161 *INFO* [main] org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Starting up the t est container (Pax Runner 1.4.0 ) 25.08.2010 14:14:09.161 *INFO* [main] org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Acquire lock for new Pax Runner instance on C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock 25.08.2010 14:14:09.177 *INFO* [main] org.ops4j.pax.runner.ConfigurationImpl Using config [classpath:META-INF/runner.pro perties] 25.08.2010 14:14:09.192 *INFO* [main] org.ops4j.pax.runner.Run Using only arguments from command line 25.08.2010 14:14:09.255 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.exam/pax-exam/1@1] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.apache.felix/org.apache.felix.scr] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.apache.felix/org.apache.felix.configadmin] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.apache.sling/org.apache.sling.commons.log] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-snaps...@update] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.junit/com.springsource.org.junit/4@1] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] 25.08.2010 14:14:09.271 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-compos ite:mvn:org.ops4j.pax.runner.profiles/log//composite] 25.08.2010 14:14:09.286 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] 25.08.2010 14:14:09.286 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] 25.08.2010 14:14:09.286 *INFO* [main] org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from [scan-bundle :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, at start level 1, bundle will be started, bundle will be loaded from the cache] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e xtender/1.2.1, at start level 1, bundle will be started, bundle will be loaded from the cache] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e xtender-impl/1.2.1, at start level 1, bundle will be started, bundle will be loaded from the cache] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.apache.felix/org.apache.felix.s cr, at default start level, bundle will be started, bundle will be loaded from the cache] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.apache.felix/org.apache.felix.c onfigadmin, at default start level, bundle will be started, bundle will be loaded from the cache] 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision bundle [mvn:org.apache.sling/org.apache.sling.c ommons.log, at default start level, bundle will be started, bundle will be loaded from t
[VOTE] Release Commons ClassLoader 1.2.0 and JCR ClassLoader 3.1.2
Hi, We solved some issues in the classloaders: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314758 https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314757 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-143/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 143 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. -- Carsten Ziegeler cziege...@apache.org
Re: osgi.installer integration tests are hanging
Mike Müller wrote > Hi > > With the newest trunk the osgi.installer integration tests are hanging, > without displaying an error. > Strange - it works for me without any problems. Are you doing a full reactor build? Carsten > best regards > mike > > output from maven: > > __ ___ > \__ \_ ___ ___ \_ _/__ _ > | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ > || / __ \_>< |\>< / __ \| Y Y \ > ||( /__/\_ \ /___ /__/\_ \( /__|_| / > \/ \/ \/ \/ \/ \/ > > Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org > > > 25.08.2010 14:14:09.083 *INFO* [main] > org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test > testRemoveResourc > eAndRestart > [felix](org.apache.sling.osgi.installer.it.RemovedResourceDetectionTest) > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Starting up > the t > est container (Pax Runner 1.4.0 ) > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Acquire lock > for > new Pax Runner instance on > C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock > 25.08.2010 14:14:09.177 *INFO* [main] org.ops4j.pax.runner.ConfigurationImpl > Using config [classpath:META-INF/runner.pro > perties] > 25.08.2010 14:14:09.192 *INFO* [main] org.ops4j.pax.runner.Run Using only > arguments from command line > 25.08.2010 14:14:09.255 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.scr] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.configadmin] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.sling/org.apache.sling.commons.log] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-snaps...@update] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.junit/com.springsource.org.junit/4@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-compos > ite:mvn:org.ops4j.pax.runner.profiles/log//composite] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, > at start level 1, bundle will be started, bundle will be loaded from the > cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e > xtender/1.2.1, at start level 1, bundle will be started, bundle will be > loaded from the cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e > xtender-impl/1.2.1, at start level 1, bundle will be started, bundle will be > loaded from the cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.apache.felix/org.apache.felix.s > cr, at default start level, bundle will be started, bundle will be loaded > from the cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.apache.fe
[jira] Created: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
form auth should be able to set the auth cookie on a specific domain Key: SLING-1695 URL: https://issues.apache.org/jira/browse/SLING-1695 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: osgi.installer integration tests are hanging
I did the whole sling build with mvn clean install in the sling directory. best regards mike > -Original Message- > From: Carsten Ziegeler [mailto:cziege...@apache.org] > Sent: Wednesday, August 25, 2010 3:04 PM > To: dev@sling.apache.org > Subject: Re: osgi.installer integration tests are hanging > > > Mike Müller wrote > > Hi > > > > With the newest trunk the osgi.installer integration tests > are hanging, > > without displaying an error. > > > Strange - it works for me without any problems. > > Are you doing a full reactor build? > > Carsten > > > best regards > > mike > > > > output from maven: > > > > __ ___ > > \__ \_ ___ ___ \_ _/__ _ > > | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ > > || / __ \_>< |\>< / __ \| Y Y \ > > ||( /__/\_ \ /___ /__/\_ \( /__|_| / > > \/ \/ \/ \/ \/ \/ > > > > Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org > > > > > > 25.08.2010 14:14:09.083 *INFO* [main] > org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting > test testRemoveResourc > > eAndRestart > [felix](org.apache.sling.osgi.installer.it.RemovedResourceDete > ctionTest) > > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContain > er Starting up the t > > est container (Pax Runner 1.4.0 ) > > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContain > er Acquire lock for > > new Pax Runner instance on > C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock > > 25.08.2010 14:14:09.177 *INFO* [main] > org.ops4j.pax.runner.ConfigurationImpl Using config > [classpath:META-INF/runner.pro > > perties] > > 25.08.2010 14:14:09.192 *INFO* [main] > org.ops4j.pax.runner.Run Using only arguments from command line > > 25.08.2010 14:14:09.255 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.exam/pax-exam/1@1] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.apache.felix/org.apache.felix.scr] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.apache.felix/org.apache.felix.configadmin] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.apache.sling/org.apache.sling.commons.log] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > > :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-SN > aps...@update] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.junit/com.springsource.org.junit/4@1] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] > > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-compos > > ite:mvn:org.ops4j.pax.runner.profiles/log//composite] > > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] > > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] > > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > > :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] > > 25.08.2010 14:14:09.302 *INFO* [main] > org.ops4j.pax.runner.Run Provision bundle > [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, > > at start level 1, bundle will be started, bundle will be > loaded from the cache] > > 25.08.2010 14:14:09.302 *INFO* [main] > org.ops4j.pax.runner.Run Provision bundle > [mvn:org.ops4j.pax.exam/pax-exam-junit-e > > xtender/1.2.1, at start level 1, bundle will be started, > bundle will be loaded from the cache] > > 25.08.2010 14:14:09.302 *INFO* [main] > org.ops4j.pax.runner.Run Provision bundle > [mvn:org.ops4j.pax.exam/pax-exam-junit-e > > xtender-
Re: osgi.installer integration tests are hanging
On 8/25/10 9:04 AM, Carsten Ziegeler wrote: > Mike Müller wrote >> Hi >> >> With the newest trunk the osgi.installer integration tests are hanging, >> without displaying an error. >> > Strange - it works for me without any problems. ditto > > Are you doing a full reactor build? > > Carsten > >> best regards >> mike >> >> output from maven: >> >> __ ___ >> \__ \_ ___ ___ \_ _/__ _ >> | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ >> || / __ \_>< |\>< / __ \| Y Y \ >> ||( /__/\_ \ /___ /__/\_ \( /__|_| / >> \/ \/ \/ \/ \/ \/ >> >> Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org >> >> >> 25.08.2010 14:14:09.083 *INFO* [main] >> org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test >> testRemoveResourc >> eAndRestart >> [felix](org.apache.sling.osgi.installer.it.RemovedResourceDetectionTest) >> 25.08.2010 14:14:09.161 *INFO* [main] >> org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Starting up >> the t >> est container (Pax Runner 1.4.0 ) >> 25.08.2010 14:14:09.161 *INFO* [main] >> org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Acquire >> lock for >> new Pax Runner instance on >> C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock >> 25.08.2010 14:14:09.177 *INFO* [main] org.ops4j.pax.runner.ConfigurationImpl >> Using config [classpath:META-INF/runner.pro >> perties] >> 25.08.2010 14:14:09.192 *INFO* [main] org.ops4j.pax.runner.Run Using only >> arguments from command line >> 25.08.2010 14:14:09.255 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.scr] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.configadmin] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.sling/org.apache.sling.commons.log] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-snaps...@update] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.junit/com.springsource.org.junit/4@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-compos >> ite:mvn:org.ops4j.pax.runner.profiles/log//composite] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, >> at start level 1, bundle will be started, bundle will be loaded from the >> cache] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e >> xtender/1.2.1, at start level 1, bundle will be started, bundle will be >> loaded from the cache] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e >> xtender-impl/1.2.1, at start level 1, bundle will be started, bundle will be >> loaded from the cache] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.apache.felix/org.apache.felix.s >> cr, at default start level, bun
Re: [VOTE] Release Commons ClassLoader 1.2.0 and JCR ClassLoader 3.1.2
+1, Artifacts all check out ok. Ian On 25 Aug 2010, at 13:33, Carsten Ziegeler wrote: > Hi, > > We solved some issues in the classloaders: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314758 > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314757 > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-143/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 143 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This vote will be open for 72 hours. > > -- > Carsten Ziegeler > cziege...@apache.org
RE: osgi.installer integration tests are hanging
Maybe it's a problem only on windows xp, but the felix framework seems to hung... > -Original Message- > From: Justin Edelson [mailto:justinedel...@gmail.com] > Sent: Wednesday, August 25, 2010 3:27 PM > To: dev@sling.apache.org > Subject: Re: osgi.installer integration tests are hanging > > > On 8/25/10 9:04 AM, Carsten Ziegeler wrote: > > Mike Müller wrote > >> Hi > >> > >> With the newest trunk the osgi.installer integration tests > are hanging, > >> without displaying an error. > >> > > Strange - it works for me without any problems. > > ditto > > > > Are you doing a full reactor build? > > > > Carsten > > > >> best regards > >> mike > >> > >> output from maven: > >> > >> __ ___ > >> \__ \_ ___ ___ \_ _/__ _ > >> | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ > >> || / __ \_>< |\>< / __ \| Y Y \ > >> ||( /__/\_ \ /___ /__/\_ \( /__|_| / > >> \/ \/ \/ \/ \/ \/ > >> > >> Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org > >> > >> > >> 25.08.2010 14:14:09.083 *INFO* [main] > org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting > test testRemoveResourc > >> eAndRestart > [felix](org.apache.sling.osgi.installer.it.RemovedResourceDete > ctionTest) > >> 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContain > er Starting up the t > >> est container (Pax Runner 1.4.0 ) > >> 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContain > er Acquire lock for > >> new Pax Runner instance on > C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock > >> 25.08.2010 14:14:09.177 *INFO* [main] > org.ops4j.pax.runner.ConfigurationImpl Using config > [classpath:META-INF/runner.pro > >> perties] > >> 25.08.2010 14:14:09.192 *INFO* [main] > org.ops4j.pax.runner.Run Using only arguments from command line > >> 25.08.2010 14:14:09.255 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.exam/pax-exam/1@1] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.apache.felix/org.apache.felix.scr] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.apache.felix/org.apache.felix.configadmin] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.apache.sling/org.apache.sling.commons.log] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> > :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-SN > aps...@update] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.junit/com.springsource.org.junit/4@1] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] > >> 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-compos > >> ite:mvn:org.ops4j.pax.runner.profiles/log//composite] > >> 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] > >> 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] > >> 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan > bundles from [scan-bundle > >> :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] > >> 25.08.2010 14:14:09.302 *INFO* [main] > org.ops4j.pax.runner.Run Provision bundle > [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, > >> at start level 1, bundle will be started, bundle will be > loaded from the cache] > >> 25.08.2010 14:14:09.302 *INFO* [main] > org.ops4j.pax.runner.Run Provision bundle > [mvn:org.ops4j.pax.exam/pax-exam-junit-e > >> xtender/1.2.1, at start level 1, bundle will be started, > bundle will be loaded from the cache] > >> 25.08.2010 14:14:0
Re: osgi.installer integration tests are hanging
Hi Mike, Can you take a thread dump and see whether there is a deadlock ? I see you are using Windows. I know Carsten is on Mac OSX, I don't know about Justin. So wild-guessing that this might be windows related ??? Regards Felix On 25.08.2010 14:29, Mike Müller wrote: > Hi > > With the newest trunk the osgi.installer integration tests are hanging, > without displaying an error. > > best regards > mike > > output from maven: > > __ ___ > \__ \_ ___ ___ \_ _/__ _ > | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ > || / __ \_>< |\>< / __ \| Y Y \ > ||( /__/\_ \ /___ /__/\_ \( /__|_| / > \/ \/ \/ \/ \/ \/ > > Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org > > > 25.08.2010 14:14:09.083 *INFO* [main] > org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test > testRemoveResourc > eAndRestart > [felix](org.apache.sling.osgi.installer.it.RemovedResourceDetectionTest) > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Starting up > the t > est container (Pax Runner 1.4.0 ) > 25.08.2010 14:14:09.161 *INFO* [main] > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Acquire lock > for > new Pax Runner instance on > C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock > 25.08.2010 14:14:09.177 *INFO* [main] org.ops4j.pax.runner.ConfigurationImpl > Using config [classpath:META-INF/runner.pro > perties] > 25.08.2010 14:14:09.192 *INFO* [main] org.ops4j.pax.runner.Run Using only > arguments from command line > 25.08.2010 14:14:09.255 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.scr] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.configadmin] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.sling/org.apache.sling.commons.log] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-snaps...@update] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.junit/com.springsource.org.junit/4@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] > 25.08.2010 14:14:09.271 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-compos > ite:mvn:org.ops4j.pax.runner.profiles/log//composite] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] > 25.08.2010 14:14:09.286 *INFO* [main] > org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from > [scan-bundle > :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, > at start level 1, bundle will be started, bundle will be loaded from the > cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e > xtender/1.2.1, at start level 1, bundle will be started, bundle will be > loaded from the cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e > xtender-impl/1.2.1, at start level 1, bundle will be started, bundle will be > loaded from the cache] > 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision > bundle [mvn:org.apache.felix/org.apache.felix.s > cr, at default start level, bundle w
Re: osgi.installer integration tests are hanging
On 8/25/10 9:56 AM, Felix Meschberger wrote: > Hi Mike, > > Can you take a thread dump and see whether there is a deadlock ? > > I see you are using Windows. I know Carsten is on Mac OSX, I don't know > about Justin. I'm on OSX too. > So wild-guessing that this might be windows related ??? One thing that would be worth checking is what version of Felix Pax Exam is using. Justin > > Regards > Felix > > On 25.08.2010 14:29, Mike Müller wrote: >> Hi >> >> With the newest trunk the osgi.installer integration tests are hanging, >> without displaying an error. >> >> best regards >> mike >> >> output from maven: >> >> __ ___ >> \__ \_ ___ ___ \_ _/__ _ >> | ___/\__ \ \ \/ / |__)_\ \/ /\__ \ / \ >> || / __ \_>< |\>< / __ \| Y Y \ >> ||( /__/\_ \ /___ /__/\_ \( /__|_| / >> \/ \/ \/ \/ \/ \/ >> >> Pax Exam 1.2.1 from OPS4J - http://www.ops4j.org >> >> >> 25.08.2010 14:14:09.083 *INFO* [main] >> org.ops4j.pax.exam.junit.internal.JUnit4TestMethod Starting test >> testRemoveResourc >> eAndRestart >> [felix](org.apache.sling.osgi.installer.it.RemovedResourceDetectionTest) >> 25.08.2010 14:14:09.161 *INFO* [main] >> org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Starting up >> the t >> est container (Pax Runner 1.4.0 ) >> 25.08.2010 14:14:09.161 *INFO* [main] >> org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer Acquire >> lock for >> new Pax Runner instance on >> C:\DOKUME~1\mike\LOKALE~1\Temp\paxexam_runner_mike\paxexam.lock >> 25.08.2010 14:14:09.177 *INFO* [main] org.ops4j.pax.runner.ConfigurationImpl >> Using config [classpath:META-INF/runner.pro >> perties] >> 25.08.2010 14:14:09.192 *INFO* [main] org.ops4j.pax.runner.Run Using only >> arguments from command line >> 25.08.2010 14:14:09.255 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-junit-extender-impl/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.scr] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.configadmin] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.sling/org.apache.sling.commons.log] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.sling/org.apache.sling.osgi.installer/3.0.0-snaps...@update] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.junit/com.springsource.org.junit/4@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.exam/pax-exam-container-rbc/1@1] >> 25.08.2010 14:14:09.271 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-compos >> ite:mvn:org.ops4j.pax.runner.profiles/log//composite] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.logging/pax-logging-api/1.5.1] >> 25.08.2010 14:14:09.286 *INFO* [main] >> org.ops4j.pax.scanner.internal.ProvisionServiceImpl Scan bundles from >> [scan-bundle >> :mvn:org.ops4j.pax.logging/pax-logging-service/1.5.1] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam/1.2.1, >> at start level 1, bundle will be started, bundle will be loaded from the >> cache] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam-junit-e >> xtender/1.2.1, at start level 1, bundle will be started, bundle will be >> loaded from the cache] >> 25.08.2010 14:14:09.302 *INFO* [main] org.ops4j.pax.runner.Run Provision >> bundle [mvn:org.ops4j.pax.exam/pax-exam-juni
Re: [jira] Created: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
Hi, Just for documentation and completeness sake: Can you please elaborate a bit on the use case etc. Thanks alot. (By no means questioning the request at all ;-) ). Regards Felix On 25.08.2010 15:11, Justin Edelson (JIRA) wrote: > form auth should be able to set the auth cookie on a specific domain > > > Key: SLING-1695 > URL: https://issues.apache.org/jira/browse/SLING-1695 > Project: Sling > Issue Type: Improvement > Components: Authentication > Reporter: Justin Edelson > > > >
[jira] Updated: (SLING-1696) Update Velocity scripting to Velocity 1.6.4
[ https://issues.apache.org/jira/browse/SLING-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller updated SLING-1696: --- Priority: Trivial (was: Major) > Update Velocity scripting to Velocity 1.6.4 > --- > > Key: SLING-1696 > URL: https://issues.apache.org/jira/browse/SLING-1696 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Mike Müller >Assignee: Mike Müller >Priority: Trivial > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1696) Update Velocity scripting to Velocity 1.6.4
Update Velocity scripting to Velocity 1.6.4 --- Key: SLING-1696 URL: https://issues.apache.org/jira/browse/SLING-1696 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Mike Müller Assignee: Mike Müller -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1696) Update Velocity scripting to Velocity 1.6.4
[ https://issues.apache.org/jira/browse/SLING-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller resolved SLING-1696. Resolution: Fixed commited in r989114 > Update Velocity scripting to Velocity 1.6.4 > --- > > Key: SLING-1696 > URL: https://issues.apache.org/jira/browse/SLING-1696 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Mike Müller >Assignee: Mike Müller >Priority: Trivial > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Commons ClassLoader 1.2.0 and JCR ClassLoader 3.1.2
+1 Carsten Carsten Ziegeler wrote > Hi, > > We solved some issues in the classloaders: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314758 > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310710&fixfor=12314757 > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-143/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 143 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This vote will be open for 72 hours. > -- Carsten Ziegeler cziege...@apache.org
Re: [jira] Created: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
I suspect my use case is very specific and is intertwined with a few other things, but basically... I make heavy use of workspaces in my CMS for content branches. Subdomains of a parent domain are used to identify which workspace should be used. Setting the auth cookie on the parent domain allows for users to view content in different branches (workspaces) without re-authenticating. Another use case (just thinking out loud here), would be to use Sling as an SSO provider, again by setting the cookie on a parent domain and then having a ServletFilter on each client application which check the cookie against the Sling instance. It's no SAML, but would work. Justin On 8/25/10 9:55 AM, Felix Meschberger wrote: > Hi, > > Just for documentation and completeness sake: Can you please elaborate a > bit on the use case etc. Thanks alot. > > (By no means questioning the request at all ;-) ). > > Regards > Felix > > On 25.08.2010 15:11, Justin Edelson (JIRA) wrote: >> form auth should be able to set the auth cookie on a specific domain >> >> >> Key: SLING-1695 >> URL: https://issues.apache.org/jira/browse/SLING-1695 >> Project: Sling >> Issue Type: Improvement >> Components: Authentication >> Reporter: Justin Edelson >> >> >> >>
[jira] Created: (SLING-1697) Log the start of each test class run
Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Fix For: Launchpad Testing 6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1698) Set an explicit version for exported packages
Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Jackrabbit Access Manager 2.0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1698: -- Fix Version/s: JCR Jackrabbit User Manager 2.0.6 > Set an explicit version for exported packages > - > > Key: SLING-1698 > URL: https://issues.apache.org/jira/browse/SLING-1698 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Justin Edelson > Fix For: JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access > Manager 2.0.6 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
[ https://issues.apache.org/jira/browse/SLING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1664. --- Resolution: Fixed > support reading the jackrabbit configuration file from the launchpad archive > > > Key: SLING-1664 > URL: https://issues.apache.org/jira/browse/SLING-1664 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Justin Edelson >Assignee: Justin Edelson > Fix For: JCR Jackrabbit Server 2.0.8 > > > downstream users of Sling should be able to put a repository.xml in either > the launchpad JAR or WAR and get it to work without any additional > configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1698: -- Fix Version/s: Scripting JSP-Taglib 2.1.0 > Set an explicit version for exported packages > - > > Key: SLING-1698 > URL: https://issues.apache.org/jira/browse/SLING-1698 > Project: Sling > Issue Type: Improvement > Components: JCR >Reporter: Justin Edelson > Fix For: Scripting JSP-Taglib 2.1.0, JCR Jackrabbit User Manager > 2.0.6, JCR Jackrabbit Access Manager 2.0.6 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1421) Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping
[ https://issues.apache.org/jira/browse/SLING-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1421: -- Fix Version/s: (was: JCR Resource 2.0.8) > Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping > -- > > Key: SLING-1421 > URL: https://issues.apache.org/jira/browse/SLING-1421 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Resource 2.0.6 >Reporter: Stefan Seifert > Attachments: 100303_slingtest-mapping.zip > > > in our sling CMS-based web projects we've the following scenario: > * most pages of a website are accessed via HTTP, but some of the via HTTPs > (e.g. including forms submitting personal data) > * at the same time we use the mapping features at /etc/map to shorten the > urls for a given domain name > * in fact we have to configure two mappings for two domain names (one for > HTTP and one for HTTPS), pointing to the same start path in JCR > with this configuration in place the sling ResourceResolver.map method > sometimes produces unexpected or incorrect results with the current > implementation. > if the current host name and port does not match with the configured mapping > host name and port sling automatically adds protocol, host name and port from > the configuration to the result of the map method. but in the case above with > multiple mappings for the same start path this cannot produce correct > results, because the decision whether the secure or non-secure domain name > should be chosen is custom application logic. > i'm not sure what the best solution is for this problem, because the current > implementation makes sense in some way and works well for the simple > scenarios. but in complex scenarios with multiple domain mappings it would be > more practical to use the map method only for shortening the urls and not for > adding the hostname. > of course it is possible to parse the value of the map method and strip off > any hostname returned manually and add an own one, but this seems not > "right". and if the cms does a check if the internal url is valid this url > can be treated as invalid. > for easy reproduction of the scenario i've attached a simple test project > [^100303_slingtest-mapping.zip]. please deploy it to a sling instance using > "mvn install" and then call in the intro page > http://localhost:8080/content/slingtest-mapping.html and follow the > instructions on the page (two host names have to be added to the local hosts > file). the test project contains two templates/jsp components, a > configuration at /etc/map with two domain names pointing to the same path and > some sample content nodes. > depending whether a default mapping "/content/-/" is configured in "apache > sling resource resolver" the generated links on the "site 1" test page are > correct. but the links generate on the "site 2" test pages are wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1421) Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping
[ https://issues.apache.org/jira/browse/SLING-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902642#action_12902642 ] Justin Edelson commented on SLING-1421: --- moving out of 2.0.8 > Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping > -- > > Key: SLING-1421 > URL: https://issues.apache.org/jira/browse/SLING-1421 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Resource 2.0.6 >Reporter: Stefan Seifert > Attachments: 100303_slingtest-mapping.zip > > > in our sling CMS-based web projects we've the following scenario: > * most pages of a website are accessed via HTTP, but some of the via HTTPs > (e.g. including forms submitting personal data) > * at the same time we use the mapping features at /etc/map to shorten the > urls for a given domain name > * in fact we have to configure two mappings for two domain names (one for > HTTP and one for HTTPS), pointing to the same start path in JCR > with this configuration in place the sling ResourceResolver.map method > sometimes produces unexpected or incorrect results with the current > implementation. > if the current host name and port does not match with the configured mapping > host name and port sling automatically adds protocol, host name and port from > the configuration to the result of the map method. but in the case above with > multiple mappings for the same start path this cannot produce correct > results, because the decision whether the secure or non-secure domain name > should be chosen is custom application logic. > i'm not sure what the best solution is for this problem, because the current > implementation makes sense in some way and works well for the simple > scenarios. but in complex scenarios with multiple domain mappings it would be > more practical to use the map method only for shortening the urls and not for > adding the hostname. > of course it is possible to parse the value of the map method and strip off > any hostname returned manually and add an own one, but this seems not > "right". and if the cms does a check if the internal url is valid this url > can be treated as invalid. > for easy reproduction of the scenario i've attached a simple test project > [^100303_slingtest-mapping.zip]. please deploy it to a sling instance using > "mvn install" and then call in the intro page > http://localhost:8080/content/slingtest-mapping.html and follow the > instructions on the page (two host names have to be added to the local hosts > file). the test project contains two templates/jsp components, a > configuration at /etc/map with two domain names pointing to the same path and > some sample content nodes. > depending whether a default mapping "/content/-/" is configured in "apache > sling resource resolver" the generated links on the "site 1" test page are > correct. but the links generate on the "site 2" test pages are wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
sling 6 releases visualization
I put this together to help visualize the releases leading up to Sling 6: https://cwiki.apache.org/confluence/download/attachments/2743/sling6-bundles-viz.pdf Red Boxes - modules with outstanding issues Green Boxes - modules with no outstanding issues Blue Boxes - modules up for vote White Boxes - released modules Black line - dependency on released module Brown line - dependency on unreleased module So... a Green Box with only brown lines is good to go. One thing that jumped out is that Servlets Post will need to be released before the JCR modules (at least some of them). Justin
Velocity Scripting Release 2.0.0 (was Velocity scripting support)
> On Wed, Aug 25, 2010 at 4:23 PM, wrote: > > ...I will also test the scripting support against the > latest velocity release > > tomorrow, thereby also testing whether it integrates with > the latest Day > > CQ5 distribution (I expect that should be interesting). The > question of > > course is what kind of tests must be performed before one > would consider a > > release... > > I'm no velocity expert...I'd suggest checking that all the velocity > features that you need work as expected, and if possible run some > stress tests and watch for memory leaks. > > > ...Perhaps it would be best to create release candidates beforehand > > and use those within an actual project?... > > We'll rather create a release, and another one if problems are > discovered. Release early, release often! > > Please let us know the results of your tests, and if things look good > I can prepare a release in the next few days. > > -Bertrand Hi Betrand I moved the disussion about the release to the dev list, which is probably better. Betrand, if you don't mind I would like to cut the release next week (just to get used to do so...). The bundle contains very little code, so from my side I don't see any problems to release it. best regards mike
Re: Velocity Scripting Release 2.0.0 (was Velocity scripting support)
Hi Mike, On Thu, Aug 26, 2010 at 8:01 AM, Mike Müller wrote: > ...Betrand, if you don't mind I would like to cut the > release next week (just to get used to do so...). > The bundle contains very little code, so from my side I don't see > any problems to release it... Fine with me! -Bertrand
