Hi Jakob, Well, I tried what you mentioned, and it now picks up changes to my .tml right away--definitely an improvement over before. I think I am seeing the same problem you are seeing, though, because it is not picking up changes to my page classes.
If I modify a page class and save in Eclipse (3.2.2), I get this error: "Java HotSpot(TM) 64-Bit Server VM[localhost:8080] (may be out of synch) was unable to replace the running code with the code in the workspace. Reason: Hot code replace failed - Scheme change not implemented" I wish I could help you, but as you can see, I'm dealing with the same issue you are. :o) Perhaps one of the other folks on the list might have some better ideas. Andy On Sat, 2008-04-12 at 19:26 +0200, Jakob Keres wrote: > Am Samstag, den 12.04.2008, 11:28 -0400 schrieb Andy Huhn: > > Hi Jakob, > > > > Also, which version of Jetty are you using? > > > Jetty6 but... > > > I don't believe there's a > > way to get component reloading working yet with Eclipse + Jetty6, > > although there is with Eclipse + Jetty5. > > ...it's working. I just adpated the build path in Eclipse3.3 like this: > > Project Properties -> Java Build Path > Tab Source: added folder src/main/resources > Default output folder for all: projectname/target/classes > > Tab Libraries: removed the class folder with the resources directory > > Not sure, if this is the common way to do, but it works quite fine. > > Greets > Jakob > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
