This sounds familiar... I think that the solution was to use different render phases to control the ordering of imports. Instead of putting @Import statements at the class level, put them on render phase methods (eg setupRender and beginRender) to control the ordering.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Inheritance-and-the-order-of-loaded-JS-tp5714430p5714433.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
