On Wed, 26 Sep 2001, Carsten Ziegeler wrote:
> Hi Team,
>
> the ant task "available" is not suitable for our needs. It does
> not only test the specified path for a given class, but also
> the classpath set by the user/jvm.
> Our "available" test should only check the jars in the ./lib
> directory.
>
> I wrote a simple ant task which does exactly this, so please
> vote, if we should add this task and use it instead of the
> build-in task. Of course I am +1 on this :-)
+1
>
> The second decision is where the src and the class file for
> this task should be stored:
> I suggest:
> ./bin/anttasks: for the compiled class file
> ./bin/src : for the source
Sooner or later we will have to split the hole src tree up into
different parts like
./src/interfaces
./src/impl
./src/anttasks
./src/samples
etc. (just to throw some examples)
> I think we should separate this src from the cocoon src
> as it is only used by the build system.
+1 but org/apache/cocoon/anttask/... is separating as well, isn't it?
Giacomo
> Last think for this topic:
> Should we convert the simple sitemap tool to an ant task?
> I'm +1 on this!
>
> Your votes, comments etc are welcome.
>
>
> Carsten
>
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: [EMAIL PROTECTED]
> ================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
