[
https://issues.apache.org/jira/browse/FELIX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835649#action_12835649
]
Richard S. Hall commented on FELIX-483:
---------------------------------------
Yeah, this is because we use a new FilterImpl now that doesn't throw parse
exceptions until its performs its matching, previously we were using the Felix
framework's filter implementation that did pre-parse...now that filter
implementation does even exist. However, in the next major release of the
framework, it looks like we'll be introducing another filter
implementation...so we could consider using that again.
> Log detailed information on invalid syntax in parsed repository xml
> requirements
> --------------------------------------------------------------------------------
>
> Key: FELIX-483
> URL: https://issues.apache.org/jira/browse/FELIX-483
> Project: Felix
> Issue Type: Improvement
> Components: Bundle Repository (OBR)
> Affects Versions: bundlerepository-1.2.0
> Reporter: Alin Dreghiciu
> Assignee: Richard S. Hall
>
> While parsing the repository xml BundleRepository logs an exception message
> while parsing requirements. This is fine but the information logged is not of
> too much use.
> Eg. for the sogi alliance repository it will log something like:
> org.osgi.framework.InvalidSyntaxException: expected ~=|>=|<=
> Just with this information you cannot do to much.
> I suggest that RequirementImpl.setFilter to be changed to output also the
> failing filter.
> e.g. for the case above:
> Filter (&(package=org.apache.batik.i18n)(version>=1.6.0)(version<1.7.0))
> parsing failed due to org.osgi.framework.InvalidSyntaxException: expected
> ~=|>=|<=
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
