On Mon, Jun 2, 2014 at 3:09 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
On Jun 2, 2014, at 3:24 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
On Thu, May 29, 2014 at 3:00 PM, Bruno Oliveira <bruno(a)abstractj.org>
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.
The AdminUI still can be build with the vanilla JS tools - the
maven-frontend-plugin would just leverage those JS tools (as a convenience
for those that build the entire server w/ java)
-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
_______________________________________________
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