What you are seeing is normal; when executing directly from the
workspace, there's no build step that creates the manifests that
Tapestry uses to autoload, thus you must use tapestry.modules JVM
property to manually load the modules.
On Fri, Mar 21, 2008 at 8:58 AM, raulmt <[EMAIL PROTECTED]> wrot
Thanks Howard, I follow your advice factoring out to a core-library so the
web-app and the other projects depend on that. But, despite the web-app does
not depends on the other projects, I put that dependency anyway so when I
package the web-app it includes the jars from the other projects in the
I would factor out the shared interfaces into a library-core that
could be inheritted by the app-core and by the add-on projects.
At runtime, T5 IoC will be able to knit together everything.
On Wed, Mar 19, 2008 at 2:41 PM, raulmt <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a core app and oth
