<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 29, 2014 at 3:00 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good morning, I have some n00b questions. What happens with web<br>
developer or node developers who don't care about Maven?</blockquote><div><br></div><div>Generally that's a huge problem: requiring maven for 'web folks'; For 'pure' JS/Web projects I'd be -1 on something like this</div>
<div><br></div><div>However this case here is different, IMO;<br></div><div>To build the entire UPS, maven is the tool and the admin-ui itself (standalone) is pretty useless;</div><div><br></div><div><br></div><div>-Matthias</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Is still<br>
possible to make use of pure node to build admin-ui?<br>
<br>
Speaking about the downsides:<br>
<br>
I think this might be a concern, if is necessary to fix something at each Node<br>
upgrade.<br>
<br>
> * he had some issues himself to get it work, especially during Node<br>
upgrades<br>
> * stability of the build can be questionable<br>
<br>
I'm not sure about the negative influence if is possible to choose. Could you<br>
please elaborate?<br>
<br>
> * it can negatively influence developers that are not aware of Node<br>
tooling<br>
<br>
My latest question is: do we really need this? why?<br>
<div><div class="h5"><br>
On 2014-05-29, Lukáš Fryč wrote:<br>
> Hey guys,<br>
><br>
> we would like to evaluate "frontend-maven-plugin" [1] that could be used as<br>
> a mean to compile admin-ui distribution files into ag-push.war webapp<br>
> during Maven build time<br>
><br>
> This way we would enable people not familiar with node/npm/bower/grunt<br>
> tooling to compile latest and greatest,<br>
><br>
> and additionally avoid a need to compile and save into git repository.<br>
><br>
> <a href="https://issues.jboss.org/browse/AGPUSH-672" target="_blank">https://issues.jboss.org/browse/AGPUSH-672</a><br>
><br>
> Note1: web developer will still leverage Node tooling<br>
><br>
> Note2: this is post UPS 0.11.0 thing! ;-)<br>
><br>
><br>
> As pointed out in the JIRA, this may have its downsides,<br>
><br>
> so if anyone has some concerns please speak up now. :-)<br>
><br>
><br>
> Cheers,<br>
><br>
> ~ Lukas<br>
><br>
> [1] <a href="https://github.com/eirslett/frontend-maven-plugin" target="_blank">https://github.com/eirslett/frontend-maven-plugin</a><br>
<br>
</div></div>> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
--<br>
<br>
abstractj<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>