"Robles, Rogelio" <[EMAIL PROTECTED]> writes:
>> -----Original Message----- >> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] >> >> - some ant/maven tasks to copy an application into the servlet >> container for testing (tdk:install, tdk:clean, tdk:deploy) >> >> BTW: Internally I use "META" for this "new tdk": >> "Maven Environment for Turbine Applications" :-) >> >IMHO, I see Maven playing a key role in the future of the TDK, even it could >replace it with a plugin rich in old "TDK-like" goals and new ones. Jointly >with other Maven plugins it could provide the flexibility that everybody >needs or wants. What I mean is that the TDK could evolve in a Maven plugin. >This plugin will provide the Turbine component of the equation but Maven >will "join the dots" to other functionality already contained in Maven. I really like this idea (which is where I'd aim with "a new TDK") but you might consider two things: - many more people are right now more familiar with ant than with maven. And ant has a lot of stable releases. Maven is still beta level. - There seems to be a fundamental misunderstanding what the TDK is. To me, the TDK is: 1) A Servlet container environment, maybe even with a database engine 2) A preconfigured Turbine Servlet with property files 3) A tool chain to simply start working on Turbine apps 4) Docs and a sample application. A Maven plugin is simply a part of 3). [snipped the rest for further reading and ideas] 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
