https://opennlp.apache.org/ http://nlp.stanford.edu/
Cloud provider automation libraries
http://jclouds.incubator.apache.org/
Distributed stream computing
https://incubator.apache.org/s4/
Asynchronous event driven IO, battle tested, mother recommended
In-process webserver
....to name a few. It's probably useful to take some thing that you'll need and look in ecosystem X for it (say... .NET) and then compare what's available there to what's available on the JVM. In my experience, the JVM wins out almost every time when it comes to number of options and maturity of options.
"Leverage proven techniques and technologies"? What does that even mean?
Leverage = take advantage of
Proven = demonstrated to have worked
Techniques = using one approach versus another
Technologies = existing code
Buzzword bingo does not add value. It only obscures meaning. Of course your code works. Of course you use existing technologies. That work. In existing code. That you leveraged. Using techniques. And technologies.
Jesus, I hate this kind of language.
He was saying many other people have contributed java libraries his programs can use, so that he doesn't have to hire an expert in HTTP, or computational geometry, or many problem domains that aren't the direct concern of his application, yet are necessary for it to work.
He said it in a compact way. It's a form of compression.
(ii) Never use a long word where a short one will do.
(iii) If it is possible to cut a word out, always cut it out.
(iv) Never use the passive where you can use the active.
(v) Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
(vi) Break any of these rules sooner than say anything outright barbarous.
Having said that, I really liked the Google Guava library, although a good bit of that stuff is working around or solving problems with Java itself.