location of org.apache.aries.osgi.functional

2017-03-09 Thread David Daniel 
I see things used from https://github.com/csierra/osgi-component-dsl in the
jax-rs whiteboard project but I dont see what bundle includes those aries
functional packages in the bndrun file https://github.com/apache/
aries-jax-rs-whiteboard/blob/master/jax-rs.example/example.bndrun  Can
someone point me to where I can get the bundle that includes the package
org.apache.aries.osgi.functional or should I be building it from the
csierra repo.

Thanks for any help,
  David

Re: location of org.apache.aries.osgi.functional

2017-03-09 Thread David Daniel 
ok I think I found it org.apache.aries.component-dsl.  Please ignore

On Thu, Mar 9, 2017 at 12:28 PM, David Daniel 
wrote:

> I see things used from https://github.com/csierra/osgi-component-dsl in
> the jax-rs whiteboard project but I dont see what bundle includes those
> aries functional packages in the bndrun file
> https://github.com/apache/aries-jax-rs-whiteboard/blob/maste
> r/jax-rs.example/example.bndrun  Can someone point me to where I can get
> the bundle that includes the package org.apache.aries.osgi.functional or
> should I be building it from the csierra repo.
>
> Thanks for any help,
>   David
>

[jira] [Updated] (ARIES-1564) Performance improvement: sorting bundles by start-level is done eagerly

2017-03-09 Thread Wouter Bancken (JIRA) 

 [ 
https://issues.apache.org/jira/browse/ARIES-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wouter Bancken updated ARIES-1564:
--
Priority: Minor  (was: Major)

> Performance improvement: sorting bundles by start-level is done eagerly
> ---
>
> Key: ARIES-1564
> URL: https://issues.apache.org/jira/browse/ARIES-1564
> Project: Aries
>  Issue Type: Improvement
>  Components: Subsystem
>Affects Versions: subsystem-2.0.8
>Reporter: Wouter Bancken
>Priority: Minor
>
> h4. Description
> During sorting in the StartAction class, the SubsystemContentHeader is parsed 
> every time the start order of a bundle is needed. By eagerly parsing the 
> header and storing the start value for every bundle, an improved startup time 
> can be achieved.
> h4. Pull request
> https://github.com/apache/aries/compare/subsystem-2.0.x...WouterBanckenACA:sorting_performance_optimalisation
> h4. Mailinglist
> http://mail-archives.apache.org/mod_mbox/aries-user/201606.mbox/%3CCAL5nZgRQcvFqz8g1c7mKJ3C_UoRmRox10%2BOM2uEjRbCkTYodDQ%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903372#comment-15903372
 ] 

Tom De Wolf edited comment on ARIES-1591 at 3/9/17 4:54 PM:


[~tjwatson] pull request https://github.com/apache/aries/pull/70 fixes this 
issue


was (Author: tom.dewolf):
pull request https://github.com/apache/aries/pull/70 fixes this issue

> Subsystem install fails due to ArrayIndexOutofBoundsException
> -
>
> Key: ARIES-1591
> URL: https://issues.apache.org/jira/browse/ARIES-1591
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> ArrayIndexOutOfBoundsException as soon as our base subsystem contains a 
> fragment bundle:
> {panel}
> Caused by: org.osgi.service.subsystem.SubsystemException: 
> java.lang.ArrayIndexOutOfBoundsException: -1
>   at 
> org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
>   ... 30 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
>   at 
> org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
>   at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
>   ... 41 more
> {panel}
> Attached are 2 subsystems that allow to reproduce it. Note that the ONLY 
> difference between these subsystem esa's and the onces attached at ARIES-1590 
> is the fragment bundle osgi-pax-web-jetty-config.
> So the problem might be related to the same commit, but another effect.
> Note: we are using the felix resolver 1.4.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not 
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 fails with the above exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict

2017-03-09 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903371#comment-15903371
 ] 

ASF GitHub Bot commented on ARIES-1590:
---

GitHub user tomdw opened a pull request:

https://github.com/apache/aries/pull/70

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems

Fixes ARIES-1590, ARIES-1591, ARIES-1588

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tomdw/aries ARIES-1590-fix-resolve-errors

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit eb3a6245511fe74edee2854b5cbeb3d12ccea14f
Author: Tom De Wolf 
Date:   2017-03-09T16:08:24Z

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems




> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will 
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to 
> package 'org.aspectj.bridge' from resources 
> com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and 
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.aspectj.bridge
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package=org.aspectj.weaver; 
> uses:=org.aspectj.weaver.patterns
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
>  |
> export: osgi.wiring.package: org.aspectj.weaver.patterns; 
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
>   org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that 
> exports the package and the other of the 2 chains points to the base 
> subsystem already installed in the runtime. In fact the bundle is part of 
> that subsystem so it should consider both as exactly the same and not 
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but 
> that commit does affect how already installed subsystems are taken into 
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0, verified it has the same problem 
> with 1.8.0
> Steps to reproduce:
> 1.

