[EMAIL PROTECTED] (Jeffrey D. Brekke) writes:
>epugh <[EMAIL PROTECTED]> writes:
>Eric & Slava,
>There is a webtest plugin for Maven in the sourceforge Maven Plugins
>project. We used to write straight junit based acceptance tests using
Hi,
while this is a cool thing, I really want to avoid some large "you
must get this plugin, this plugin and this plugin and that plugin from
CVS-HEAD" scenario to build the Turbine code. The fact that maven b10
seems to be able to build our site without any trickery, jar-copying
or stuff is very reassuring to me.
If your plugin is available through some maven-ibiblio magic, then
cool, lets go ahead and test it. If a Turbine user must download it
from somewhere on the net, integrate it into maven so that he won't
get build errors, then I would veto its usage in the normal turbine
build process.
If we want to attract users to Turbine, we must make it possible to
rebuild the code and work with the code without a large entry
barrier. I fully intend to add some sort of "build Turbine with
Eclipse cookbook", because using an IDE is a real option for many of
our users.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
