CruiseControl-Antlet Thoughts (before:Re: Webapp-Antlet: First version)

Hi Michael,

So my thoughts about the cruisecontrol-antlet are very simple:

1) We should have two targets (masterbuild, cleanbuild) in the cc-antlet 
using the other antlets: clean, checkout, checkstyle, compile, jdepend, 
test, doc, dist
(Maybe the checkout will rely to cruisecontrol-antlet)

2) I think the antlet can also produce the config.xml for cruisecontrol, 
because it isn't so difficult. I think with a template and the 
ant-replacing function this is reachable.

3) Interesting is thing how to get the process run and how to configure 
your project in: There I have no good ideas at the moment, but a few 
thoughts. I have implemented some time ago a cc-listener for tomcat over 
JMX. Maybe JMX is one possibility.
I am a little stuck with this thought, because of the 
multiproject-functionality in cruisecontrol. I think it is useful so on 
this hand you have to put your config into cc manually.

You got any ideas on it?

Micha


Michael Homeijer wrote:
> ----- Original Message ----- 
> From: "Michael Kloss" <[email protected]>
> To: <[email protected]>
> Sent: Monday, February 16, 2004 9:12 PM
> Subject: Re: Webapp-Antlet: First version
> 
> 
> 
>>Hi,
>>
>>
>>>- I think it should be called "webapp".
>>
>>Fine
>>
>>
>>>- I think all irrelevant files should should be left out (eg.
> 
> status.xml).
> 
>>Jap, this is no big deal
>>
>>
>>>- The hard part is probably filling the lib dir with jars from ruper
> 
> (from
> 
>>>dependencies in module.xml), but that can be left out until
>>>ruper/dependencies are working.
>>
>>That's true. But there's a common ground with the java antlet (building
>>the dist), so I think we can implement this feature nearly the same.
>>
>>
>>>It seems right to create small initial versions and leave
> 
> standardisation of
> 
>>>build directories, generated doc directories,  lib dir construction,
>>>documentation etc. until there's a small collection of working antlets.
>>
>>What do you mean by this exactly? The current Structure of the Template?
> 
> 
> I haven't looked at the template yet. The antlets I have migrated only do
> the neccessary stuff, I have left everything else out. My guess is that
> before we have the downloads of antlets and their jars/libs completely
> working, all builds/module descriptions for all available antlets will have
> to be refactored. In that case you'd like to have as little code as possible
> to refactor.
> 
> After that we can add documentation, standardize antlet setup, builds etc.
> 
> I am happy to see that what's left is pretty much straightforward ant.
> 
> Hope this makes any sense.
> 
> I'd be happy to commit the webapp antlet for you.
> Furthermore I'd very much like to hear your thought on the tasks the
> cruisecontrol antlet should perform.
> 
> Michael
> 
> 
>>Regards
>>
>>Micha
>>
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>>Build and deploy apps & Web services for Linux with
>>a free DVD software kit from IBM. Click Now!
>>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
>>_______________________________________________
>>Krysalis-developers mailing list
>>[email protected]
>>https://lists.sourceforge.net/lists/listinfo/krysalis-developers
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click