Well, I have ProxySelector2 which is a working solution but which is a COMPLETE
replacement of the existing NB ProxySelector2 and fixes a bunch of other
reported issues too.
(URL: https://bitbucket.org/phansson/netbeansproxy2)
But the question is if there's time for taking that into the NB code base now?
As a quick workaround I should be able to in 24h to come up with a simple patch
that can make the existing ProxySelector work without the GPL'ed file. It still
wont work (as in: it won't do what it is supposed to) but we won't be worse off
than we are today. And then we'll leave inclusion of ProxySelector2 for post
NB9 phase, perhaps for NB9.1.
Let me know.
Peter
On Monday, September 11, 2017 9:43 PM, Geertjan Wielenga
<[email protected]> wrote:
Well, great, if you can solve the problem such that we avoid the licensing
problem while also having an actually working solution, that would be really
great. If you have a patch, i.e., one that removes the existing problematic
solution and replaces it with yours, that would be a way forward, I think, with
everything referenced in the issue you're referring to (i.e.,
https://issues.apache.org/jira/browse/NETBEANS-4).
Gj
On Mon, Sep 11, 2017 at 9:39 PM, Peter Hansson
<[email protected]> wrote:
>
>
>The problem you ran into, the missing nsProxyAutoConfig.js file, is touched
>upoin in https://issues.apache.org/ jira/browse/NETBEANS-4. As far as I
>understand the problem with the file is that it is GPL'ed and therefore cannot
>live in a Apache repo nor can it be distributed with an Apache licensed
>bundle. Or am I wrong?
>
>
>To fix, Geertjan wrote to me some time ago asking if I would donate my
>ProxySelector2 project to Apache and of course the answer was yes (emails from
>me to various parties on 11 Jun 2017).
>
>In any case, I haven't followed the incubator process and haven't heard more
>about the issue - until today when I stumbled over the messages where people
>said they couldn't build because of this missing file. I thought I would pitch
>in with what I know.
>
>If it is ok to include the file from a legal perspective - so the build will
>work - then I understand that it is a short term way forward to make the build
>work. But the file in question belongs to a part of NetBeans, the
>ProxySelector, which doesn't work with Java8 or later (it expects Rhino, not
>Nashorn) and therefore for all practical matters you might as well include an
>empty nsProxyAutoConfig.js file just to get going with the build. Anyway,
>ProxySelector2 project was born out of this deficiency as well as many others
>that exists with the existing ProxySelector in NB.
>
>
>I'm thrilled with the progress you've made and can't wait till the day when
>Apache NetBeans is ready to accept contributions.
>
>
>Peter
>
>
>
>
>
>
>
>On Monday, September 11, 2017 8:40 PM, Geertjan Wielenga
><geertjan.wielenga@googlemail. com> wrote:
>
>
>
>Great, thanks a lot.
>
>Gj
>
>
>On Mon, Sep 11, 2017 at 8:20 PM, Jan Lahoda <[email protected]> wrote:
>
>> Both done. For building simple "ant" should now suffice.
>>
>> Jan
>>
>> On Mon, Sep 11, 2017 at 6:30 PM, Geertjan Wielenga <
>> geertjan.wielenga@googlemail. com> wrote:
>>
>> > That would be brilliant, thanks very much!
>> >
>> > Gj
>> >
>> > On Mon, Sep 11, 2017 at 6:28 PM, Jan Lahoda <[email protected]> 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 <[email protected]>
>> 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 <[email protected]>
>> > 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:
>> > > >>> 22C41D62B7BD70C00603B2CAE75406 414224CF9F nsProxyAutoConfig.js
>> > > >>>
>> > > >>> We need to fix more properly as soon as we can, of course.
>> > > >>>
>> > > >>> Jan
>> > > >>>
>> > > >>
>> > > >
>> > >
>> >
>>
>
