Hi Chris,
The current releases (with the exception of a limited number of
reporting plugins) work with the RC and have been tested via the
integration tests.
Likewise, you can build from SVN if you wish for one or all plugins,
however we're highly recommending those not working on development of
Hi John,
I guess what's problematic is that many of us have been working from the
HEAD of SVN so that we could workaround this or that bug. So now that we
have a release candidate (RC) -- it is only a portion of the picture (no
plugins are provided). So do we stick with our current SNAPSHOT
plugins
On 10/18/05, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> Isn't that basically the same as using antrun? That's how we've been
> using it in the meantime to call jdo enhancers and testNg.
not really. Using antrun you put this knowledge in the POM and the build
script is a part of the specific proj
Isn't that basically the same as using antrun? That's how we've been
using it in the meantime to call jdo enhancers and testNg.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 18, 2005 12:42 PM
To: Maven Users List
Subject: Re: [m2]
I hadn't - thanks.
I'm not sure this adds a great deal over using the Ant API itself
though. However, what John is referring to is to making Ant a plugin
language for Maven (so not Jelly or Marmalade, just plain ant scripts
where a target can be used as a goal and the plugin configuration is
fed v
On 10/19/05, John Casey <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not sure about the antRun plugin specifically...the work I've been
> doing lately is for lower-level support of Ant as a native mojo
> language, rather than for referencing Ant scripts in th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
One point of confusion which comes from our development approach up to
recently is the release cycle for plugins vs. that of the core. Going
forward, plugins will each have their own release cycle, which is not
meshed (except roughly) with releas
Hi Brett,
I'm confused.
1) I'm pretty certain that some plugins have changed -- specifically the
antcall plugin.
2) When I build the HEAD from SVN (using the m2-bootstrap script) -- I get
all new plugins built and installed in my local repo (stamped at the current
SNAPSHOT). So when you build RC,
There are no specific plugins for the RC, we just missed an
incompatibility between versions with resources and site.
Upgrading to the RC fixes issues with the resources plugin, but breaks
certain reports. These will be corrected shortly.
- Brett
On 10/17/05, Chris Berry <[EMAIL PROTECTED]> wrot
Greetings;
Are new plugins available for m2 RC?? If I understand things, I would think
that they might be made available??
I.e. When building m2 from SVN one gets a new set of base plugins
constructed (e.g. 2.0-beta-3-SNAPSHOT)
But with the RC release-- which is distributed as JARs -- the correspon
10 matches
Mail list logo