Mazz,
I have nothing against your PR in particular, but I'm against this
feature in principle: it's more code that we have to take care of for
"development only". And as it's more code, it also means more bugs.
Perhaps not now, but in a week or two (or once we have a change in the
XML templates).
To me, requiring the developer to install Cassandra is similar to
requiring a developer to install MariaDB or PostgreSQL and that's
acceptable, specially if we don't have to maintain code that is to be
used only for development purposes.
On a Fedora machine, Cassandra can be installed and started by:
# dnf config-manager --add-repo=http://rpm.datastax.com/community
# dnf install dsc30
# systemctl start cassandra
( plus, there might some required changes related to networking in
/etc/cassandra/conf/cassandra.yaml )
That said, I suggest -Paio (all-in-one) for the profile name :)
- Juca.
On 20.06.2016 18:02, John Mazzitelli wrote:
I just submitted a new PR for hawkular services:
https://github.com/hawkular/hawkular-services/pull/22
This re-introduces the ability to build Hawkular Services with embedded Cassandra if you
want.
This will ONLY embed Cassandra IF you build with the special Maven profile -Pembeddedc.
If you never build with that profile, Hawkular Services will build as it does now (that
is, requires you to install and start your own Cassandra separately).
So this will allow developers to continue doing what they've been doing (that is, no
need to run a standalone C*) if they want.
Again, the default build is NOT to embed Cassandra. You must explicitly tell Maven you
want to embed C* via -Pembeddedc to get this feature.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev