[
https://issues.apache.org/jira/browse/QPID-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-3504:
-----------------------------
Attachment: 0001-QPID-3504-Fixed-evaluation-of-QPID_HOME-in-windows-Q.patch
The attached patch fixes the evaluation of QPID_HOME if this environment
variable is not set. Also, it adds %QPID_HOME%\lib\opt\ into CLASSPATH where
BDB je.jar should be put when QPid Broker is run with bdb message store.
> add the bdb backed store implementation for the Java broker to our ASF repo
> as an optional build module
> -------------------------------------------------------------------------------------------------------
>
> Key: QPID-3504
> URL: https://issues.apache.org/jira/browse/QPID-3504
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Broker BDB Store
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.13
>
> Attachments:
> 0001-QPID-3504-Fixed-evaluation-of-QPID_HOME-in-windows-Q.patch
>
>
> Email to the dev list from a couple weeks ago:
> Hi all,
> As some of you no doubt already know the Java broker has a few
> configuration/message store implementations, with there currently being
> Memory, Derby (to be split into truly generic JDBC + Derby implementations at
> some point), and BDB Java Edition backed implementations of the interfaces.
> Although the store code itself for the last of these implementations carries
> the Apache Licence v2.0 it depends on a library licenced under the Sleepycat
> licence [1], which is classed as a Category X dependency here at Apache and
> so can't be distributed by the project. As a result, this store
> implementation has always been hosted elsewhere and I recently began looking
> into moving it to Apache Extras. Having done so I was instead left with the
> impression that it would actually be possible to move the code into our ASF
> repo. This was reinforced after further investigation lead me to instances of
> other Apache projects that currently are or have previously been doing
> roughly what I thought to be allowable. I have since enquired on this
> possibility over on legal-discuss and my question was answered positively [2].
> Based on this I propose to do the following:
> - Move the BDB based store code into our ASF repo as the basis of an optional
> component that is not compiled by the build process by default, and is not
> referred to in the shipping broker configuration.
> - Add targets to our Ant build to allow downloading the BDB jar (with warning
> that it is Sleepycat licenced) and building the associated store module.
> - Improve the documentation describing how users would update their
> configuration to use the optional component, and where to download the
> necessary BDB dependency it requires (again with warning it is Sleepycat
> licenced).
> I think this will be easier going forward both for us developers and for
> users, but this is a heads up in case there are those in the community
> particularly against such a change being made; if so please speak up now, as
> I hope to get round to doing this in the not too distance future.
> Robbie
> [1]
> http://www.oracle.com/technetwork/database/berkeleydb/downloads/jeoslicense-086837.html
> [2] http://s.apache.org/nP
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
