The project build path must contain Tapestry and all of it's dependencies at the time the Spindle builder runs (right after the Eclipse java compiler). I'm not well versed with maven but there are two ways to go:
1. Use the Tapestry Framework Library - all is well 'cuz it adds Tap + deps to build path 2. Remove Tapestry Framework Library and go your own way. A viable option but you are responsible for making sure Tap + deps are in the project build path. I'm assuming that you are using maven only to build/deploy your app thereby bypassing the Eclipse builders altogether? Spindle needs the Eclipse compiler to run successfully in order to work at all Geoff On 5/24/05, sastan <[EMAIL PROTECTED]> wrote: > Hello, > > i am working with eclipse 3.0, spindle 3.1.24 and maven 1.0.2 > > I had a complete tapestry app up and running. Then i wanted maven to > manage the dependencies and removed all other dependencies. It also > worked with jetty launcher and as war. > > But now spindle reports my an error: > No Tapestry build, the Tapestry jars are missing from the build > > They are there!! I also tried to add the original lib-dependencies from > spindle. It didn't help. > > In the result spindle isn't full functional. > > Can anybody give me a hint please. > > sastan > > > > --------------------------------------------------------------------- > 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]
