[Hawkular-dev] Console project structure and plugins

Thomas Heute theute at redhat.com
Wed Jan 28 06:04:53 EST 2015


On 01/28/2015 09:38 AM, Juraci Paixão Kröhling wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/27/2015 06:09 PM, Viliam Rockai wrote:
>> 1. Create separate repository for each component. Those all would
>> be bower dependencies of the hawkular console. Pros: possibly
>> consistent with the Hawtio 2.x ways, modularity = we download only
>> what we need. Cons: lots of repositories to take care of.
> I'd go with this one, coupled with a good CI mechanism. For Jenkins,
> you could have "pipes" and a "release" plugin, so, if the modules are
> independent enough, releasing should not take an effort bigger than
> clicking on a button (if that's what you mean by "lots of repositories
> to take care of").
+ productization ;)


>
> - - Juca.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUyJ/6AAoJECKM1e+fkPrXOCUH/1WEYUVWksIya2Y3kZKmXnjv
> JhFsGcmYHUFNk+3I+fnJGJzQuvOfpd0mErPjDleqV11yMDyLZQx843c50eIjiK1F
> uJelnyOUWQBv0fg05akL0P/xdb4Tc9rCfMWXyzOdQVlcX/70/JWFMxfxJLqXD2U1
> r9UUzQOq2BLrGs+SOEHRHL1F2W1zKoBdwyng8v3TY/auqMzIz3EN1XcJIGZVaX+G
> LvobmEy1MqU9L5l90fHodY3WpS+47pZehG91FrlcMnr0EHwUxCo1ByWT+qQ9OzVZ
> 7QlzacwupjmSSBewUmJnZFubH9X6zg2pR/q19wkT9CQ91ROeVL89bAVKnsFrP58=
> =MM7m
> -----END PGP SIGNATURE-----
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev



More information about the hawkular-dev mailing list