On Wed, Aug 5, 2015 at 4:12 PM, Stephen Nutbrown <steves...@gmail.com>
wrote:
> Seems to be working for me too! Thanks.
> The only issue I am having is that my code for hibernate doesn't seem to
> work quite as expexted. Ideally, this should be picked up from the happylib
> public static void
> contributeHibernateEntityPackageManager(Configuration<String>
> configuration) {
> configuration.add("com.my.package.myentities");
> }
> However I am finding it only seems to work for me if it's in the main
> projects AppModule.java, perhaps I have configured something wrong, or
> perhaps this has to be in app module rather than in my shared jar?
>
I suspect the HappyModule configuration isn't read at all. That's because
you don't have a manifest when you are reading the classes directly from
the the target path rather than from a jar. Often, you need to explicitly
specify @SubModule(HappyModule.class) (or @ImportModule in T5.4) in your
AppModule when you are developing multiple libraries at the same time (or,
doing integration testing of your modules).
Kalle
> I've put the hibernate entities that are shared between the projects in
> there and so ideally the code should be in the shared library rather than
> duplicated in both webapps (although it works as it is... any ideas what
> may cause that?)
>
> Thanks,
> Steve
> On 5 Aug 2015 21:42, "Svein-Erik Løken" <sv...@jacilla.no> wrote:
>
> > WOW! Multi-module in Tapestry with Live Class Reloading is fantastic!
> > Thanks for pointing me in the right direction Thiago!
> >
> > To get live class reloading work for the common module in IntelliJ: Open
> > Project Structure, Project Settings > Modules. Select the common module >
> > Paths > Compiler output. Set Output path to the same path as the main
> > project output path.
> >
> > I have created a multi-module maven demo project for test and
> > documentation. A page in the main project includes a component-class from
> > the common module. I have demo of using assets (img and js-modules) and
> IoC
> > service. Everything works with Live Class Reloading.
> >
> > I am using a top-level pom (dependencyManagement, pluginManagement,
> > properties), a modules pom (maven-root), the main project (war), and the
> > common module (jar).
> >
> > The main project and common module is both created from mvn
> > -DarchetypeArtifactId=quickstart ..., with necessary modification.
> >
> > I have documented all steps to make everything working in IntelliJ
> (plugin
> > configuration etc).
> >
> >
> > >
> > > As long as the compiler target folder of the included
> > > library/module/subproject is included in the classpath of the main
> > > project, regardless of what tool you're using, live class reloading
> will
> > > work after a class in the library/module/subproject is recompiled.
> Maybe
> > > Eclipse makes it easier because it compiles automatically on save. I
> > don't
> > > know how IDEA handles this.
> > >
> > >
> > > --
> > > Thiago H. de Paula Figueiredo
> > > Tapestry, Java and Hibernate consultant and developer
> > > http://machina.com.br
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
