(Chris)
Pleased to see fellow users steering Maven more in the direction of
ant and I have a few questions about this new plugin.
1. I'm concerned that I have to write java code in order to call ant
tasks. For example to support the tomcat task, would I or somebody
else have to have extended the antfile plugin?
2. Is this a stop gap plugin until John 'persuades' ;) his client to
let him reuse some wrapper archetecture to dynamically create ant
property delegates - or does it achieve something slightly different?
3. Are you talking about invoking isolated ant tasks or whole ant
build files or both? Are you suggesting that ant basically becomes
another plugin language encapsulated in its own build file - could be
very useful.
I'd definitely welcome the option to embed ant tasks directly within
a pom, preserving the exact same ant syntax, like I think antrun does
- only benefiting from automatic maven properties and invoked in the
same jvm as discussed a while ago.
AW
On 15 Sep 2005, at 15:11, John Casey wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris,
Thanks for your contribution. I've been using little pieces of it in
other stuff lately, but haven't had time to really get into
integrating
this into the M2 core yet. Would you be willing to file a JIRA
issue for
adding Ant the antfile plugin to the mix? I've been sort of putting it
off, because I want to integrate Ant support in the same was that
beanshell is integrated, for example.
At this point, we're so heads down on getting to m2-final, that we
need
a central point of reference for any outstanding issues. Therefore,
for
better or worse, it'll be really hard to get any functionality not
listed in JIRA into the m2 release. From personal experience, I can
see
that anything not in JIRA stands a decent chance of simply drowning in
the noise.
Thanks,
John
Chris Berry wrote:
| Greetings,
| There was a recent thread on "whether to use ant". It is a long
thread
| (19+ posts) and became divergent. So rather than bury that post
there,
| I will raise it here to the top level. Like people in that thread, I
| firmly believe that a happy marriage between Maven and Ant is in the
| best interest of all.
|
| When maven began it was really intended to be an easy way to
share Ant
| build scripts. We were all tired of reinventing the wheel. Every
time
| we started a new Ant project we had to copy in and customize a
set of
| Ant build scripts. With every new Ant project, we violated the
Don't
| Repeat Yourself" principle. Enhancements/bug fixes had to be hand
| propagated across projects.
|
| Over time, maven became more than this. It added Good Stuff like the
| POM (a holistic "recipe" for the project) and dependency management.
| It added Bad Stuff, like Jelly. That's all water under the bridge.
|
| IMO, maven should emphatically refrain from reinventing the
wheel. Ant
| is the defacto Java build tool, although it is in no way limited to
| Java. Ant already does ~90+% of the individual Tasks required by a
| build system. And what it doesn't do is typically provided by others
| wishing to either augment Ant's deficiencies (e.g. ant-contrib) or
| wishing to have their tools adopted (e.g. axis-ant). Ant is
| cross-platform, and is intended as a build tool -- not as a general
| scripting language. Ant's original intent was simply to be a "better
| make".
|
| Maven should concentrate on being the "glue" that holds it all
| together -- providing value in reusability, repeatability, and
| holistic project management.
|
| To this end, I have written an Antfile Plugin. It extends the AntRun
| plugin, and simply allows you to delegate to an Ant buildfile. The
| buildfile is rolled into the plugin jar, and then, is unzipped from
| that jar into the /target and is run during the build.
|
| One simply extends the AntFile plugin with their own plugin,
declaring
| the buildfile, pulling config info from the POM and passing them
on as
| properties to Ant. It's very simple to use.
|
| (BTW: I have built an Axis plugin on top of this, validating it's
usage pattern)
|
| I passed my AntRun plugin to John Casey (one of the Maven gurus),
and
| I hope that The Powers That Be will allow it into the HEAD of the
SVN
| tree.
|
| Cheers,
| -- Chris
|
|
---------------------------------------------------------------------
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDKYEWK3h2CZwO/4URAt2hAJ9nyagGeok+IjiJTt5m2Gyyxb3iBACfbG06
MVTNja/5c7hnYd18vRD6cV0=
=6dzQ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
