Hi,
as there was _zero_ feedback, I just killed the experiment. I'll leave
the code in the tools repository.
Greetings
Matthias
Am Dienstag, dem 02.03.2021 um 20:08 +0100 schrieb Matthias Bläsing:
> Hi,
>
> Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer:
> >
> > This is
Hi,
Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer:
>
> This is bit of a complaint addressed to the NB infra community. When you
> are stuck behind corporate proxy that is very aggressively filtering web
> content, mirrors are a nightmare for you. In my case we need to
Hi,
On Tue, 14 Apr 2020 at 12:27, antonio wrote:
> I think it's better to generate an "update.xml" file for each mirror,
> containing full urls for the given mirror, and generate them _once_, and
> not for _every_ user request. That would be 226 [1] update-xml files. We
> can generate a webpage
Hi Matthias,
Thanks for the explanation, crystal clear now.
I think it's better to generate an "update.xml" file for each mirror,
containing full urls for the given mirror, and generate them _once_, and
not for _every_ user request. That would be 226 [1] update-xml files. We
can generate a
On Tue, 14 Apr 2020 at 11:13, Matthias Bläsing
wrote:
> Yes - it is the _catalog_ not every nbm. Yes this still needs work (for
> example instead of loading the catalog and working on the DOM, a
> streaming parser should be able to do the modification on-the-fly). The
> alternative would be to
Am Dienstag, den 14.04.2020, 10:20 +0100 schrieb Neil C Smith:
> On Mon, 13 Apr 2020 at 20:44, Matthias Bläsing
> wrote:
> > Fetch the base updates.xml:
> ...
> > The difference is, that the "distibution" attributes are relative i the
> > base version and fully qualified in the mirror version.
>
Hi,
Am Dienstag, den 14.04.2020, 06:02 +0200 schrieb antonio:
> I see your point, I just can't understand why this computes the URLs on
> the server side (in the netbeans-vm php file) and not on the client side
> (in the IDE itself).
>
> Wouldn't it be easier to let the user choose her
On Mon, 13 Apr 2020 at 20:44, Matthias Bläsing
wrote:
> Fetch the base updates.xml:
...
> The difference is, that the "distibution" attributes are relative i the
> base version and fully qualified in the mirror version.
...
> Does this looks sane?
If you're thinking of generating every request
Hi Matthias,
Sorry for the late reply.
I see your point, I just can't understand why this computes the URLs on
the server side (in the netbeans-vm php file) and not on the client side
(in the IDE itself).
Wouldn't it be easier to let the user choose her preferred mirror(from a
drop down
Hi all,
Am Donnerstag, den 30.01.2020, 14:55 + schrieb Jean-Marc Borer:
> This is bit of a complaint addressed to the NB infra community. When you
> are stuck behind corporate proxy that is very aggressively filtering web
> content, mirrors are a nightmare for you. In my case we need to
Well, correct me if I am wrong, but the update center index itself is not
hosted on the mirrors. You get redirected from the links provided in the
index. And that is the issue for us.
On Wed, Feb 5, 2020 at 9:06 PM Laszlo Kishalmi
wrote:
> I think the best way would be mirror the update center
I like Matthias idea. At least with companies with very restrictive
whitelisting policies, you could force the use of a whitelisted mirror.
Sounds good.
Is there a need to write a plugin for that, or change something on the
infra or is it an improvement request for NB?
Cheers,
JMB
On Thu, Feb
Geertjan Wielenga wrote:
> I'm not sure what the solution is.
FYI, the Eclipse Installer (aka Eclipse Oomph) has a "Use mirrors" check
box, which is checked by default and thus likely being using in the vast
majority of installs. The traditional Eclipse "Install New Software
Dialog" doesn't
I think the best way would be mirror the update center from one specific
mirror (or might be even from the dist) internally in the corporation,
then set up that one as an update center.
You might wrote a very minimal plugin to set that UC up for everyone if
there are a lot of people involved.
On Wed, 5 Feb 2020, 14:21 Peter Kovacs, wrote:
> The ASF publishes the releases at:
>
> https://apache.org/dist/netbeans/
>
> Maybe that is less of an issue?
>
That's an option, keeping in mind the limits here if there's a lot of
corporate use though - https://www.apache.org/dev/infra-ban.html
The ASF publishes the releases at:
https://apache.org/dist/netbeans/
Maybe that is less of an issue?
On 05.02.20 14:50, Geertjan Wielenga wrote:
> I'm not sure what the solution is.
>
> Gj
>
> On Wed, Feb 5, 2020 at 2:46 PM Jean-Marc Borer wrote:
>
>> Any opinion here?
>>
>> For us, mirrors
I'm not sure what the solution is.
Gj
On Wed, Feb 5, 2020 at 2:46 PM Jean-Marc Borer wrote:
> Any opinion here?
>
> For us, mirrors are just giving us headaches for plugins and updates...
>
> On Thu, Jan 30, 2020 at 2:55 PM Jean-Marc Borer wrote:
>
> > Hi guys,
> >
> > This is bit of a
Any opinion here?
For us, mirrors are just giving us headaches for plugins and updates...
On Thu, Jan 30, 2020 at 2:55 PM Jean-Marc Borer wrote:
> Hi guys,
>
> This is bit of a complaint addressed to the NB infra community. When you
> are stuck behind corporate proxy that is very aggressively
Hi guys,
This is bit of a complaint addressed to the NB infra community. When you
are stuck behind corporate proxy that is very aggressively filtering web
content, mirrors are a nightmare for you. In my case we need to whitelist
every single server hosting java binaries otherwise we get empty
19 matches
Mail list logo
