Hey all,
We have a proposal solution already implemented in LO. We use this maven
plugin:
https://github.com/eirslett/frontend-maven-plugin
It just downloads node.js/bower/grunt and use it locally, no need to
install those on your system.
This is how we have it in the LO right now (it'll be changed in the
future):
https://github.com/liveoak-io/liveoak/blob/master/console/pom.xml#L143
Right now, we store 3rd party JS libs in git, too, but we can update
them using bower (run from maven). I would prefer to make this part of
the build process in the future.
Viliam
On Mon, 2014-03-31 at 08:08 -0400, Stian Thorgersen wrote:
Without any tests for the admin console, upgrading the AngularJS
version is quite time consuming as everything has to be manually tested. Until that's
sorted I don't see this as a big priority.
Whatever solution we choose for this have to:
* Be the same as used for AngularJS patternfly project and LiveOak console
* Be in Maven central
* Not require installing Bower, Grunt or NPM - building Keycloak should only require Java
+ Maven
----- Original Message -----
> From: "Stan Silvert" <ssilvert(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Friday, 28 March, 2014 7:02:59 PM
> Subject: [keycloak-dev] versioning of js packages
>
> I just noticed that we have js libs like angular checked into GitHub:
>
https://github.com/keycloak/keycloak/tree/master/admin-ui/src/main/resour...
>
> As far as I can tell, this requires manually uploading new versions
> whenever you want to upgrade.
>
> Have you guys tried or considered the npm Maven plugin?
>
http://java.dzone.com/articles/introducing-npm-maven-plugin
>
> Any thoughts about js package management in a Maven project?
>
> Stan
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>