To be honest I'm not understanding why this is being handled differently to
what we already have. We have npm-update which takes care of NPM modules
for admin console, old account console and login, which also covers
filtering.
On Tue, 5 Nov 2019 at 15:25, Alex Szczuczko <aszczucz(a)redhat.com> wrote:
I've been looking at this for a while now, and I'm thinking
that it'd be
best to split the
src/main/resources/theme/keycloak-preview/account/resources/package.json
and its associated files into a new maven pom. It would help this build to
work more elegantly, but it is possible for me to maintain it in the
current structure, if moving files around would be too disruptive to
development at this stage.
It's all a bit of a mess at the moment because account2 is assumed to be
non-compiled like the rest of the "themes", and it isn't. It has its own
package.json that needs to be used at build time.
Thoughts?
Alex
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev