Thanks Massimo, I was not aware of that! For anyone else who might use
this, note that you must provide the fully-qualified class names instead
of the simple names (com.foo.MyModule, instead of MyModule).
chris
Massimo Lusetti wrote:
On Sat, Feb 23, 2008 at 9:38 AM, Chris Lewis <[EMAIL PROTEC
On Sat, Feb 23, 2008 at 9:38 AM, Chris Lewis <[EMAIL PROTECTED]> wrote:
> List,
>
> I'm working on a multi-module project in Eclipse. One of the modules is
> a T5 web app, while the others are components and services for T5. The
> generated artifacts are drop-in modules for T5, meaning they con
List,
I'm working on a multi-module project in Eclipse. One of the modules is
a T5 web app, while the others are components and services for T5. The
generated artifacts are drop-in modules for T5, meaning they contain a
Tapestry-Module-Classes header in their jar manifest.
Now my problem is
