On Tue, 17 Feb 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
Ought we create a generic 'output' tag?
+1
not because of the license as much as for non-Java projects.
<output type="jar"/> instead of <jar>, <output type="license"/>, <output type="text"/> for generic outputs like README, <output type=".net-assembly"/>, <output type="shared-library"/> ...
+1 from here too
Don't forget that we also can do:
<output type="dir" name="Junit Report"/> <output type="dir" name="Javadoc Report"/> <output type="dir" name="Project site"/>
so that we can also publish whole directories.
I will need it for ForrestDoc (which i snow failing due to interruption of the process that takes too long)
Note that I would also like to have something like:
<build type="ant|maven|shell">
<param name="" value=""/>
</build >(This can also bring us near the possibility of having build plugins)
Finally it would not be bad to also have:
<input type="java/plain"/> <input type="test/junit"/> <input type="xml/forrest"/>
but that will maybe come later.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
