Please describe use-case:
We want Blacken to be widely used and available.
It should be packaged in Debian. If it can get packaged in Debian, it will be
package-able by other distributions as well. (All of the core issues preventing
packaging will be resolved.)
See: http://wiki.debian.org/UpstreamGuide
We need to have a solid plan in place to check API and ABI compatibility.
See http://wiki.eclipse.org/Evolving_Java-based_APIs for details on maintaining
compatibility.
I think we're going to need a helper test function which can generate code to
verify all API functions are still available. It need not call the functions,
it only needs to verify they are still visible.
I'm thinking a variation on the Covers/Coverage logic currently in place. If we
go with something along these lines, it can notice when API functions are
missing from the test and complain with enough information that the test can be
updated.
Note that this isn't slated until after we have a fully functional tutorial
game, so there will be "real content" that can use the library right from the
beginning.
Original issue reported on code.google.com by yam...@gmail.com on 27 Sep 2012 at 2:28
Original issue reported on code.google.com by
yam...@gmail.comon 27 Sep 2012 at 2:28