On Fri, 14 Jul 2000, you wrote:
> #1. import a "fresh" copy of turbine into CVS. call the module
> "turbine.new". i'm totally +1 for that.
First I want to clean it out before I import it.
I plan on removing ALL sample code.
What about the incomplete Admin stuff? My thought was to
move it out of the core into a separate directory. So it can be worked on
but it's not automatically in the turbine.jar. Then once it's finished, it
can just be added in the modules.pacakages path.
Any suggestions on what else should be removed?
> #3. for the TDK, I think that it should be in CVS, but in its own module
> (ie: "tdk"). It should take snapshots of the turbine.jar file that is built
> from the "turbine" module and save them in the tdk/lib/ directory.
Yes. This is exactly what I want to do.
> #4. you should not include all the needed .jar files into one .jar file. i
> promise that will cause problems. the needed .jar files should go into a lib
> directory only. duplication here is ok, disk space is cheap.
I'll heed to your wisdom. :-)
> #5. the TDK should be able to build itself out of an Ant.xml file.
Yes. Ok
Sorry for all the questions, just want to do it right!
--
dave
[EMAIL PROTECTED]
----------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
