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 specify the location of executables,
a particular type of bootclasspath, and anything else that might need to
be referenced.
- a number of JDKs are preconfigured to "implement" those definitions
- the mechanism is extensible so that new JDKs with different layouts
can be added (we can do this in the same way new wagons are added using
Plexus)
- the user would only have to do minimal configuration (a list of
available JDK paths is probably enough, and we can autodiscover these if
not setup, either using JAVA_HOME, PATH or a full path search if we
really wanted to)
This sounds great. We should probably look into reusing/aligning to what
Eclipse does here if we can, too.
The only thing to keep in mind is that while I think this is primarily
for Java target environments now, I think the same technique can be used
for other target environments (.NET/Mono, native stuff, etc).
Cheers,
Brett
This is very interesting stuff.
Now will this be a part of maven itself, or will it be something
slightly external (like scm, lxr, ..)?
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
