I have just found the solution : -Dtapestry.modules=com.cariboonetworks.mylib1.services.Lib1Module,com.cariboonetworks.mylib2.services.Lib2Module, ... in the VM parameters of the JettyLauncher configuration did the trick.
So, after several days of development environment frustrations, it seems that i get my configuration back and ready to work ... And i'm sure, after the exchanges i had here and the searches i made on google that i'm not the only one who get frustrated with this. I think that it would be very negative for the tapestry framework if new developers fall in thoses traps even before seeing the great possibilities of tapestry and i think that a kind of tutorial or check list to get ready with the major developement environment (eclipse, netbeans, idea, ...) would be a very valuable tool for all the tapestry beginners and the others ... A JIRA request as already been filled 2 months ago for this and i think we should vote for it. Stephane Stephane Decleire a écrit : > Oups, no, it wasn't ... > Strange since i have checked this yesterday ... > > So, with "build automatically" checked, here is what i get : > > 1. If i launch my tapestry application in eclipse using "Debug as / > Maven Build ..." and start jetty:run", dependencies are correctly added > to the project but each change in a tml or java file restart the whole > jetty process ! It is not as long as tomcat but it is not what is > expected from tapestry reload feature ... > > 2. If i launch my tapestry application in the jetty launcher, the reload > process is ok, but i am faced with a dependency problem : in the pom > file of each of my libraries, i use a maven plugin like that : > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-jar-plugin</artifactId> > <configuration> > <archive> > <manifestEntries> > > <Tapestry-Module-Classes>com.cariboonetworks.myproject.services.AppModule</Tapestry-Module-Classes> > </manifestEntries> > </archive> > </configuration> > </plugin> > > so the AppModule classes of my libraries are no more "loaded" when my > app is launched with the JettyLauncher. Is there a way to tell those > manifest entries to the JettyLauncher ? > > Stephane > > Stephane Decleire a écrit : > >> Yes i do >> >> Jonathan Barker a écrit : >> >> >>> Do you have Build Automatically selected in Eclipse? >>> >>> >>> >>> >>>> -----Original Message----- >>>> From: Stephane Decleire [mailto:[EMAIL PROTECTED] >>>> Sent: Sunday, December 07, 2008 18:59 >>>> To: Tapestry users >>>> Subject: Re: [T5] Tapestry + Maven make me crazy !!! >>>> >>>> I've installed the last sonatype's m2eclipse and my app is launched >>>> without dependencies errors but neither tml modifications nor java >>>> modifications are automatically reloaded when i right click my project, >>>> select "Debug as / Maven Build ..." and start jetty:run from there ... >>>> >>>> Thiago H. de Paula Figueiredo a écrit : >>>> >>>> >>>> >>>>> Em Sun, 07 Dec 2008 19:53:28 -0300, Jonathan Barker >>>>> <[EMAIL PROTECTED]> escreveu: >>>>> >>>>> >>>>> >>>>> >>>>>> Second, if you upgraded from the old, rather limited m2eclipse plugin >>>>>> to the latest and greatest, it will break the old JettyLauncher >>>>>> plugin. Been >>>>>> there, broke that. >>>>>> >>>>>> >>>>>> >>>>> Sonatype's m2eclipse (the newer ones) works flawlessly with >>>>> JettyLauncher here. >>>>> >>>>> >>>>> >>>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> > >
