Re: [Hawkular-dev] Removal of embedded Cassandra
Wait, what? I didn't finish this thread but I just jumped out of my chair.
You mean I have to separately run and manage a C* cluster just to run itests?? Why would
we require that? So now the tests will always fail unless you have some extra server that
you run manually outside of the tests?
Plus, with that, it is not so simple anymore for Joe Developer to simply git clone and
"mvn clean install -Pitest" and see things work. They will now have to
separately install and run their own C* cluster (and first know that that has to be
done).
-1 that.
Forcing someone to run something OUTSIDE of the itest framework just to get the itests to
pass is wrong.
Or am I missing something? Will the itests framework run a standalone C* at the start and
shut it down after it finishes?
----- Original Message -----
On 14.06.2016 12:58, Heiko W.Rupp wrote:
> On 14 Jun 2016, at 12:20, Juraci Paixão Kröhling wrote:
>
>> - Keep everything as is, but change the default value for
>> `hawkular.backend` to `remote` instead of the current `embedded_cassandra`
>
> I think this needs to be the default no matter what is decided for the
> next item.
If we don't ship Cassandra, then it makes no sense to have this
property, no? Or am I missing something?
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev