Yeah, this is definitely an example of that use case. I was just
thinking that this concept had a more special meaning within Maven as
you can do special things with a JDK - if you give the location, you can
derive some of the other parameters like the location from it.
With plugin configurati
This might seem trivial in comparison, and is most likely orthogonal to this
discussion, but what about the concept of applying the same set of plugin
configurations to all of the applicable plugins in a build? When we
discussed this earlier (informally), I thought this was a central concern to
be
On 7/17/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks Nathan. This is exactly what I was getting at (and the reasons
for it), but this is a lot more detail than what I wrote down.
So, just to make sure I understand, it would work something like this:
- JDK definitions are built in, and spec
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
>
> Some things to note about targeting a different JDK:
> * rt.jar is not enough - JDKs provide a number of other classes in extra
> libraries, and it isn't called rt.jar on some platforms.
In fact, this actually va
Thanks Nathan. This is exactly what I was getting at (and the reasons
for it), but this is a lot more detail than what I wrote down.
So, just to make sure I understand, it would work something like this:
- JDK definitions are built in, and specify the location of executables,
a particular type
I would strongly favor this approach as it has fixed issues with our
projects where we now just specify the execution environment to be java 1.4and
5.0 and individuals can use different maintenance versions of Sun's java 5
jdk as well as some of the diagnostics in BEA's jrockit 5.0 jdk without
cha
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
>
> Some things to note about targeting a different JDK:
> * rt.jar is not enough - JDKs provide a number of other classes in extra
> libraries, and it isn't called rt.jar on some platforms.
In fact, this actually vari
When I raised the Java 5 thing, I mentioned needing toolchain support,
but probably wasn't clear about what I meant given all the responses
about target environments, -source and -target not being enough, and so on.
It's probably worth sharing what I was thinking of here for Maven 2.1,
regardless
