When Java 7 was released last week, Lucene and Solr both issued a warning saying that you can't use Java 7 with Lucene or Solr. These are popular text search libraries (and Solr is an app) so this can be pretty severe, and the way the community was informed at first was pretty emotional. See Java 7 paralyses Lucene and Solr for an example of the kind of headline generated.
The actual warnings on the Apache sites are pretty mild and state the problem although not the history of the problem well, and give an expectation of when you'll be able to use Lucene with Java 7.
Some people have written some pretty good responses to the issue, see Don't Use Java 7? Are you kidding me? for one example.
These do a good job of hiding the emotions from the problem; in mailing lists and other forums, the word is that Java 7 is buggy, that Oracle's ignoring the problem (they're not, they are working on the bug and have a fix scheduled) and that Oracle didn't test enough.
I say that's crap. Sure, it'd be nice if Oracle never released a JVM with bugs, but it's silly to blame them for this.
There's enough blame for everyone, for Lucene and Oracle.
Oracle honestly did the right thing, though. They had some optimizations in Java 6 (-XX:+OptimizeStringConcat and -XX:+AggressiveOpts) that could break some code, like all things can. With Java 7, they made the optimizations on by default, starting a month before Java 7's release.
you could say that Oracle should have held off. But why? Eventually you have to release stuff, because otherwise people won't test it, and you'll never know if it works or not. At some point you have to let stuff go to see if it works, and here it didn't. They're working on a fix, which is good.
But what about Lucene's fault here? They screwed up, too. They decided at the last minute to try Java 7 with Lucene and Solr and found out it didn't work. Boo hoo. That's way to late. It's not like Java 7 was sneaking up on anyone, Oracle's been doing webinars and presentations and press releases alot lately to get the word out to whoever's living under a rock and didn't know.
So Lucene should have said hey this thing's coming, maybe we should try it. And when these geniuses did, it was too late to turn back without giving java 7 a huge black eye, which nobody needs. And they weren't testing well even then - they apparently had a bug because their tests relied on the specific order of tests being run, which means they didn't follow the rules about either setting order without fail (which Testng can do and is part of why everyone should use testng instead of junit) or isolating tests completely (which is the best junit can do, because it's still way behind testng in features. But it's the "standard.)
So what did Lucene do? They gave java 7 a black eye anyway, by letting people get upset about it.
They should just shut up.