Community
Participate
Working Groups
This is a sibling of bug 329984, which starts: "In bug 329854 we noticed that a misspelled platform filter is never diagnosed throughout the whole tool chain editor->builder->metadata generator up-to the b3 aggregator. It was argued that the aggregator doesn't know about *platform filters*, but only about generic filters. However, the manifest clearly states "Eclipse-PlatformFilter", so before the information is lost that the filter is intended to be a platform filter someone should check it." I see two (non-exclusive) ways how p2 could help: - During build/generate-metadata the platform filter could be validated against a list of legal names/values. - During planning the explanation for an unavailable artifact could state for which platform the required artifact was indeed unavailable (if filtering occurred).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
