[jira] [Commented] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281683#comment-13281683 ] Thomas Diesler commented on FELIX-3521: --- The test fails at the very last assertion. Please also see the log for test progress. Here the test in prose: // Bundle-SymbolicName: requirebundleB // Export-Package: resources // Bundle-SymbolicName: requirebundleC // Export-Package: resources resolve B,C // Bundle-SymbolicName: requirebundleD // Export-Package: org.jboss.osgi.test.classloading.export;uses:=resources // Import-Package: resources;bundle-symbolic-name=requirebundleC resolve D verify that D wires to C // Bundle-SymbolicName: requirebundleE // Require-Bundle: requirebundleD // Import-Package: resources resolve E verify that E wires to C > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281604#comment-13281604
]
Daniel Kuffner commented on FELIX-3519:
---
I have to make soem more tests later or tomorrow. I have still the feeling that
there is some inconsistence. :)
thanks for your help.
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281581#comment-13281581 ] Richard S. Hall edited comment on FELIX-3521 at 5/23/12 1:14 PM: - I don't find the information in this bug report to be super helpful. Would be nice if you included an actual textual description of the scenario (without a description here, this bug becomes stale if the link ever returns something else). At a minimum, it would be nice to mention the line number where it fails. Thanks. was (Author: rickhall): I don't find the information in this bug report to be super helpful (without a description here, this bug becomes stale if the link ever returns something else). Would be nice if you included an actual textual description of the scenario. At a minimum, it would be nice to mention the line number where it fails. Thanks. > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281581#comment-13281581 ] Richard S. Hall edited comment on FELIX-3521 at 5/23/12 1:13 PM: - I don't find the information in this bug report to be super helpful (without a description here, this bug becomes stale if the link ever returns something else). Would be nice if you included an actual textual description of the scenario. At a minimum, it would be nice to mention the line number where it fails. Thanks. was (Author: rickhall): I don't find the information in this bug report to be super helpful. Would be nice if you included an actual textual description of the scenario. At a minimum, it would be nice to mention the line number where it fails. Thanks. > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281581#comment-13281581 ] Richard S. Hall commented on FELIX-3521: I don't find the information in this bug report to be super helpful. Would be nice if you included an actual textual description of the scenario. At a minimum, it would be nice to mention the line number where it fails. Thanks. > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281557#comment-13281557
]
Carsten Ziegeler commented on FELIX-3519:
-
The build should only fail if you have set strictMode to true - in that case
all warnings are considered as errors
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281556#comment-13281556 ] Thomas Watson commented on FELIX-3521: -- Do the capabilities in the testcase actually contain the proper attributes for the bundle-symbolic-name? I would not think the resolver would be responsible for adding them for you. > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281535#comment-13281535
]
Daniel Kuffner commented on FELIX-3519:
---
Ok make sense to me but in my case the ANT build failes because of the warning.
Is that abug of the ANT tool or is that somehow configurable?
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281521#comment-13281521
]
Carsten Ziegeler commented on FELIX-3519:
-
Ah ok, thanks for the update!
Actually its a warning by intention to be compatible. Imagine you're writing a
component for 1.0 of the spec but for some reason have an activate() method
which is not intended to be called by SCR (and won't be called because of the
1.0 compliance). In this case, an error would break the build and you would
have no chance to get the build running other than renaming this method - which
might not be possible for some reason.
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281481#comment-13281481
]
Daniel Kuffner commented on FELIX-3519:
---
Yes it works if I put the specVersion on the Component.
I have retested it and I figured out that I have posted the wrong parameters in
the bug description.
It will not fail if I specify the specVersion 1.1 on the ant task. Sorry for
the confusion.
Can we issue the problem as an error instead of a warning for future releases?
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3512) SCR Annotation Reference Documentation - "interface" must be "referenceInterface"
[ https://issues.apache.org/jira/browse/FELIX-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-3512. - Resolution: Fixed Thanks, I've corrected this > SCR Annotation Reference Documentation - "interface" must be > "referenceInterface" > - > > Key: FELIX-3512 > URL: https://issues.apache.org/jira/browse/FELIX-3512 > Project: Felix > Issue Type: Bug > Components: Documentation >Reporter: Daniel Kuffner >Assignee: Carsten Ziegeler > > Please documentation of Reference on > http://felix.apache.org/site/scr-annotations.html > The table contains a annotation attribute called "interface" which doesn't > exist. > The correct name is "referenceInterface" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-3512) SCR Annotation Reference Documentation - "interface" must be "referenceInterface"
[ https://issues.apache.org/jira/browse/FELIX-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-3512: --- Assignee: Carsten Ziegeler > SCR Annotation Reference Documentation - "interface" must be > "referenceInterface" > - > > Key: FELIX-3512 > URL: https://issues.apache.org/jira/browse/FELIX-3512 > Project: Felix > Issue Type: Bug > Components: Documentation >Reporter: Daniel Kuffner >Assignee: Carsten Ziegeler > > Please documentation of Reference on > http://felix.apache.org/site/scr-annotations.html > The table contains a annotation attribute called "interface" which doesn't > exist. > The correct name is "referenceInterface" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3523) Properly serialize multiple bundle installations
Felix Meschberger created FELIX-3523: Summary: Properly serialize multiple bundle installations Key: FELIX-3523 URL: https://issues.apache.org/jira/browse/FELIX-3523 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Consider an administrator wishing to install a number of interdependent bundles through the Web Console. There are basically two options: (1) Multiple requests with one bundle after the other. Problem is that installation takes place asynchronously and there is no easy and direct feedback on the installation. Thus sending successive requests must be timed. Not nice. (2) Send one single request with multiple bundlefile parameters. Unfortunately, this does not work either, because each bundle is installed in its own thread. Not nice. I see two solutions: (a) add an option requesting synchronous installation instead of background installation. When using HTTP clients such as cURL such an option can easily be used and leveraged because there is little chance of deadlocks (which lead to the asynchronous installation in the first place) (b) implement a proper queue for asynchronous installation such that the installation of multiple bundles can be properly serialized. This would have the added benefit of not creating a new thread for each installation. Caveat for synchronization: If the Web Console itself is to be updated, synchronous installation/update may fail. Such an implementation much take precaution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3519) [SCR ANT] A activator method without parameters issue a warning and failes the build
[
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281441#comment-13281441
]
Carsten Ziegeler commented on FELIX-3519:
-
Yes, I agree this should work and activate() is a valid signature.
Could you please try if adding specVersion="1.1" to the @Component tag works as
well (without adding @Activate)?
> [SCR ANT] A activator method without parameters issue a warning and failes
> the build
>
>
> Key: FELIX-3519
> URL: https://issues.apache.org/jira/browse/FELIX-3519
> Project: Felix
> Issue Type: Bug
> Components: SCR Annotations
>Affects Versions: scr generator 1.1.4
>Reporter: Daniel Kuffner
> Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
> classpathref="scr-classpath"
>parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3522) Regression related to uses clause with multiple package providers
[ https://issues.apache.org/jira/browse/FELIX-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated FELIX-3522: -- Description: For this test https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/UsesDirectiveResolverTest.java I get Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.116 sec <<< FAILURE! testMultipleProviders(org.jboss.test.osgi.resolver.UsesDirectiveResolverTest) Time elapsed: 0.096 sec <<< ERROR! org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] because it is exposed to package 'javax.servlet' from resources javax.servlet.api [AbstractResource[javax.servlet.api:0.0.0]] and http.service.provider [AbstractResource[http.service.provider:0.0.0]] via two dependency chains. Chain 1: war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] import: null | export: osgi.wiring.package=javax.servlet javax.servlet.api [AbstractResource[javax.servlet.api:0.0.0]] Chain 2: war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] import: null | export: osgi.wiring.package=org.ops4j.pax.web.service; uses:=javax.servlet export: osgi.wiring.package=javax.servlet http.service.provider [AbstractResource[http.service.provider:0.0.0]] at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1134) at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:197) at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:57) at org.jboss.test.osgi.resolver.UsesDirectiveResolverTest.testMultipleProviders(UsesDirectiveResolverTest.java:158) was: For this test https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 I get Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< FAILURE! testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) Time elapsed: 0.053 sec <<< FAILURE! junit.framework.AssertionFailedError: expected: but was: > Regression related to uses clause with multiple package providers > - > > Key: FELIX-3522 > URL: https://issues.apache.org/jira/browse/FELIX-3522 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/UsesDirectiveResolverTest.java > I get > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.116 sec <<< > FAILURE! > testMultipleProviders(org.jboss.test.osgi.resolver.UsesDirectiveResolverTest) > Time elapsed: 0.096 sec <<< ERROR! > org.osgi.service.resolver.ResolutionException: Uses constraint violation. > Unable to resolve resource war.extender.jar > [AbstractResource[war.extender.jar:0.0.0]] because it is exposed to package > 'javax.servlet' from resources javax.servlet.api > [AbstractResource[javax.servlet.api:0.0.0]] and http.service.provider > [AbstractResource[http.service.provider:0.0.0]] via two dependency chains. > Chain 1: > war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] > import: null > | > export: osgi.wiring.package=javax.servlet > javax.servlet.api [AbstractResource[javax.servlet.api:0.0.0]] > Chain 2: > war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] > import: null > | > export: osgi.wiring.package=org.ops4j.pax.web.service; uses:=javax.servlet > export: osgi.wiring.package=javax.servlet > http.service.provider [AbstractResource[http.service.provider:0.0.0]] > at > org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1134) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:197) > at > org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:57) > at > org.jboss.test.osgi.resolver.UsesDirectiveResolverTest.testMultipleProviders(UsesDirectiveResolverTest.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3522) Regression related to uses clause with multiple package providers
[ https://issues.apache.org/jira/browse/FELIX-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated FELIX-3522: -- Attachment: test.log > Regression related to uses clause with multiple package providers > - > > Key: FELIX-3522 > URL: https://issues.apache.org/jira/browse/FELIX-3522 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/UsesDirectiveResolverTest.java > I get > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.116 sec <<< > FAILURE! > testMultipleProviders(org.jboss.test.osgi.resolver.UsesDirectiveResolverTest) > Time elapsed: 0.096 sec <<< ERROR! > org.osgi.service.resolver.ResolutionException: Uses constraint violation. > Unable to resolve resource war.extender.jar > [AbstractResource[war.extender.jar:0.0.0]] because it is exposed to package > 'javax.servlet' from resources javax.servlet.api > [AbstractResource[javax.servlet.api:0.0.0]] and http.service.provider > [AbstractResource[http.service.provider:0.0.0]] via two dependency chains. > Chain 1: > war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] > import: null > | > export: osgi.wiring.package=javax.servlet > javax.servlet.api [AbstractResource[javax.servlet.api:0.0.0]] > Chain 2: > war.extender.jar [AbstractResource[war.extender.jar:0.0.0]] > import: null > | > export: osgi.wiring.package=org.ops4j.pax.web.service; uses:=javax.servlet > export: osgi.wiring.package=javax.servlet > http.service.provider [AbstractResource[http.service.provider:0.0.0]] > at > org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1134) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:197) > at > org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:57) > at > org.jboss.test.osgi.resolver.UsesDirectiveResolverTest.testMultipleProviders(UsesDirectiveResolverTest.java:158) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3522) Regression related to uses clause with multiple package providers
Thomas Diesler created FELIX-3522: - Summary: Regression related to uses clause with multiple package providers Key: FELIX-3522 URL: https://issues.apache.org/jira/browse/FELIX-3522 Project: Felix Issue Type: Bug Components: Resolver Reporter: Thomas Diesler For this test https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 I get Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< FAILURE! testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) Time elapsed: 0.053 sec <<< FAILURE! junit.framework.AssertionFailedError: expected: but was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3521) Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute
[ https://issues.apache.org/jira/browse/FELIX-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated FELIX-3521: -- Summary: Regression related to RequireBundle and Import-Package with bundle-symbolic-name attribute (was: Incorrect wire related to RequireBundle and Import-Package with bundle-symbolic-name attribute) > Regression related to RequireBundle and Import-Package with > bundle-symbolic-name attribute > -- > > Key: FELIX-3521 > URL: https://issues.apache.org/jira/browse/FELIX-3521 > Project: Felix > Issue Type: Bug > Components: Resolver >Reporter: Thomas Diesler > Attachments: test.log > > > For this test > https://github.com/tdiesler/jbosgi-resolver/blob/3.0/felix/src/test/java/org/jboss/test/osgi/resolver/RequireBundleResolverTest.java#L226 > I get > Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<< > FAILURE! > testImportBySymbolicName(org.jboss.test.osgi.resolver.RequireBundleResolverTest) > Time elapsed: 0.053 sec <<< FAILURE! > junit.framework.AssertionFailedError: > expected: but > was: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
