Yes, I'd like a profile-based solution as well.

On Mon, Oct 30, 2017 at 10:53 AM, Lucas Ponce <lponce@redhat.com> wrote:

On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian <jtakvori@redhat.com> wrote:

Hi,

While I'm really glad that inventory has an embedded UI, very helpful while testing and debugging, it's a bit sad that it involves nodejs/npm build triggered during the maven build of hawkular-commons (build time is more than tripled).

For Hawkular Metrics UI we use a separate repo (hawkular-ui) for the build: all npm/nodejs build stuff happens there. On hawkular-metrics side, before preparing the WAR, the webapp is pulled using maven SCM plugin.

What do you think, can we have a similar process here? (I'd volunteer to do it)

As the UI is a development helper, I guess it can go a different repo (I don't think it has testing by itself).

But if potentially needs to grow (and additions and tests are necessary) then should be under the CI and perhaps it should be used a separate profile (-Pui) or similar to let travis to build it.

Both solutions sound good to me, so it is a matter of what people prefer to do.

Lucas

 

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

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

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