]
Thomas Diesler resolved JBOSGI-129.
-----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta5
(was: JBossOSGi 1.0.x)
Resolution: Done
------- Comment #4 From BJ Hargrave 2009-11-09 19:01:51 UTC [reply] -------
Fixed in Equinox and CT.
Filter behaviour change in r4v42
--------------------------------
Key: JBOSGI-129
URL:
https://jira.jboss.org/jira/browse/JBOSGI-129
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Environment: [Bug 1418]
https://www.osgi.org/members/bugzilla/show_bug.cgi?id=1418
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta5
Running org.jboss.test.osgi.filter.test.FrameworkUtilFilterUnitTestCase
FIXME: verify: Invalid (*=b)
FIXME: verify: NoMatch (a=)
FIXME: verify: NoMatch (a<= 2)
FIXME: verify: NoMatch (a<=2 )
FIXME: verify: NoMatch (a<= )
FIXME: verify: NoMatch (a>= 0)
FIXME: verify: NoMatch (a>=0 )
FIXME: verify: NoMatch (a>= )
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.435 sec
Running org.jboss.test.osgi.filter.test.BundleContextFilterUnitTestCase
FIXME: verify: Invalid (*=b)
FIXME: verify: NoMatch (a=)
FIXME: verify: NoMatch (a<= 2)
FIXME: verify: NoMatch (a<=2 )
FIXME: verify: NoMatch (a<= )
FIXME: verify: NoMatch (a>= 0)
FIXME: verify: NoMatch (a>=0 )
FIXME: verify: NoMatch (a>= )
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.584 sec
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: