On 1-Feb-09, at 8:34 AM, Mohan KR wrote:
I have a couple of questions, given the roadmap:
- Till now the recommendation from us has been to use the
“installation” that will be used for the
production builds (which is 2.0.9). So the selected installation is
always the “external”. I hope this
is kept an option.
It will always be an option. There's no reason to take it away. We
will always leave so that you will have a surefire way to know that
you're doing exactly the same thing on the command line. You may want
to use an external installation for any number of reasons.
- Regardless of the above settings, the embedder would always
be used for runtime dependency
resolution?
Yes.
Can someone elaborate on the workflow when an external Maven is
selected as the
default installation and the interaction with embedder?
The classpath created for execution is made up from the external
installation. Dependency resolution is done with the embedder. We try
to make the embedder obey all the same settings so that it's as
consistent as possible.
Thanks,
mohan kr
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