[jira] [Commented] (ARIES-1588) Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903374#comment-15903374
 ] 

Tom De Wolf commented on ARIES-1588:


[~tjwatson] pull request https://github.com/apache/aries/pull/70 fixes this 
issue

> Installation of subsystems fails due to uses constraint violation after 
> exposing feature capabilities.
> --
>
> Key: ARIES-1588
> URL: https://issues.apache.org/jira/browse/ARIES-1588
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-2.1.0
>Reporter: Wouter Bancken
> Fix For: subsystem-2.1.0
>
> Attachments: pax-web-jetty-bundle-4.2.5.jar
>
>
> h4. Setup
> Two feature subsystems
> 1. Feature subsystem with fragment-hosts and fragments
> 2. Feature subsystem with other bundles
> Installation of the second subsystem fails
> h4. Issue
> Installation of the second subsystem fails with the message 
> {quote}
> gogo: SubsystemException: org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0] because it exports package 
> 'org.apache.xbean.finder.archive' and is also exposed to it from resource 
> org.apache.xbean.finder [98.0] via the following dependency chain:
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0]
> import: (osgi.wiring.package=org.apache.xbean.finder)
> export: osgi.wiring.package: org.apache.xbean.finder; 
> uses:=org.apache.xbean.finder.archive
> export: osgi.wiring.package=org.apache.xbean.finder.archive
> org.apache.xbean.finder [98.0]
> {quote}
> Before failing a lot of similar messages are logged with the message "DEBUG: 
> Candidate permutation failed due to a conflict between an export and import; 
> will try another if possible."
> This is especially weird since pax-web-jetty-bundle does not expose the 
> org.apache.xbean.finder.archive package (see attached Jar). Both 
> pax-web-jetty-bundle and org.apache.xbean.finder are only present in the 
> first subsystem.
> In our setup pax-web-jetty-bundle is a fragment-host for a fragment which is 
> in the same (first) subsystem. Similar DEBUG statements are printed for other 
> fragment-hosts in the first subsystem.
> The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5 
> (ARIES-1443). In earlier versions, we had no issues for these subsystems. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903376#comment-15903376
 ] 

Tom De Wolf commented on ARIES-1590:


[~tjwatson] pull request https://github.com/apache/aries/pull/70 fixes this 
issue

> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will 
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to 
> package 'org.aspectj.bridge' from resources 
> com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and 
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.aspectj.bridge
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package=org.aspectj.weaver; 
> uses:=org.aspectj.weaver.patterns
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
>  |
> export: osgi.wiring.package: org.aspectj.weaver.patterns; 
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
>   org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that 
> exports the package and the other of the 2 chains points to the base 
> subsystem already installed in the runtime. In fact the bundle is part of 
> that subsystem so it should consider both as exactly the same and not 
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but 
> that commit does affect how already installed subsystems are taken into 
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0, verified it has the same problem 
> with 1.8.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not 
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 will start failing in DEBUG logging with chain errors like above. It 
> will try a number of permutations but it will not get out of it. 
> Note: which bundles and packages are shown in the example log above are less 
> important as we have multiple such kind of errors for which only the package 
> and bundles differ.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] aries pull request #70: ARIES-1590 revert commit of ARIES-1443 without break...

2017-03-09 Thread tomdw 
GitHub user tomdw opened a pull request:

https://github.com/apache/aries/pull/70

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems

Fixes ARIES-1590, ARIES-1591, ARIES-1588

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tomdw/aries ARIES-1590-fix-resolve-errors

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/aries/pull/70.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #70


commit eb3a6245511fe74edee2854b5cbeb3d12ccea14f
Author: Tom De Wolf 
Date:   2017-03-09T16:08:24Z

ARIES-1590 revert commit of ARIES-1443 without breaking being able to 
install nested feature subsystems




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ARIES-1564) Performance improvement: sorting bundles by start-level is done eagerly

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903173#comment-15903173
 ] 

Tom De Wolf commented on ARIES-1564:


[~Wouter Bancken] correct me if I'm wrong, but a number of other perf 
improvements makes this issue obsolete?

> Performance improvement: sorting bundles by start-level is done eagerly
> ---
>
> Key: ARIES-1564
> URL: https://issues.apache.org/jira/browse/ARIES-1564
> Project: Aries
>  Issue Type: Improvement
>  Components: Subsystem
>Affects Versions: subsystem-2.0.8
>Reporter: Wouter Bancken
>
> h4. Description
> During sorting in the StartAction class, the SubsystemContentHeader is parsed 
> every time the start order of a bundle is needed. By eagerly parsing the 
> header and storing the start value for every bundle, an improved startup time 
> can be achieved.
> h4. Pull request
> https://github.com/apache/aries/compare/subsystem-2.0.x...WouterBanckenACA:sorting_performance_optimalisation
> h4. Mailinglist
> http://mail-archives.apache.org/mod_mbox/aries-user/201606.mbox/%3CCAL5nZgRQcvFqz8g1c7mKJ3C_UoRmRox10%2BOM2uEjRbCkTYodDQ%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1591) Subsystem install fails due to ArrayIndexOutofBoundsException

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903167#comment-15903167
 ] 

