fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <ro...@shaposhnik.org>
Subject Re: FW: [DISCUSSION] How to deal with runtime dependencies
Date Thu, 11 Feb 2016 02:24:37 GMT
On Wed, Feb 10, 2016 at 12:56 AM, Markus GeiƟ <markus.geiss@live.de> wrote:
> Hey all,
>
> We've started a thread at our dev list and forgot to send it to the
> general incubator list too.
> Any opinion is appreciated, you can find the original message below.
>
> Best,
>
> Markus
>
> .::YAGNI likes a DRY KISS::.
>
>> From: markus.geiss@live.de
>> To: dev@fineract.incubator.apache.org
>> Subject: [DISCUSSION] How to deal with runtime dependencies
>> Date: Mon, 8 Feb 2016 14:12:04 +0100
>>
>> Hey all,
>>
>> hope this finds you well.
>>
>> I thought instead of discussing this on top of pull request, because it is more
>> than just the JDBC driver, it is the right time to create a new thread.
>>
>> We are currently using MySQL's Connector/J and Hibernate's EntityManager at
>> runtime as the JDBC driver and JPA implementation. Our source code is not
>> depending on both.
>>
>> It would create a huge effort to replace both for test and production environments.
>>
>> The questions is:
>>
>> Would it be compliant with the license policies if we omit them for our source
>> release, but keeping them for our own integration tests.
>>
>> If somebody is creating a deployable distribution, the expectation is that whomever
>> is creating the distribution can decide what he wants to use.

The devil is in the details. Can you show a branch with this solution to the
problem prototyped?

Thanks,
Roman.

Mime
View raw message