4:37 a.m.
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)
4:53 a.m.
On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian <jtakvori(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
4:55 a.m.
Yes, I'd like a profile-based solution as well.
On Mon, Oct 30, 2017 at 10:53 AM, Lucas Ponce <lponce(a)redhat.com> wrote:
On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian <jtakvori(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
1:29 p.m.
I think another question is will we ever want to include things outside of
inventory? Would having a UI to help with development/testing also be
useful for other pieces of Hawkular Services?
I think using a separate repo (possibly re-using the hawkular-ui repo)
could be a good idea here, and then bringing it into Hawkular Services if a
profile is activated.
On Mon, Oct 30, 2017 at 5:55 AM, Joel Takvorian <jtakvori(a)redhat.com> wrote:
Yes, I'd like a profile-based solution as well.
On Mon, Oct 30, 2017 at 10:53 AM, Lucas Ponce <lponce(a)redhat.com> wrote:
>
>
> On Mon, Oct 30, 2017 at 10:37 AM, Joel Takvorian <jtakvori(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
2584
days inactive
2584
days old
3 comments
3 participants
participants (3)
-
Joel Takvorian -
Lucas Ponce -
Matthew Wringe