I like this idea due to fact it reduces number of manual steps needed to build
UPS server WAR via a single command. Ideal for JS noobs such as myself.

I don't like the fact that it could introduce test result inconsistencies, e.g.:

Alice: I can't register new variant via UI.
Bob: Which UPS version are you running?
Alice: Latest from master.
Bob: Works for me.
...both debugging...
Bob: Can you rebuild UPS? There was new UI with the fix committed meanwhile.

So, I believe that adding such plugin is a good idea if we keep UPS track a
specific non-movable commit from UI repository.

Karel

On Thu, 29 May 2014 13:43:02 +0200
Lukáš Fryč <lukas.fryc@gmail.com> wrote:

> Hey guys,
>
> we would like to evaluate "frontend-maven-plugin" [1] that could be used as
> a mean to compile admin-ui distribution files into ag-push.war webapp
> during Maven build time
>
> This way we would enable people not familiar with node/npm/bower/grunt
> tooling to compile latest and greatest,
>
> and additionally avoid a need to compile and save into git repository.
>
> https://issues.jboss.org/browse/AGPUSH-672
>
> Note1: web developer will still leverage Node tooling
>
> Note2: this is post UPS 0.11.0 thing! ;-)
>
>
> As pointed out in the JIRA, this may have its downsides,
>
> so if anyone has some concerns please speak up now. :-)
>
>
> Cheers,
>
> ~ Lukas
>
> [1] https://github.com/eirslett/frontend-maven-plugin

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev