Although walking into Starbucks and ordering a half-caf double-decaf
grande Lombok (with a twist of lemon) doesn't quite sound the same. :)
On Aug 24, 10:25 am, DJ wrote:
> Just heard episode 274, since Dick was wondering where Lombok name
> came from, here is the answer:
>
> Lombok is an island
Just heard episode 274, since Dick was wondering where Lombok name
came from, here is the answer:
Lombok is an island in Indonesia, located east of Bali.
On google map link below you can see Java, Bali, and Lombok next to
each other.
http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=lo
On Aug 23, 11:39 am, Reinier Zwitserloot wrote:
> A full and exhaustive treatise doesn't exist, but there are a few
> rules almost everyone can agree with, and yet these rules are not
> followed by the JDK, probably because we didn't know any better back
> then. i.e.:
> [...]
Thanks for the comp
Dom - you might be able to get this from edelivery.oracle.com, it depends on
how old a version you need. For older versions you'll have to go via Oracle
Support (metalink.oracle.com)
The Oracle Technology Network site only shows the last couple of versions
generally.
Duncan
On Fri, Aug 21, 2009
Thank you Dom I will try upgrading maven.
I will also try the list you have suggested. I had already asked on
the list for the plugin itself and did not get a response. I also
noticed where others who described the same or very similar problems
were not answered. This made me think there's eit
On Aug 23, 12:52 am, Martin Wildam wrote:
>
> In reality programmers could live without exceptions for many, many
> years. ;-)
We all coded assembly too. You're flipping the argument around now,
Martin: Just because something is old, it's true.
That's just as logically invalid as 'Something is
On Aug 23, 12:36 am, Martin Wildam wrote:
>
> The question is: How really to use them right? I think this is a
> desired result of this discussion. :-]
>
A full and exhaustive treatise doesn't exist, but there are a few
rules almost everyone can agree with, and yet these rules are not
followed b
It's not out of band, Peter - this stuff happens, in real life, even
if you never explicitly accepted the burden of responsibility by e.g.
using @SneakyThrows. Just mixing class files compiled against
different versions of the same code base is enough to get there. Thus,
you *CANNOT* just swallow
