My two cents is about consistency of either we do provide integrations with other products out the box or not.
If the arguments of people not wanting to add Kafka clients to the class path for ability to link Artemis with Kafka, because it means having to maintain it (see it’s thread for all discussion), I don’t see why linking Artemis with a specific JDBC vendors product like Apache Derby is any different here. Not that I’m against this, quite the contrary actually if I could add Kafka integration, but I would like this ruling to be consistent. Sent from my iPhone > On 12 Jan 2018, at 23:51, Clebert Suconic <[email protected]> wrote: > > I would like to add an option on artemis create to enable jdbc. > > > By default (if you don't provide any other configuration) it will use > derby by default on the properties. > > > And I wanted to add derby as a dependency on ./lib > > > Anyone against it? > > > so, you would do ./artemis create --jdbc > > > and it would configure derby as an option > > > > (JDBC is not encouraged.. the journal is the best option.. but same as > in ActiveMQ5, some people need it). > > > > > also: I'm trying to understand what I need to change on dep.xml under > artemis-distribution, but I can't make it to work... anyone can give > me a hand on that? > > > > > -- > Clebert Suconic
