From issues at jboss.org Fri Apr 15 07:37:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Fri, 15 Apr 2016 07:37:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) WildFly 10.x support patch In-Reply-To: References: Message-ID: Sander Stoel created JBOSGI-788: ----------------------------------- Summary: WildFly 10.x support patch Key: JBOSGI-788 URL: https://issues.jboss.org/browse/JBOSGI-788 Project: JBoss OSGi Issue Type: Patch Reporter: Sander Stoel Assignee: Arcadiy Ivanov This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Apr 18 02:53:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 18 Apr 2016 02:53:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-789) Update dependencies to match WildFly 10 In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-789: ------------------------------------- Summary: Update dependencies to match WildFly 10 Key: JBOSGI-789 URL: https://issues.jboss.org/browse/JBOSGI-789 Project: JBoss OSGi Issue Type: Component Upgrade Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Apr 18 05:23:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 18 Apr 2016 05:23:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) WildFly 10.x support patch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-788 started by Arcadiy Ivanov. --------------------------------------------- > WildFly 10.x support patch > -------------------------- > > Key: JBOSGI-788 > URL: https://issues.jboss.org/browse/JBOSGI-788 > Project: JBoss OSGi > Issue Type: Patch > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Apr 18 05:24:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 18 Apr 2016 05:24:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-786) Add support for WildFly 10.0.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-786 started by Arcadiy Ivanov. --------------------------------------------- > Add support for WildFly 10.0.x > ------------------------------ > > Key: JBOSGI-786 > URL: https://issues.jboss.org/browse/JBOSGI-786 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 10:37:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 10:37:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) Support WildFly 10 model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-788: ---------------------------------- Summary: Support WildFly 10 model (was: WildFly 10.x support patch) > Support WildFly 10 model > ------------------------ > > Key: JBOSGI-788 > URL: https://issues.jboss.org/browse/JBOSGI-788 > Project: JBoss OSGi > Issue Type: Patch > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:11:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:11:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) Support WildFly 10 model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-788: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/16 (was: https://github.com/jbosgi/jbosgi/pull/15) > Support WildFly 10 model > ------------------------ > > Key: JBOSGI-788 > URL: https://issues.jboss.org/browse/JBOSGI-788 > Project: JBoss OSGi > Issue Type: Patch > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:20:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:20:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) Support WildFly 10 model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-788. ----------------------------------- Fix Version/s: JBossOSGI 2.5.0 Resolution: Done > Support WildFly 10 model > ------------------------ > > Key: JBOSGI-788 > URL: https://issues.jboss.org/browse/JBOSGI-788 > Project: JBoss OSGi > Issue Type: Patch > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > > This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:42:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:42:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-789) Update dependencies to match WildFly 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-789: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-parent/pull/11, https://github.com/jbosgi/jbosgi-vfs/pull/10, https://github.com/jbosgi/jbosgi-resolver/pull/13, https://github.com/jbosgi/jbosgi-logging/pull/7, https://github.com/jbosgi/jbosgi-metadata/pull/8, https://github.com/jbosgi/jbosgi-spi/pull/9, https://github.com/jbosgi/jbosgi-testing/pull/8, https://github.com/jbosgi/jbosgi-deployment/pull/8, https://github.com/jbosgi/jbosgi-framework/pull/28, https://github.com/jbosgi/jbosgi-repository/pull/18, https://github.com/jbosgi/jbosgi-provision/pull/8, https://github.com/jbosgi/jbosgi/pull/16 > Update dependencies to match WildFly 10 > --------------------------------------- > > Key: JBOSGI-789 > URL: https://issues.jboss.org/browse/JBOSGI-789 > Project: JBoss OSGi > Issue Type: Component Upgrade > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:42:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:42:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-789) Update dependencies to match WildFly 10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-789. ----------------------------------- Resolution: Done > Update dependencies to match WildFly 10 > --------------------------------------- > > Key: JBOSGI-789 > URL: https://issues.jboss.org/browse/JBOSGI-789 > Project: JBoss OSGi > Issue Type: Component Upgrade > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:48:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:48:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-769) Reenable tests once WFLY on VFS > 3.2.9.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-769: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-repository/pull/19 > Reenable tests once WFLY on VFS > 3.2.9.Final > --------------------------------------------- > > Key: JBOSGI-769 > URL: https://issues.jboss.org/browse/JBOSGI-769 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Trivial > > Due to JBVFS-200 tests in FileBasedRepositoryStorageTestCase are disabled. Once WildFly uptakes VFS >3.2.9.Final, re-enable the tests and verify correct operation -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:48:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:48:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-769) Reenable tests once WFLY on VFS > 3.2.9.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-769 started by Arcadiy Ivanov. --------------------------------------------- > Reenable tests once WFLY on VFS > 3.2.9.Final > --------------------------------------------- > > Key: JBOSGI-769 > URL: https://issues.jboss.org/browse/JBOSGI-769 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Trivial > > Due to JBVFS-200 tests in FileBasedRepositoryStorageTestCase are disabled. Once WildFly uptakes VFS >3.2.9.Final, re-enable the tests and verify correct operation -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:50:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:50:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-769) Reenable tests once WFLY on VFS > 3.2.9.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-769 stopped by Arcadiy Ivanov. --------------------------------------------- > Reenable tests once WFLY on VFS > 3.2.9.Final > --------------------------------------------- > > Key: JBOSGI-769 > URL: https://issues.jboss.org/browse/JBOSGI-769 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Trivial > > Due to JBVFS-200 tests in FileBasedRepositoryStorageTestCase are disabled. Once WildFly uptakes VFS >3.2.9.Final, re-enable the tests and verify correct operation -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 13:50:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 13:50:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-769) Reenable tests once WFLY on VFS > 3.2.9.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-769. ----------------------------------- Resolution: Done > Reenable tests once WFLY on VFS > 3.2.9.Final > --------------------------------------------- > > Key: JBOSGI-769 > URL: https://issues.jboss.org/browse/JBOSGI-769 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Trivial > > Due to JBVFS-200 tests in FileBasedRepositoryStorageTestCase are disabled. Once WildFly uptakes VFS >3.2.9.Final, re-enable the tests and verify correct operation -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 14:10:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 14:10:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-790) Javadoc lint must be disabled everywhere In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-790 started by Arcadiy Ivanov. --------------------------------------------- > Javadoc lint must be disabled everywhere > ---------------------------------------- > > Key: JBOSGI-790 > URL: https://issues.jboss.org/browse/JBOSGI-790 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 14:10:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 14:10:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-790) Javadoc lint must be disabled everywhere In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-790: ------------------------------------- Summary: Javadoc lint must be disabled everywhere Key: JBOSGI-790 URL: https://issues.jboss.org/browse/JBOSGI-790 Project: JBoss OSGi Issue Type: Task Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 14:32:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 14:32:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-790) Javadoc lint must be disabled everywhere In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-790: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-parent/pull/12 > Javadoc lint must be disabled everywhere > ---------------------------------------- > > Key: JBOSGI-790 > URL: https://issues.jboss.org/browse/JBOSGI-790 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 14:32:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 14:32:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-790) Javadoc lint must be disabled everywhere In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-790. ----------------------------------- Resolution: Done > Javadoc lint must be disabled everywhere > ---------------------------------------- > > Key: JBOSGI-790 > URL: https://issues.jboss.org/browse/JBOSGI-790 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 15:17:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 15:17:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-791) Synchronize standalone config with 10 and exclude new batch subsystem In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-791: ------------------------------------- Summary: Synchronize standalone config with 10 and exclude new batch subsystem Key: JBOSGI-791 URL: https://issues.jboss.org/browse/JBOSGI-791 Project: JBoss OSGi Issue Type: Enhancement Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 15:18:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 15:18:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-791) Synchronize standalone config with 10 and exclude new batch subsystem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-791 started by Arcadiy Ivanov. --------------------------------------------- > Synchronize standalone config with 10 and exclude new batch subsystem > --------------------------------------------------------------------- > > Key: JBOSGI-791 > URL: https://issues.jboss.org/browse/JBOSGI-791 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 15:20:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 15:20:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-791) Synchronize standalone config with 10 and exclude new batch subsystem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-791: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/17 > Synchronize standalone config with 10 and exclude new batch subsystem > --------------------------------------------------------------------- > > Key: JBOSGI-791 > URL: https://issues.jboss.org/browse/JBOSGI-791 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 15:20:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 15:20:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-791) Synchronize standalone config with 10 and exclude new batch subsystem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-791. ----------------------------------- Resolution: Done > Synchronize standalone config with 10 and exclude new batch subsystem > --------------------------------------------------------------------- > > Key: JBOSGI-791 > URL: https://issues.jboss.org/browse/JBOSGI-791 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 15:20:01 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 15:20:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-791) Synchronize standalone config with 10 and exclude new batch subsystem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-791: ---------------------------------- Fix Version/s: JBossOSGI 2.5.0 > Synchronize standalone config with 10 and exclude new batch subsystem > --------------------------------------------------------------------- > > Key: JBOSGI-791 > URL: https://issues.jboss.org/browse/JBOSGI-791 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 16:30:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 16:30:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-786) Add support for WildFly 10.0.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-786. ----------------------------------- Resolution: Done > Add support for WildFly 10.0.x > ------------------------------ > > Key: JBOSGI-786 > URL: https://issues.jboss.org/browse/JBOSGI-786 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 16:32:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 16:32:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-788) Support WildFly 10 model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-788: ---------------------------------- Issue Type: Enhancement (was: Patch) > Support WildFly 10 model > ------------------------ > > Key: JBOSGI-788 > URL: https://issues.jboss.org/browse/JBOSGI-788 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > > This pull request passes all tests, however not all dependency versions have been updated. Tested and verified that domain mode is working as expected at least in our setup (multple server groups). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 16:33:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 16:33:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-790) Javadoc lint must be disabled everywhere In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-790: ---------------------------------- Fix Version/s: JBossOSGI 2.5.0 > Javadoc lint must be disabled everywhere > ---------------------------------------- > > Key: JBOSGI-790 > URL: https://issues.jboss.org/browse/JBOSGI-790 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Apr 19 16:33:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 19 Apr 2016 16:33:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-769) Reenable tests once WFLY on VFS > 3.2.9.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-769: ---------------------------------- Fix Version/s: JBossOSGI 2.5.0 > Reenable tests once WFLY on VFS > 3.2.9.Final > --------------------------------------------- > > Key: JBOSGI-769 > URL: https://issues.jboss.org/browse/JBOSGI-769 > Project: JBoss OSGi > Issue Type: Task > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Trivial > Fix For: JBossOSGI 2.5.0 > > > Due to JBVFS-200 tests in FileBasedRepositoryStorageTestCase are disabled. Once WildFly uptakes VFS >3.2.9.Final, re-enable the tests and verify correct operation -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 06:53:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 06:53:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: Sander Stoel created JBOSGI-792: ----------------------------------- Summary: Initial bundles fail to resolve if runtime name differs Key: JBOSGI-792 URL: https://issues.jboss.org/browse/JBOSGI-792 Project: JBoss OSGi Issue Type: Bug Affects Versions: JBossOSGI 2.5.0, JBossOSGI 2.4.0, JBossOSGI 2.3.1 Reporter: Sander Stoel Assignee: Arcadiy Ivanov If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. {code} [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" [Server:server] ], [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server] "Services that were unable to start:" => [ [Server:server] "jbosgi.SystemBundle", [Server:server] "jbosgi.SystemContext", [Server:server] "jbosgi.framework.ACTIVE", [Server:server] "jbosgi.framework.INIT", [Server:server] "jbosgi.internal.framework.ACTIVE" [Server:server] ], {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 06:54:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 06:54:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195077#comment-13195077 ] Sander Stoel edited comment on JBOSGI-792 at 4/21/16 6:53 AM: -------------------------------------------------------------- I have found the cause and made a fix for this, will add a PR to this ticket once I've tested it properly and made sure it works in all circumstances. was (Author: sanderst): I have found and made a fix for this, will add a PR to this ticket once I've tested it properly and made sure it works in all circumstances. > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 06:54:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 06:54:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195077#comment-13195077 ] Sander Stoel commented on JBOSGI-792: ------------------------------------- I have found and made a fix for this, will add a PR to this ticket once I've tested it properly and made sure it works in all circumstances. > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 06:59:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 21 Apr 2016 06:59:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195080#comment-13195080 ] Arcadiy Ivanov commented on JBOSGI-792: --------------------------------------- Could you attach a server.log as well please? > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 06:59:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 06:59:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sander Stoel updated JBOSGI-792: -------------------------------- Description: If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. {code} [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" [Server:server] ], [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server] "Services that were unable to start:" => [ [Server:server] "jbosgi.SystemBundle", [Server:server] "jbosgi.SystemContext", [Server:server] "jbosgi.framework.ACTIVE", [Server:server] "jbosgi.framework.INIT", [Server:server] "jbosgi.internal.framework.ACTIVE" [Server:server] ], {code} While this is in domain mode it also occurs in standalone mode was: If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. {code} [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" [Server:server] ], [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { [Server:server] "Services that were unable to start:" => [ [Server:server] "jbosgi.SystemBundle", [Server:server] "jbosgi.SystemContext", [Server:server] "jbosgi.framework.ACTIVE", [Server:server] "jbosgi.framework.INIT", [Server:server] "jbosgi.internal.framework.ACTIVE" [Server:server] ], {code} > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 07:01:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 07:01:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195081#comment-13195081 ] Sander Stoel commented on JBOSGI-792: ------------------------------------- It would require me to filter a lot our data from that, is it also ok if I attach a test case once I'm ready? > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 07:01:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 21 Apr 2016 07:01:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195082#comment-13195082 ] Arcadiy Ivanov commented on JBOSGI-792: --------------------------------------- Also, if you're submitting a PR, could you please make sure it is contained in a feature branch and not master. Thanks a lot! > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 07:05:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 21 Apr 2016 07:05:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195084#comment-13195084 ] Arcadiy Ivanov commented on JBOSGI-792: --------------------------------------- Certainly. Thanks! > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 10:14:00 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 10:14:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sander Stoel updated JBOSGI-792: -------------------------------- Attachment: server.log pom.xml A test pom.xml and the resulting server.log This is triggered by following the steps to reproduce. I have not been able to create an automated test unfortunately > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 10:31:01 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 10:31:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sander Stoel updated JBOSGI-792: -------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/18 > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Apr 21 10:31:01 2016 From: issues at jboss.org (Sander Stoel (JIRA)) Date: Thu, 21 Apr 2016 10:31:01 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195281#comment-13195281 ] Sander Stoel commented on JBOSGI-792: ------------------------------------- Added PR > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Apr 22 18:07:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 22 Apr 2016 18:07:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-792: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi/pull/20, https://github.com/jbosgi/jbosgi/pull/21 (was: https://github.com/jbosgi/jbosgi/pull/18) > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Apr 22 18:08:00 2016 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 22 Apr 2016 18:08:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-792) Initial bundles fail to resolve if runtime name differs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-792. ----------------------------------- Fix Version/s: JBossOSGI 2.5.1 JBossOSGI 2.4.1 Resolution: Done > Initial bundles fail to resolve if runtime name differs > ------------------------------------------------------- > > Key: JBOSGI-792 > URL: https://issues.jboss.org/browse/JBOSGI-792 > Project: JBoss OSGi > Issue Type: Bug > Affects Versions: JBossOSGI 2.3.1, JBossOSGI 2.4.0, JBossOSGI 2.5.0 > Reporter: Sander Stoel > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.5.1, JBossOSGI 2.4.1 > > Attachments: pom.xml, server.log > > > If you load a deployment with a different runtime name than the deployment name deployment will fail on server start. > {code} > [Server:server] "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > [Server:server] "jbosgi.PersistentBundles.INSTALL is missing [jboss.osgi.as.initial.deployments.COMPLETE]", > [Server:server] "jbosgi.internal.framework.INIT is missing [jbosgi.PersistentBundles.COMPLETE]" > [Server:server] ], > [Server:server] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > [Server:server] "Services that were unable to start:" => [ > [Server:server] "jbosgi.SystemBundle", > [Server:server] "jbosgi.SystemContext", > [Server:server] "jbosgi.framework.ACTIVE", > [Server:server] "jbosgi.framework.INIT", > [Server:server] "jbosgi.internal.framework.ACTIVE" > [Server:server] ], > {code} > While this is in domain mode it also occurs in standalone mode -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Apr 30 18:36:00 2016 From: issues at jboss.org (Roman Smushkevich (JIRA)) Date: Sat, 30 Apr 2016 18:36:00 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-793) Can't deploy wab fragment In-Reply-To: References: Message-ID: Roman Smushkevich created JBOSGI-793: ---------------------------------------- Summary: Can't deploy wab fragment Key: JBOSGI-793 URL: https://issues.jboss.org/browse/JBOSGI-793 Project: JBoss OSGi Issue Type: Bug Components: wildfly Affects Versions: JBossOSGI 2.5.0 Reporter: Roman Smushkevich Assignee: Arcadiy Ivanov If you try to deploy a wab fragment to already deployed wab comes exception: {code:java} 00:26:42,178 INFO [org.jboss.osgi.framework] (MSC service thread 1-7) JBOSGI011001: Bundle installed: com.mrs.budget.portal:1.0.0 00:26:42,180 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011001: Bundle installed: com.mrs.budget.portal.resources:1.0.0 00:26:50,267 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "com.mrs.budget.portal.resources.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.jboss.as.webservices.deployers.WSClassVerificationProcessor.deploy(WSClassVerificationProcessor.java:75) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more 00:26:55,362 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0021: Registered web context: /budget 00:26:55,374 INFO [org.jboss.osgi.framework] (MSC service thread 1-8) JBOSGI011002: Bundle started: com.mrs.budget.portal:1.0.0 00:26:55,376 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "com.mrs.budget.portal.resources.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"com.mrs.budget.portal.resources.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"com.mrs.budget.portal.resources.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"com.mrs.budget.portal.resources.jar\" Caused by: java.lang.NullPointerException"}} 00:26:55,393 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "com.mrs.budget.portal.resources.jar" (runtime-name : "com.mrs.budget.portal.resources.jar") 00:26:55,394 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "com.mrs.budget.portal.jar" (runtime-name : "com.mrs.budget.portal.jar") 00:26:55,397 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."com.mrs.budget.portal.resources.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "com.mrs.budget.portal.resources.jar" {code} Debugging showd, that the deployment of wab Fragment tryes to pass through WS verification, that needs a deployment unit module: {code:java} @Override public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException { final DeploymentUnit unit = phaseContext.getDeploymentUnit(); final JAXWSDeployment wsDeployment = unit.getAttachment(JAXWS_ENDPOINTS_KEY); if (wsDeployment != null) { final Module module = unit.getAttachment(Attachments.MODULE); final DeploymentReflectionIndex deploymentReflectionIndex = unit .getAttachment(org.jboss.as.server.deployment.Attachments.REFLECTION_INDEX); final ClassLoader moduleClassLoader = module.getClassLoader(); for (AbstractEndpoint pojoEndpoint : wsDeployment.getPojoEndpoints()) { verifyEndpoint(pojoEndpoint, moduleClassLoader, deploymentReflectionIndex); } for (AbstractEndpoint ejbEndpoint : wsDeployment.getEjbEndpoints()) { verifyEndpoint(ejbEndpoint, moduleClassLoader, deploymentReflectionIndex); } verifyApacheCXFModuleDependencyRequirement(unit); } } {code} but according to ModelManager - fragment is not a module -- This message was sent by Atlassian JIRA (v6.4.11#64026)