[jira] Created: (SLING-2018) Using RepositoryAccessor inside a bundle

Using RepositoryAccessor inside a bundle Key: SLING-2018 URL: https://issues.apache.org/jira/browse/SLING-2018 Project: Sling Issue Type: Bug Components: JCR Affects Versions: 3

[jira] Created: (SLING-2019) explorer doesn't work when sling is used in a non-root context

explorer doesn't work when sling is used in a non-root context -- Key: SLING-2019 URL: https://issues.apache.org/jira/browse/SLING-2019 Project: Sling Issue Type: Bug

AW: pendant to load-on-startup

thx -Ursprüngliche Nachricht- Von: Felix Meschberger [mailto:fmesc...@adobe.com] Gesendet: Montag, 7. März 2011 07:51 An: dev@sling.apache.org Betreff: Re: pendant to load-on-startup Hi Clemens, Am Montag, den 07.03.2011, 06:22 + schrieb Clemens Wyss: In my

[jira] Resolved: (SLING-2020) Update to latest Apache Felix Event Admin 1.2.10

[ https://issues.apache.org/jira/browse/SLING-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2020. -- Resolution: Fixed Fixed in Rev. 1078758 Update to latest Apache Felix Event Admin

[jira] Created: (SLING-2020) Update to latest Apache Felix Event Admin 1.2.10

Update to latest Apache Felix Event Admin 1.2.10 Key: SLING-2020 URL: https://issues.apache.org/jira/browse/SLING-2020 Project: Sling Issue Type: Improvement Components: Launchpad

Build failed in Jenkins: sling-trunk-1.6 #822

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/822/changes Changes: [fmeschbe] SLING-2020 Upgrade to Apache Felix Event Admin 1.2.10 -- [...truncated 10829 lines...] 07.03.2011 05:19:46.691 *INFO* [FelixStartLevel]

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Application Builder #822

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad/822/ -- [INFO] [INFO] Building Apache Sling Launchpad Application Builder [INFO]

[jira] Created: (SLING-2021) JarExecutor should not be a singleton

JarExecutor should not be a singleton - Key: SLING-2021 URL: https://issues.apache.org/jira/browse/SLING-2021 Project: Sling Issue Type: Improvement Components: Testing Reporter:

Build failed in Jenkins: sling-trunk-1.5 » Apache Sling Launchpad Application Builder #1138

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad/1138/ -- [INFO] [INFO] Building Apache Sling Launchpad Application Builder [INFO]

Build failed in Jenkins: sling-trunk-1.5 #1138

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/1138/changes Changes: [fmeschbe] SLING-2020 Upgrade to Apache Felix Event Admin 1.2.10 -- [...truncated 11867 lines...] [INFO] [remote-resources:process {execution: default}] [INFO]

[jira] Resolved: (SLING-2021) JarExecutor should not be a singleton

[ https://issues.apache.org/jira/browse/SLING-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2021. Resolution: Fixed Changed to a regular constructor in revision 1078776

[jira] Created: (SLING-2022) JarExecutor: optionally run in a specific folder

JarExecutor: optionally run in a specific folder Key: SLING-2022 URL: https://issues.apache.org/jira/browse/SLING-2022 Project: Sling Issue Type: Improvement Components: Testing

[jira] Updated: (SLING-2022) More JarExecutor options: work folder and options for the executable jar

[ https://issues.apache.org/jira/browse/SLING-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2022: --- Description: Add a property to configure the path where the runnable jar is

Build failed in Jenkins: sling-trunk-1.5 #1139

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/1139/changes Changes: [bdelacretaz] SLING-2021 - JarExecutor does not need to be a singleton -- [...truncated 6622 lines...] [INFO] [deploy:deploy {execution: default-deploy}] [INFO] Retrieving

Build failed in Jenkins: sling-trunk-1.6 #823

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/823/ -- Started by an SCM change Building remotely on ubuntu1 FATAL: Unable to call fetch2. Invalid object ID 19506 java.lang.IllegalStateException: Unable to call fetch2. Invalid object ID 19506

Build Failures

Hi all, I already updated the Launchpad Builder list to include the Apache Felix Event Admin 1.2.10 bundle, which is not yet rsync-ed to the maven repository yet. Expect to see some build failures until this sync is done. Regards Felix

[jira] Resolved: (SLING-2022) More JarExecutor options: work folder and options for the executable jar

[ https://issues.apache.org/jira/browse/SLING-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2022. Resolution: Fixed Implemented in revision 1078781 More JarExecutor options: work

[jira] Created: (SLING-2023) Sample Integration tests should run in the integration-tests phase

Sample Integration tests should run in the integration-tests phase -- Key: SLING-2023 URL: https://issues.apache.org/jira/browse/SLING-2023 Project: Sling Issue Type:

Build failed in Jenkins: sling-trunk-1.5 #1140

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/1140/changes Changes: [bdelacretaz] SLING-2002 - new JarExecutor options: work dir and options for the jar under test -- Started by an SCM change Building remotely on ubuntu1 Updating

Build failed in Jenkins: sling-trunk-1.6 #824

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/824/ -- Started by an SCM change Building remotely on ubuntu1 Updating http://svn.apache.org/repos/asf/sling/trunk U

Build failed in Jenkins: sling-trunk-1.5 #1141

See https://hudson.apache.org/hudson/job/sling-trunk-1.5/1141/changes Changes: [bdelacretaz] SLING-2023 - run sample tests in the integration-test phase, and fix initialization bugs that the different order of tests execution exposed -- Started by an SCM

Build failed in Jenkins: sling-trunk-1.6 #825

See https://hudson.apache.org/hudson/job/sling-trunk-1.6/825/changes Changes: [bdelacretaz] SLING-2023 - run sample tests in the integration-test phase, and fix initialization bugs that the different order of tests execution exposed -- Started by an SCM

Re: Access Log as OSGi Events

On Fri, Mar 4, 2011 at 2:06 AM, Felix Meschberger fmesc...@adobe.comwrote: Hi, Am Donnerstag, den 03.03.2011, 17:07 + schrieb Carl Hall: There seem to be 3 things to accomplish here: * Change logging order to have slf4j write into the LogService then have a LogListener that will

[jira] Created: (SLING-2024) Replace file logger with logback

Replace file logger with logback Key: SLING-2024 URL: https://issues.apache.org/jira/browse/SLING-2024 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons Log