Geode-dependency-bom works for me
On Fri, Mar 29, 2019, 18:23 Jacob Barrett wrote:
> It’s not API so it can be changed later right?
>
> It’s not intended for general direct consumption. The client BOM is. We
> can define future BOMs for consumptions.
>
> -jake
>
>
> > On Mar 29, 2019, at 5:42 PM
It’s not API so it can be changed later right?
It’s not intended for general direct consumption. The client BOM is. We can
define future BOMs for consumptions.
-jake
> On Mar 29, 2019, at 5:42 PM, Anthony Baker wrote:
>
> Last call for naming suggestions. I’d like to fix this prior to rele
Last call for naming suggestions. I’d like to fix this prior to releasing
1.9.0.
> On Mar 27, 2019, at 9:31 AM, Anthony Baker wrote:
>
> What if we rename this to something like ‘geode-dependency-bom’?
>
>> I’m curious:
>>
>> - Why do all subprojects declare a dependency on
>> project(':boms:geode-all-bom’)) ?
>> - Why are we shipping geode-all-bom-1.9.0.jar in the lib/ dir and in our
>> war files?
>>
>>
>> Thanks,
>> Anthony
>>
>>
oms:geode-all-bom’)) ?
> - Why are we shipping geode-all-bom-1.9.0.jar in the lib/ dir and in our
> war files?
>
>
> Thanks,
> Anthony
>
>
I’m curious:
- Why do all subprojects declare a dependency on
project(':boms:geode-all-bom’)) ?
- Why are we shipping geode-all-bom-1.9.0.jar in the lib/ dir and in our war
files?
Thanks,
Anthony
