* he had some issues himself to get it work, especially during Node

* stability of the build can be questionable

* it can negatively influence developers that are not aware of Node

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Good morning, I have some n00b questions. What happens with web developer or node developers who don't care about Maven?

Is still possible to make use of pure node to build admin-ui? Speaking about the downsides: I think this might be a concern, if is necessary to fix something at each Node upgrade. > * he had some issues himself to get it work, especially during Node upgrades > * stability of the build can be questionable I'm not sure about the negative influence if is possible to choose. Could you please elaborate? > * it can negatively influence developers that are not aware of Node tooling My latest question is: do we really need this? why? On 2014-05-29, Lukáš Fryč 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Jun 2, 2014, at 3:24 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > On Thu, May 29, 2014 at 3:00 PM, Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: > Good morning, I have some n00b questions. What happens with web > developer or node developers who don't care about Maven? > > Generally that's a huge problem: requiring maven for 'web folks'; For 'pure' JS/Web projects I'd be -1 on something like this > > However this case here is different, IMO; > To build the entire UPS, maven is the tool and the admin-ui itself (standalone) is pretty useless; not entirely, i was messing around with creating a node.js version of the UPS( following the spec's ), and i was able to just copy the admin UI to it and it worked.

> > > -Matthias > > > Is still > possible to make use of pure node to build admin-ui? > > Speaking about the downsides: > > I think this might be a concern, if is necessary to fix something at each Node > upgrade. > > > * he had some issues himself to get it work, especially during Node > upgrades > > * stability of the build can be questionable > > I'm not sure about the negative influence if is possible to choose. Could you > please elaborate? > > > * it can negatively influence developers that are not aware of Node > tooling > > My latest question is: do we really need this? why? > > On 2014-05-29, Lukáš Fryč 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(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > > abstractj > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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(a)gmail.com&gt; 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Mon, 2 Jun 2014 17:17:04 +0200 Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > running againt master is IMO also using the latest development; > > If folks want stable, have them use released versions, instead of master Correct but the plugin would hide the fact there are two masters involved.

If we had UI as <dependency> with version -SNAPSHOT in pom.xml, that's a different thing.

> > > On Mon, Jun 2, 2014 at 4:40 PM, Karel Piwko <kpiwko(a)redhat.com&gt; wrote: > > > 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(a)gmail.com&gt; 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(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Mon, 2 Jun 2014 17:55:43 +0200 Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > Correct but the plugin would hide the fact there are two masters involved.> > > two masters? master in terms of git? Exactly. Recently, I've noticed that UI has been merged to UPS repository, so this would not be an issue any more. Two masters no more. https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/admin-ui > > > > If > > we had UI as <dependency> with version -SNAPSHOT in pom.xml, that's a > > different > > thing. > > > > as said earlier, I think Keycloak does that. But I am not sure on the > details of the UI bundling > KC has Angular as a part of regular Maven module: https://github.com/keycloak/keycloak/tree/master/forms/common-themes The problem here I'm presuming is a need to produce jar of admin-ui, which means bringing Ant/Maven/Gradle/Grunt task (maybe grunt-sync-jar) into current UI build. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev