On Sat, Mar 28, 2015 at 3:12 AM, Branko Čibej <[email protected]> wrote:

> On 28.03.2015 10:43, Konstantin Boudnik wrote:
> > On Sat, Mar 28, 2015 at 09:00AM, Branko Čibej wrote:
> >> On 28.03.2015 06:41, Konstantin Boudnik wrote:
> >>> On Fri, Mar 27, 2015 at 08:32PM, Dmitriy Setrakyan wrote:
> >>>> (restarting a new vote for 1.0.0 after having fixed the LGPL issue
> that was
> >>>> raised during the previous vote today)
> >>>>
> >>>> I have uploaded the new 1.0.0 release candidate to:
> >>>>   http://people.apache.org/~dsetrakyan/incubator-ignite-1.0.0/
> >>>>
> >>>> The following changes were made based on all the feedback I got for
> RC3:
> >>>>
> >>>> 1. Added the ability to build a binary ZIP file without LGPL
> dependencies.
> >>>> 2. Fixed jdk8.backport wrong license issue.
> >>>> 3. Fixed NOTICE.txt according to comments from IPMC.
> >>>> 4. Fixed LICENSE.txt according to comments from IPMC.
> >>>>
> >>>> To build a binary release from source run:
> >>>>
> >>>>     # With LGPL dependencies
> >>>>     mvn clean package -DskipTests
> >>>>
> >>>>     # Without LGPL dependencies
> >>>>     mvn clean package -DskipTests -P-lgpl,-examples
> >>> Would it make sense to turn off 'lgpl' by default? Perhaps doesn't
> have to be
> >>> addressed until next release, unless a re-spin will happen.
> >> These dependencies /have/ to be turned off by default, because otherwise
> >> it's too easy to build binaries that are not ALv2. Especially if that
> >> -P-lgpl is not documented anywhere.
> > It's documented at the top of the DEVNOTES.txt. But it's better to off
> it by
> > default, of course to avoid _any_ possible hiccups.
>
> Ah, right, it's in devnotes in the package.
>
>   * 'For official apache binary release,' ... there is no official
>     Apache binary release.
>

Got it.


>   * 'To execute this build you need to be in GIT root folder.' ...
>     appears not to be true.
>

Will fix.


> All the other 'optional' dependencies are built by default. Why are they
> called optional?
>

They are optional because when you build the binary release they end up in
the "libs/optional" folder and do not get loaded by default when you
startup the application. To enable them, you have to move them from the
optional folder to the libs folder.


>
>
> Really, I seem not to be getting the message through here. And I keep
> getting the impression that someone is in a huge hurry to just get
> something out the door. I have to ask again, what's the rush?
>

Of course we want to see the project on which we worked so hard for the
past 9 months go through it's first official 1.0 release. We are not
rushing this release prematurely, it has been very well tested and all the
issues form the previous vote were fixed.


>
> -- Brane
>
>

Reply via email to