[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867551#comment-15867551 ] Dominik Süß commented on SLING-5457: Patch proposal submitted via PR (see comment by ASF Github Bot).

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867568#comment-15867568 ] Oliver Lietz commented on SLING-6502: - Works in Jetty 9, Tomcat 8.5 and WildFly 10.1 (have to check

[jira] [Created] (SLING-6521) Testing Resource Resolver Mock depends on old osgi compendium artifactId

Vincent VL created SLING-6521: - Summary: Testing Resource Resolver Mock depends on old osgi compendium artifactId Key: SLING-6521 URL: https://issues.apache.org/jira/browse/SLING-6521 Project: Sling

[jira] [Comment Edited] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867432#comment-15867432 ] Carsten Ziegeler edited comment on SLING-6502 at 2/15/17 8:15 AM: -- I'm

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867432#comment-15867432 ] Carsten Ziegeler commented on SLING-6502: - I'm not quiet sure what we're trying to fix here. I

[jira] [Updated] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6502: Attachment: apis.patch We had issues with embedded API ({{javax.inject}}) in the past and I don't

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867491#comment-15867491 ] Carsten Ziegeler commented on SLING-6502: - Does this work in each and every web container? In the

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867544#comment-15867544 ] ASF GitHub Bot commented on SLING-5457: --- GitHub user DominikSuess opened a pull request:

[GitHub] sling pull request #199: SLING-5457 - OsgiInstaller should retry to start bu...

GitHub user DominikSuess opened a pull request: https://github.com/apache/sling/pull/199 SLING-5457 - OsgiInstaller should retry to start bundles on failures - adding 5 retry cycles in BundleUpdateTask for Exceptions You can merge this pull request into a Git repository by running:

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867820#comment-15867820 ] Karl Pauls commented on SLING-5457: --- Ok, I'm going to apply this patch and cut a release for the related

[jira] [Comment Edited] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867848#comment-15867848 ] Konrad Windszus edited comment on SLING-5457 at 2/15/17 1:39 PM: - Ok, I

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867848#comment-15867848 ] Konrad Windszus commented on SLING-5457: Ok, I agree with the approach in general. I just have

OSGi Installer Core Release

Hi, since obviously the next release of the OSGi Installer is imminent (https://issues.apache.org/jira/browse/SLING-5457?focusedCommentId=15867820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15867820) could someone please look at the proposed patch in

[jira] [Created] (SLING-6522) Refactor/Improve error handling of InstallTaskFactorys

Konrad Windszus created SLING-6522: -- Summary: Refactor/Improve error handling of InstallTaskFactorys Key: SLING-6522 URL: https://issues.apache.org/jira/browse/SLING-6522 Project: Sling

[jira] [Updated] (SLING-6522) Refactor/Improve error handling of InstallTaskFactorys

[ https://issues.apache.org/jira/browse/SLING-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6522: --- Description: Currently the retry behaviour and exception handling needs to be done in each

[jira] [Updated] (SLING-6522) Refactor/Improve error handling of InstallTaskFactorys

[ https://issues.apache.org/jira/browse/SLING-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6522: --- Description: Currently the retry behaviour and exception handling needs to be done in each

Build Issues

Today I wanted to build Sling from trunk. I ran into two issues 1) Preparing test on Apache Sling Dynamic Class Loader Support 1.3.9-SNAPSHOT is blocked for ever on: [main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System (Version: 4.9.1) created. [main] INFO

[jira] [Commented] (SLING-6521) Testing Resource Resolver Mock depends on old osgi compendium artifactId

[ https://issues.apache.org/jira/browse/SLING-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868223#comment-15868223 ] Stefan Seifert commented on SLING-6521: --- well, it is not incompatible with latest sling-mock version

[jira] [Updated] (SLING-6521) Testing Resource Resolver Mock depends on old osgi compendium artifactId

[ https://issues.apache.org/jira/browse/SLING-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6521: -- Priority: Minor (was: Major) > Testing Resource Resolver Mock depends on old osgi compendium

[jira] [Commented] (SLING-6522) Refactor/Improve error handling of InstallTaskFactorys

[ https://issues.apache.org/jira/browse/SLING-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868030#comment-15868030 ] Konrad Windszus commented on SLING-6522: I propose to deal with the error cases from above with

[jira] [Updated] (SLING-6522) Refactor/Improve error handling of InstallTasks

[ https://issues.apache.org/jira/browse/SLING-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6522: --- Summary: Refactor/Improve error handling of InstallTasks (was: Refactor/Improve error

[jira] [Updated] (SLING-6522) Refactor/Improve error handling of InstallTasks

[ https://issues.apache.org/jira/browse/SLING-6522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6522: --- Description: Currently the retry behaviour and exception handling needs to be done in each

RE: Build Issues

>2) Rat Check fails for Apache Sling Testing Mocks Modules Reactor 1- >SNAPSHOT ... >[INFO] 2 resources included (use -debug for more details) >[DEBUG] - included pom.xml >[DEBUG] - included sling-mock-jackrabbit/org.apache.sling.testing.sling- >mock-jackrabbit.iml i think this happens only

Re: Build Issues

Hi Stefan Thanks. I am using the git repo and forgot that it can leave spurious directories around (git clean -df fix it then). That said the block in the regular (non -DskipTests) build remains. [INFO] [INFO] Building

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868381#comment-15868381 ] Carsten Ziegeler commented on SLING-6502: - The problem is if we use the API provided from outside

[jira] [Resolved] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-5457. --- Resolution: Fixed Assignee: Karl Pauls Ok, I got it working after all. It turned out that the

Re: OSGi Installer Core Release

Hi Konrad, SLING-6392 looks good. If you commit it (and assuming you agree with SLING-5457 for now) I would go ahead and cut a release. regards, Karl On Wed, Feb 15, 2017 at 3:25 PM, Karl Pauls wrote: > I'll have a look. > > regards, > > Karl > > On Wed, Feb 15, 2017 at

[jira] [Commented] (SLING-6392) OSGi Installer: Symbolic name changes on a resource keeping the same URL are not supported

[ https://issues.apache.org/jira/browse/SLING-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868806#comment-15868806 ] Karl Pauls commented on SLING-6392: --- [~kwin] this looks good to me and I got a message from [~cziegeler]

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868824#comment-15868824 ] Oliver Lietz commented on SLING-6502: - * set version of

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867888#comment-15867888 ] Karl Pauls commented on SLING-5457: --- [~kwin] I don't think that is the case. It will CYCLE until it is

Re: OSGi Installer Core Release

I'll have a look. regards, Karl On Wed, Feb 15, 2017 at 2:45 PM, Konrad Windszus wrote: > Hi, > since obviously the next release of the OSGi Installer is imminent >

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867897#comment-15867897 ] Karl Pauls commented on SLING-5457: --- [~kwin] see [~dsuess] comment on the GitHub PR for more details but

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867967#comment-15867967 ] Konrad Windszus commented on SLING-5457: I created a follow-up ticket for the more global

[jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures

[ https://issues.apache.org/jira/browse/SLING-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867971#comment-15867971 ] Karl Pauls commented on SLING-5457: --- Thanks. As I said on the GitHub PR - I agree with you that this