[
https://issues.apache.org/jira/browse/FELIX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-483.
-----------------------------------
Resolution: Fixed
Fix Version/s: bundlerepository-1.6.0
I've changed the filter implementation which now supports SUBSET / SUPERSET
operators, but based on the osgi filter implementation which does pre-parse.
In addition, the new StaxParser throws an exception which now includes the xml
location information if available.
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M
bundlerepository/src/main/java/org/apache/felix/bundlerepository/StaxParser.java
Committed r916282
> 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: Guillaume Nodet
> Fix For: bundlerepository-1.6.0
>
>
> 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.
