Both done. For building simple "ant" should now suffice.

Jan

On Mon, Sep 11, 2017 at 6:30 PM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> That would be brilliant, thanks very much!
>
> Gj
>
> On Mon, Sep 11, 2017 at 6:28 PM, Jan Lahoda <lah...@gmail.com> wrote:
>
> > Unless someone disagrees (or wants to do that), my plan is to push the
> > missing file and change the default cluster config to basic later today.
> > After that, building should simply be done by "ant".
> >
> > Jan
> >
> > On Mon, Sep 11, 2017 at 6:23 PM, Simon IJskes <si...@ijskes.org> wrote:
> >
> > > After the 1st run, i followed that instruction and it fixed that
> > > particular problem.
> > >
> > > And i have a succesful build i see:
> > >
> > > BUILD SUCCESSFUL
> > > Total time: 3 minutes 6 seconds
> > >
> > >
> > >
> > > On 11-09-17 18:19, Geertjan Wielenga wrote:
> > >
> > >> I see this problem still when building, of course we have not fixed
> this
> > >> at
> > >> this point. But the fix above does not work for me, so I cannot build.
> > >>
> > >> Gj
> > >>
> > >> On Thu, Aug 31, 2017 at 11:07 AM, Jan Lahoda <lah...@gmail.com>
> wrote:
> > >>
> > >> Hi,
> > >>>
> > >>> I am afraid the compilation is indeed broken, probably some mistake
> in
> > a
> > >>> "last moment" change. For now, I'd suggest to manually create file:
> > >>> core.network/external/binaries-list
> > >>>
> > >>> with content:
> > >>> 22C41D62B7BD70C00603B2CAE75406414224CF9F nsProxyAutoConfig.js
> > >>>
> > >>> We need to fix more properly as soon as we can, of course.
> > >>>
> > >>> Jan
> > >>>
> > >>
> > >
> >
>

Reply via email to