Tom De Wolf commented on ARIES-1591:


[~tjwatson] same problem with felix resolver 1.12.0 and subsystems 
2.0.9-SNAPSHOT (latest snapshot). Please consider reverting ARIES-1443, 
specifically commit 4c0437de06f34321909a6132a7f2be163b2f6d5 as that is the 
cause that breaks aries subsystems.

> Subsystem install fails due to ArrayIndexOutofBoundsException
> -
>
> Key: ARIES-1591
> URL: https://issues.apache.org/jira/browse/ARIES-1591
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> ArrayIndexOutOfBoundsException as soon as our base subsystem contains a 
> fragment bundle:
> {panel}
> Caused by: org.osgi.service.subsystem.SubsystemException: 
> java.lang.ArrayIndexOutOfBoundsException: -1
>   at 
> org.apache.aries.subsystem.core.internal.Utils.handleTrowable(Utils.java:117)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:398)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:101)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:91)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60)
>   at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:738)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:791)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:365)
>   at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:70)
>   ... 30 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
>   at 
> org.apache.felix.resolver.util.CopyOnWriteList.set(CopyOnWriteList.java:53)
>   at org.apache.felix.resolver.Candidates.prepare(Candidates.java:1052)
>   at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:173)
>   at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393)
>   ... 41 more
> {panel}
> Attached are 2 subsystems that allow to reproduce it. Note that the ONLY 
> difference between these subsystem esa's and the onces attached at ARIES-1590 
> is the fragment bundle osgi-pax-web-jetty-config.
> So the problem might be related to the same commit, but another effect.
> Note: we are using the felix resolver 1.4.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not 
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 fails with the above exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1590) Subsystem install fails due to unexpected resolve conflict

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903152#comment-15903152
 ] 

Tom De Wolf commented on ARIES-1590:


[~tjwatson] I've tested it again with felix resolver 1.12.0 and it still has 
the same problem. Please consider reverting ARIES-1443, specifically commit 
4c0437de06f34321909a6132a7f2be163b2f6d5 as that is the cause that breaks aries 
subsystems. 

