Re: suggestion refactor SCM
On 9/27/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: Jose Alberto Fernandez a écrit : I think that it will be a very good idea, mostly as a stepping stone to higher level functionality. The main reason for not having such a thing is the fact that each project knows in advance what kind of repository is being in used. So why do we need something abstract? On the other hand, once you have such an abstracted functionality, I am sure we could envision higher level tasks stored on other antlibs that may provide project management style functionality irrespective of the underlying repository. That would be a very good thing to have. So I am all for it. The question is what are the concepts that can be ported across all different SCMs? In Maven-SCM, we have some abstract beans for each commands (checkout, checkin, update, changelog...) in an abstract api, Each provider implement these beans for obtain an accessible command in framework for this provider. We support actually clearcase, cvs, local, perforce, starteam and in few weeks, Serena Dimension (PVCS). For your information, I am about to propose CruiseControl to reuse this library. We currently support 14 SCM, but most of the time only the changelog functionality is supported. Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Reusable ant tasks, a Java Command Line Interface library?
Hi all, Something is needed to ease the running of command line programs in Java. Several issues appear when using the official SDK Runtime#exec() and Process: multiple exec() method to chose from, quotes handling, lack of shell, no timeout management, input/output management Ant first solved the problem by creating a Commandline class some years ago and a couple of helper classes to provide more functionality on top of Runtime.exec(). These classes have been copied and sligthty forked in several projects including plexus, maven2, cruisecontrol. To me that clearly denotates its usefulness. So why not putting these classes available in a standalone library? Note: this is similar to the general idea Vincent Massol had ([1]) on reusable ant tasks, with a focus on command line and process execution. As it is not practical to discuss this accross several mailing lists, I wrote a proposal on my blog (http://www.coffeebreaks.org/blogs/?p=8). If you want to help, please send me a mail or better write a comment on the blog entry. If there are enough interest, I will create a dedicated list. Cheers, Jerome [1] http://blogs.codehaus.org/people/vmassol/archives/think_tank.html#001036_id_love_reusable_ant_tasks
Re: Google Summer of Code, Apache ANT project ideas?
On 6/3/05, Erik Hatcher [EMAIL PROTECTED] wrote: Doug - glad you're interested in the SoC. One idea that would be tremendously helpful to Ant would be to revamp the documentation system such that task/type documentation is auto- generated. I started the proposal/xdocs project several years ago, but it never caught on. I'm not sure where it stands currently in terms of documentation generation. Hehe. [Shameless plug] If someone wants to address a somewhat reusable xdoclet documentation tool, the cruisecontrol project is probably also interested. The current doc is nice: http://cruisecontrol.sourceforge.net/main/configxml.html but manually generated. See http://jira.public.thoughtworks.org/browse/CC-202 I'm swamped, but would be your mentor on such an effort if no other Ant committer was set on doing so. :) J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
