There are few T5.4-a2 components (that I seem to use) that pull in the
core stack which then imports the bootstrap.css. Alerts is one of
them, which I've Munky Patched not to. You're then free to import
whatever CSS you want in whatever order as per usual.
Another option (which I also do to keep the exception screens looking
pretty) is to define your own Bootstrap asset dir:
@Contribute(SymbolProvider.class) @ApplicationDefaults
public static void
contributeApplicationDefaults(MappedConfiguration<String, String>
config) {
// use a newer version of bootstrap
config.add(SymbolConstants.BOOTSTRAP_ROOT,
"classpath:/META-INF/assets/bootstrap-2.2.2");
}
Steve.
On 9 February 2013 20:54, Lance Java <lance.j...@googlemail.com> wrote:
> If I was to take a guess, it would be the new usage of require.js in tapestry
> 5.4. Tapestry has defined a bootstrap module. You might need to define a
> module which depends on the bootstrap module to guarantee that yours is
> loaded after bootstrap.
>
> As I said, this is a guess... I've not yet dug too far in this area yet
> myself.
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-5-4-alpha-2-css-overriding-tp5719856p5719904.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