> Subsystem install fails due to unexpected resolve conflict
> --
>
> Key: ARIES-1590
> URL: https://issues.apache.org/jira/browse/ARIES-1590
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Reporter: Tom De Wolf
>Priority: Blocker
> Fix For: subsystem-2.1.0
>
> Attachments: reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, 
> reproduce-subsystem-4.1.2-SNAPSHOT.esa
>
>
> When we use the 2.0.9-SNAPSHOT version currently in development we get an 
> unexpected resolve conflict:
> {panel}
> DEBUG: Candidate permutation failed due to a conflict between imports; will 
> try another if possible. (org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.apache.servicemix.bundles.spring-core [116.0] because it is exposed to 
> package 'org.aspectj.bridge' from resources 
> com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT] and 
> org.apache.servicemix.bundles.aspectj [111.0] via two dependency chains.
> Chain 1:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.bridge)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package: org.aspectj.bridge
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> Chain 2:
>   org.apache.servicemix.bundles.spring-core [116.0]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver)(version>=1.7.1)(!(version>=2.0.0)))
>  |
> export: osgi.wiring.package=org.aspectj.weaver; 
> uses:=org.aspectj.weaver.patterns
>   com.reproduce.reproduce-base-subsystem 
> [org.apache.aries.subsystem.core.internal.BasicSubsystem: children=0, 
> constituents=60, id=3, 
> location=file:///Users/tom/Documents/code/aca-common/osgi-subsystem-support/reproduce-base-subsystem/target/reproduce-base-subsystem-4.1.2-SNAPSHOT.esa,
>  parents=1, state=INSTALLED, 
> symbolicName=com.reproduce.reproduce-base-subsystem, 
> type=osgi.subsystem.feature, version=4.1.2.SNAPSHOT]
> import: 
> (&(osgi.wiring.package=org.aspectj.weaver.patterns)(&(version>=1.7.1)(!(version>=2.0.0
>  |
> export: osgi.wiring.package: org.aspectj.weaver.patterns; 
> uses:=org.aspectj.bridge
> export: osgi.wiring.package=org.aspectj.bridge
>   org.apache.servicemix.bundles.aspectj [111.0])
> {panel}
> It is unexpected because 1 of the 2 chains points to the actual bundle that 
> exports the package and the other of the 2 chains points to the base 
> subsystem already installed in the runtime. In fact the bundle is part of 
> that subsystem so it should consider both as exactly the same and not 
> consider it as 2 chains he cannot resolve.
> Not sure if it is related to ARIES-1588 and the commit mentioned there but 
> that commit does affect how already installed subsystems are taken into 
> account in the resolve process.
> Note: we are using the felix resolver 1.4.0, verified it has the same problem 
> with 1.8.0
> Steps to reproduce:
> 1. start clean felix
> 2. install the attached reproduce-base-subsystem-4.1.2-SNAPSHOT.esa, do not 
> start it
> 3. install the attached reproduce-subsystem-4.1.2-SNAPSHOT.esa
> Step 3 will start failing in DEBUG logging with chain errors like above. It 
> will try a number of permutations but it will not get out of it. 
> Note: which bundles and packages are shown in the example log above are less 
> important as we have multiple such kind of errors for which only the package 
> and bundles differ.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ARIES-1588) Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.

2017-03-09 Thread Tom De Wolf (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARIES-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903151#comment-15903151
 ] 

Tom De Wolf commented on ARIES-1588:


[~tjwatson] same problem with felix resolver 1.12.0 and subsystems 
2.0.9-SNAPSHOT (latest snapshot). Please consider reverting ARIES-1443, 
specifically commit 4c0437de06f34321909a6132a7f2be163b2f6d5 as that is the 
cause that breaks aries subsystems. 

> Installation of subsystems fails due to uses constraint violation after 
> exposing feature capabilities.
> --
>
> Key: ARIES-1588
> URL: https://issues.apache.org/jira/browse/ARIES-1588
> Project: Aries
>  Issue Type: Bug
>  Components: Subsystem
>Affects Versions: subsystem-2.1.0
>Reporter: Wouter Bancken
> Fix For: subsystem-2.1.0
>
> Attachments: pax-web-jetty-bundle-4.2.5.jar
>
>
> h4. Setup
> Two feature subsystems
> 1. Feature subsystem with fragment-hosts and fragments
> 2. Feature subsystem with other bundles
> Installation of the second subsystem fails
> h4. Issue
> Installation of the second subsystem fails with the message 
> {quote}
> gogo: SubsystemException: org.osgi.service.resolver.ResolutionException: Uses 
> constraint violation. Unable to resolve resource 
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0] because it exports package 
> 'org.apache.xbean.finder.archive' and is also exposed to it from resource 
> org.apache.xbean.finder [98.0] via the following dependency chain:
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0]
> import: (osgi.wiring.package=org.apache.xbean.finder)
> export: osgi.wiring.package: org.apache.xbean.finder; 
> uses:=org.apache.xbean.finder.archive
> export: osgi.wiring.package=org.apache.xbean.finder.archive
> org.apache.xbean.finder [98.0]
> {quote}
> Before failing a lot of similar messages are logged with the message "DEBUG: 
> Candidate permutation failed due to a conflict between an export and import; 
> will try another if possible."
> This is especially weird since pax-web-jetty-bundle does not expose the 
> org.apache.xbean.finder.archive package (see attached Jar). Both 
> pax-web-jetty-bundle and org.apache.xbean.finder are only present in the 
> first subsystem.
> In our setup pax-web-jetty-bundle is a fragment-host for a fragment which is 
> in the same (first) subsystem. Similar DEBUG statements are printed for other 
> fragment-hosts in the first subsystem.
> The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5 
> (ARIES-1443). In earlier versions, we had no issues for these subsystems. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release esa-maven-plugin 1.0.2

2017-03-09 Thread davidb 
Nobody else voting?

PS... just as a reminder - anyone can vote, you don't have to be a
committer :)
But we do need 2 additional PMC member votes for this to pass...

Cheers,

David

On 7 March 2017 at 22:17,  wrote:

> Here's my +1
>
> David
>
> On 7 March 2017 at 09:45,  wrote:
>
>> Hi all,
>>
>> I'm calling a vote on the esa-maven-plugin version 1.0.2.
>>
>> The following issues are fixed in this release:
>> * ARIES-1490 Add feature to configure the 'Subsystem-Content' header
>> * ARIES-1650 Maven plugin no longer includes non-bundle artifacts
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachearies-1101
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
>>
>> Usage:
>> sh verify_staged_release.sh 1101 tmpdir 2>&1 | tee verifyresults.txt
>>
>> More details on verifying the release here:
>> http://aries.apache.org/development/verifyingrelease.html
>>
>> Please vote:
>>  +1 Approve the release
>>  -1 Do not approve the release (please explain why)
>>
>> This vote will be open for at least 72 hours.
>>
>> Best regards,
>>
>> David Bosschaert
>>
>
>