jstrachan 2002/06/11 03:29:35
Modified: xdocs/ref new-design-musings.xml
Log:
added link to example mediator
Revision Changes Path
1.2 +4 -1 jakarta-turbine-maven/xdocs/ref/new-design-musings.xml
Index: new-design-musings.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/ref/new-design-musings.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- new-design-musings.xml 11 Jun 2002 10:13:54 -0000 1.1
+++ new-design-musings.xml 11 Jun 2002 10:29:35 -0000 1.2
@@ -60,13 +60,16 @@
<ul>
<li>one or more build targets, which may have their own dependent
targets</li>
<li>one or more Ant Tasks or maven beans</li>
- <li>some glue to populate the tasks/beans with information from user
defined properties files or POM values</li>
+ <li>some <i>mediator</i> glue to populate the tasks/beans with
information from user defined properties files or POM values</li>
</ul>
<p>
Now the first 2 items are trivial. The last one seems a bit
controversial.
I personally prefer an Ant-like XML script to define the Maven
targets, then folks can reuse existing
knowledge in scripting build related tasks (property, javac, java,
javadoc, junit etc). Though this could
also be done in Java code too.
+ </p>
+ <p>
+ There's an example of how this <i>meditator</i> glue could look in
Jelly in src/bin/mediator.jelly.
</p>
<p>
Current proposal: use Java code or Jelly script depending on the
developers religion ;-). Both can
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
