I know this Problem. [...] Best example is the NEI-API[...]
Oh, God, yes. I tried to include the NEI API in my APIs and the amount of complaining it does is just incredible. Luckily for me, mcp_deobfuscate is very clever, so just putting the NEI jar in lib-obf and running deobfuscate_libs makes its classes and methods available for linking (via classpath during the compile process), allowing recompile_mods to just do its thing.
In unrelated news, I've made another experimental version! I'll quote the OP for the change list, since it's fairly long:
QuoteDisplay More[v0.7.11-experimental2] changes the UU conversion ratios when using a buildcraft refinery. The revised conversion ratios are mostly configurable, and the defaults (and how they were derived) are available for your convenience. Expect to be able to set the amount of UU used by a group of conversions in the final 0.7.11 (the only reason you can't now is because I didn't think of it until just this moment).
Another thing added in the experimental version is electrolyzed water as a liquid. That's right, you can now store your EUs in liquid form. There's also a liquid electrolyzer machine that doesn't have a GUI yet, nor does it actually operate, but is included so you can see what it's going to look like. I really need a texture for the electrolyzer front, possibly more than one texture for different operational states (electrolyzing, idle, de-electrolyzing).
Something to test: play with the wrench on the liquid electrolyzer, and try to make it turn in such a way that the faces don't quite follow your wrench. This shouldn't be possible, and I haven't been able to manage it, but if lots of us try, someone might find the way (and tell me how they did it).
There's also a configuration change: the config key "accelerator" in the block section has been replaced with a key named "machine". When LiquidUU reads a config with the old key present, it should mark it as obsolete -- please make sure that happens. Note that LiquidUU will not remove the obsolete key from your configuration, it'll just ignore it when the new key is present. This should provide maximum backwards compatibility, but if something goes wrong, I'll want to know what happened.
Not a proper release yet, but it's getting there.