activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <clebert.suco...@gmail.com>
Subject Re: [DISCUSS] Adding Derby as a dependency
Date Sun, 14 Jan 2018 21:05:49 GMT
We already have jdnc as a feature.

On Sun, Jan 14, 2018 at 2:47 PM Michael André Pearce <
michael.andre.pearce@me.com> wrote:

> 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 <clebert.suconic@gmail.com>
> 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
>
-- 
Clebert Suconic

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message