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 configuration templating, I'm guessing you are just going to
be able to apply an arbitrary value consistently rather than derive
anything from it.
Does that sound right?
- Brett
On 18/07/2006 11:56 PM, John Casey wrote:
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 addressed by toolchain configuration.
Is it instead something that we should be capturing in a separate line on
the design wish list?
Specifically, I'm talking about the ability to specify source
includes/excludes, compiler configurations like -source and -target, and
other things to a set of plugins in a build from a single point of control
in the POM.
-john
On 7/17/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
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]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
