On Sun, Jul 16, 2000 at 12:38:42PM -0700, Jon Stevens wrote:
> on 7/16/2000 12:05 PM, "dave" <[EMAIL PROTECTED]> wrote:
>
> >> The admin package should live under the src tree with the rest of the
> >> source
> >> code.
> >
> > The main reason I moved it was to clean-out the core and remove any
> > incomplete code. The admin stuff is incomplete.
I'm pretty much ready to check in - I've been very hectic and not had
*any* time on my hands, but the stuff works - I just haven't finished
tweaking the look.
> The other problem is with separating out the issues of having a single
> turbine.jar file with the admin stuff in there. It could also be a security
> hole to have it there.
>
> I vote that the admin stuff should become its own project in turbine's CVS.
+1 - I'm up for this, no reason why a turbine "core" should have such
functionality built-in.
It would be nice to make it *very* easy to deploy the admin stuff into,
say, an installation of dave's TDK. In fact we could use the admin app
as a testbed to develop a consistent and simple Turbine app deployment
strategy (kind of like a WAR but for Turbine).
> ie:
>
> /products/cvs/turbine
> module: admin
Anyway shall I make this? I'll think about the structure and ask for
comments before doing anything (like dave with turbine.new)
Sean
--
Sean Legassick
[EMAIL PROTECTED]
homo sum: humani nihil a me alienum puto
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
