Milos Kleint wrote:
check the toolchains proposal that is supposed to address this issue.
http://docs.codehaus.org/display/MAVEN/Toolchains
The way the toolchain proposal chooses is somewhat doable with Maven
right now: define a set of VM specific properties in each developers'
settings.xml and use that in the config of the various plugins.
What I don't like about the appraoch is that one has to hand-maintain
the properties/toolchain.xml still. If I update my JDK, I still have to
remember updating the settings or the build will break.
The great benefit of the toolchain approach is that it provides a
standard definition of the JDK and that could also abstract from some
platform specific difficulties (rt.jar on linux/win vs classes.jar on Mac).
Still, I don't like the way how I have to manually distribute the path
to the current JDK into various config files.
-dirk
Milos Kleint
On Sun, Mar 30, 2008 at 7:58 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
On 3/30/08, delbd <[EMAIL PROTECTED]> wrote:
> Yeah, that's what i thought. So we can consider that maven is missing
> one important thing in dependency management: the jvm dependency. I
Check JIRA, and if its not already posted, file it. Perhaps it can be
incorporated in 2.1. Or, perhaps there's already a way to do it that I
haven't considered...
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
