Hi,
I'm working on the TDK, and I wanted to ask what the
simplest allowable directory structure & corresponding
module.packages definition would be.
I have periapt.com so I have successfully used:
module.packages=com.periapt.modules
WEB-INF/classes/com/periapt/modules/screens
WEB-INF/classes/com/periapt/modules/layouts
WEB-INF/classes/com/periapt/modules/navigations
But I find this a little cumbersome.
I was wondering if it is possible to simply have:
module.packages=. (or something, can't get it to work)
WEB-INF/classes/screens
WEB-INF/classes/layouts
WEB-INF/classes/navigations
I can't seem to get this to work. I figure if it's a
webapp and running with it's own classpath, then
you can leave the package directive out because
there's not going to be many name collisions if
it's living by itself (if I'm wrong please correct me).
But do {screens,layouts,navigations} have to be in
a package in order to be found?
Or if you actually need a package then how about this:
module.packages=modules
WEB-INF/classes/modules/screens
WEB-INF/classes/modules/layouts
WEB-INF/classes/modules/navigations
Again, I want what is simplest. But if a FQDN is
a requirement then I'll glean the FQDN from a
properties file and build a directory structure
for a webapp that reflects this requirement.
Is there already a standard way to do this?
It would be nice to have a standard way to build
a turbine app, then this can be reflected in the
TDK, and I'll document the process.
jvz
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
