Let's fork BeansBinding
I think that most of the interested people have understood what I'm going to say. BeansBinding (aka JSR 295) is a good module to bring the magic of property binding into Java. While it's far from being so elegant as binding in JavaFX (where binding has got language support), to me it's a good library doing its job well. Also, NetBeans has got support for it in its visual editor (former Matisse). I'm personally using it a lot - it also looks reasonably stable, even though I've filed a bug against it. People with more complex needs are complaining about some more serious issues or missing features. I myself have developed a few small classes that help me a lot in some cases (managing the EDT, demarcating transactions) and probably could be contributed back.
The problem is that the API has not been developed since late 2007. Unfortunately it's a story that sometimes occurs with Sun, probably because Shannon Hickey is busy doing other things. This is not bad per se, as we all understand the current Sun status and effort on projects that they presume critical as JavaFX (and I agree with them). What I find silly is that they don't communicate about the problem. How can you critically use a product if you don't know how much it will be supported in future?
The latest paradox is that a few days ago Eclipse guys started advertising their own binding stuff on the BeansBinding mailing list - and still no reaction from Sun! Get me right - there's nothing wrong or immoral in what the Eclipse guys did. We live in a open community and there's competition - "it's the economy, stupid". But I find it silly to see the competitor taking away customers and still sit in silence.
So, I'm now going to fork BeansBinding and maintaining it on my own. I hope/presume that there is some other guy willing to do that, so it will be a genuine community effort. It doesn't seem a hard task, since the code looks clean (more info after I run FindBugs on it), there are 126 classes in total, of which only 43 are new, the others a forked, patched implementation of the EL language. I hope that we are able to get the patches incorporated into EL (and maybe in the latest 1.5 years this has been already done). There are just a handful of tests, so the first thing to do is to give the project a good coverage.
The idea is to keep the new thing under the original license (LGPL) and the same packages / classes names, so it can be dropped in as a replacement of the original (keeping compatibility also with the NetBeans visual designer). Extensions could be put initially in a separate JAR file; should Sun wake up in the near future, this would facilitate a re-join. I'm going to open the project on Kenai.
The only thing that is not clear to me is how to name the project, so please give me suggestions. I've only a trivial idea such as BeansBinding2. Also, it's the first time I fork a project, so I probably have to do some due diligence for the bureaucracy.