Thanks for the info. I'm not sure what the problem was, but upgrading fixed
it.
On Feb 4, 2008 9:38 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Yep, only the jar is created with Java 5, but that doesn't affect
> the usability with older Java versions.
> (this is done because of Maven's ina
Yep, only the jar is created with Java 5, but that doesn't affect
the usability with older Java versions.
(this is done because of Maven's inability to not modify jars when they have
been generated and signed already)
Martijn
On 2/4/08, Frank Bille <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm not e
Hi,
I'm not entirely sure what you mean. All the jdk-1.4 projects is compiled
with 1.4 for the releases.
Frank
On Feb 4, 2008 4:05 PM, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm getting a number of "class not valid" errors when my IDE is trying to
> autocomplete imports. Typically
Looks like both 1.3.0 and 1.3.1 were both built with Java 5. Not sure what
the problem was, but upgrading to 1.3.1 fixed it.
On Feb 4, 2008 9:05 AM, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm getting a number of "class not valid" errors when my IDE is trying to
> autocomplete import
Hi,
I'm getting a number of "class not valid" errors when my IDE is trying to
autocomplete imports. Typically this error occurs when I encounter JARs
compiled with Java 6, while I'm on Java 5. Can the JARs be compiled with
Java 5, or can multiple versions be made available? Thanks.
-Nick
