Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350814 - Clean-up API filters before releasing for Juno
Summary: Clean-up API filters before releasing for Juno
Status: CLOSED FIXED
Alias: None
Product: Graphiti
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 0.9.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: Juno RC3 Theme_round_offs
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-30 08:25 EDT by Michael Wenz CLA
Modified: 2012-06-29 04:30 EDT (History)
1 user (show)

See Also:
michael.wenz: juno+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wenz CLA 2011-06-30 08:25:44 EDT
There are some API filters defined for the Graphiti framework projects. Clean-up and remove the filters that are no longer necessary (e.g. usage of former non-API stuff or execptions introduced to avoid the need to increase versions to 1.0)
Comment 1 Michael Wenz CLA 2011-07-19 04:14:13 EDT
Needs to be done for Juno, but only in a late phase (M7?)
Comment 2 Michael Wenz CLA 2012-05-31 10:23:55 EDT
- I removed the no longer needed API filters (actually only 1)
- I enabled the automatic removal of unused API filters for each project
- I aligned the target API baseline definition in the build with the plain and simple standard Graphiti 0.8.0 installation to avoid ghost unused API filter warnings in the central build

--> central build does no longer show any unused API filter warnings
Comment 3 Michael Wenz CLA 2012-06-01 03:34:54 EDT
I removed the automatic deletion of not used API filters again since it lead to spontaneously appearing changes that were not easy to understand. This happened already in case a slightly different baseline had been set.
Comment 4 Michael Wenz CLA 2012-06-29 04:30:59 EDT
Part of Graphiti 0.9.0 (Eclipse Juno)