https://issues.apache.org/bugzilla/show_bug.cgi?id=48825
Jesse Glick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #4 from Jesse Glick <[email protected]> 2010-02-27 16:14:47 UTC --- (In reply to comment #3) > So the problem is not that that Project#setProperty does not override > properties any more, rather that Property#addProperty is not called in your > piece of code. Indeed. A kind of incompatibility in Property but probably not one that can be trivially fixed. (A demonstration of why you should not permit subclassing without a lot of preparation...) An alternate version of the task that works in both 1.7.1 and 1.8.0: public class OverrideTask extends Property { protected @Override void addProperty(String n, String v) { getProject().setProperty(n, v); } protected /*...@override*/ void addProperty(String n, Object v) { getProject().setProperty(n, (String) v); } } -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
