Agreed, but OTOH, with 2.2 requiring 1.5, this could give the push for
better support of a separation between Maven runtime and JDK being
used for the build.
Jochen
On Thu, Apr 30, 2009 at 5:23 AM, John Casey wrote:
> I just had a disquieting thought:
>
> Assuming we require JDK 1.5 for Maven 2
I still build java 1.3 projects (Websphere 5.0.2) with a JDK6_u13.
I' use the maven-compiler parameter to point on a Java1.3
JRE rt.jar, to avoid reference to unsupported classes/mehod. This is the
simplier/safer way AFAIK. Users only have to define a property
in settings.xml (and have a Java1.3
I think this is the same as those on 1.3 now... you set source and
target and either use animal sniffer, or you go through the bigger
configuration step of an external JDK (using the current config
options available).
Getting toolchains support in the plugins out would certainly be a
good
On Wed, Apr 29, 2009 at 8:23 PM, John Casey wrote:
> Assuming we require JDK 1.5 for Maven 2.2.0, I don't know how to tell users
> to build projects that require JDK 1.4, using a JDK 1.4 compiler. From what
> I've been able to find, the toolchains stuff isn't used by any released
> plugin version
I just had a disquieting thought:
Assuming we require JDK 1.5 for Maven 2.2.0, I don't know how to tell
users to build projects that require JDK 1.4, using a JDK 1.4 compiler.
From what I've been able to find, the toolchains stuff isn't used by
any released plugin versions, which means we'd ha
