if we break the api it is not our responsibility to fix it, it is the job of whoever is responsible for that wicket-stuff project.
Technically, you are right. Practically you are not. * To start with, It's just a matter of courtesy. * It's much less work for the one doing the API break to fix other projects than for someone who probably doesn't right away understand the break/ ideas/ consequences. Where it takes a couple of minutes for the 'breaker' to fix a project, it takes an hour or more for someone else. * We have been moving fast with our breaks up to a point that it has probably been pretty hard to keep up for anyone but the core members. * In the end, I've been doing 90% of the wicket-stuff fixes (and I often waited for a few weeks and even asked on the dev list if others would take some time to fix it), whereas I've been repsonsible for maybe 10% of the breaks. And that's a bit of team work than can be improved imo. Eelco
