<div dir="ltr"><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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style: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? Is still<br>
possible to make use of pure node to build admin-ui?<br></blockquote><div><br></div><div>This is a completely valid question and that's why it was answered beforehand. :-)</div><div><br></div><div>{quote} <span style="font-family:arial,sans-serif;font-size:13px">Note1: web developer will still leverage Node tooling {quote}</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">...during his regular workflow</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<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></blockquote><div><br></div><div>Since I did not used it, I can't say it's 100% way to go, but it's worth a prototype work.</div><div><br></div><div>There seems to be a non-trivial community around this tool.</div>
<div><br></div><div>(Btw we did something similar with use of PhantomJS back in Arquillian and it's HUGE win for users.</div><div>They don't even know there was ever some problem with downloading PhantomJS.)</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
My latest question is: do we really need this? why?<br></blockquote><div><br></div><div>The problem this plugin solves is that everytime you change admin-ui, you need to compile down distribution and save it as a source tree (and this itself is no, no..!, NO!).</div>
<div><br></div><div>* if you forget. you will get your friends into trouble - they won't work on up to date version anymore</div><div>* you are polluting git commit history with non-relevant changes</div><div>(sidenote: at this very moment, we don't compile distribution - once we do so, some of admin-ui dist files will be removed and some will be added with each admin-ui change)<br>
</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div>The fact is not only we, but also larger community, are facing the same issue:<br></div><div><br></div><div>* how the hell connect the web development tooling with Maven tooling?,</div>
<div>* or vice-versa my boss wants me to produce WAR, but I'm frontend developer who knows no java</div><div><br></div><div>It frontend-maven-plugin works it is the solution for broader audience. If not, we should keep seeking an answer.</div>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<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></div></div>