This is starting to sound like an issue that should be fixed in tapestry rather than changing the way the jar is generated.
It sounds like tapestry will act differently when referencing a classpath jar than if unzipping the jar and referencing a classpath directory. I think tapestry should act exactly the same in these two circumstances. There is an interesting conversation here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=243163 -- View this message in context: http://tapestry.1045711.n5.nabble.com/Cannot-get-component-library-to-load-tp5713444p5713575.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
