I think this is a very useful proposal...particularly for supporting use
cases around runtime construction/modification of model (Wendell's
comments).
But is there any scoping mechanism in plexus and/or maven? Or would the
shared context always be 'global' for all of maven + plugins?
I'm of
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
So m2eclipse *does* depend upon the Maven embedder currently...and at
the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in
Hi Tom,
Tom Huybrechts wrote:
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy
Hi Fabrizio,
Fabrizio Giustina wrote:
On 12/11/06, Scott Lewis <[EMAIL PROTECTED]> wrote:
There is a (recently proposed/adopted) version numbering spec that
describes using the qualifier segment to distinguish between release,
integration, and nightly builds. See here for the details:
Hi Fabrizio,
A small clarification below
Fabrizio Giustina wrote:
Hi Graham
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the
repository, is in theory all that would be needed to make eclipse jars
automatically avai
