Changed the rewrite rule on netbeans-vm to forward to the Apache
Archives for 9.0 nbm-s.
Also archived the 9.0 release.
On 12/27/18 5:38 AM, Antonio wrote:
Gavin McDonald says they'll tell us if there're any traffic problems,
and that 9.0 is in the archive, and that we should use that.
http:
Gavin McDonald says they'll tell us if there're any traffic problems,
and that 9.0 is in the archive, and that we should use that.
http://archive.apache.org/dist/incubator/netbeans/incubating-netbeans-java/incubating-9.0/
Cheers,
Antonio
El 27/12/2018 a las 14:26, Antonio escribió:
Hi all,
I
Hi all,
I'm asking at infra.chat if we should use the archive or
netbeans-vm.apache.org.
Cheers,
Antonio
El 27/12/2018 a las 9:46, Emilian Bold escribió:
That's no questions. My only concern is where to store.
We store on Apache infra and if it's too much for them we ask them for
suggesti
> That's no questions. My only concern is where to store.
We store on Apache infra and if it's too much for them we ask them for
suggestions or new servers.
I understand how you computed but for older nbms I don't believe we
will have even a fraction of those maximum downloads.
--emi
http://coo
On 12/26/18 11:23 PM, Emilian Bold wrote:
Considering the are no updates, why would we even serve the nbms? To
older 8.2 installs or what? Won't those older installs request the 10
nbms anyhow? So, I don't see how those nbms would get so many
downloads.
I've just really calculated the worst cas
Considering the are no updates, why would we even serve the nbms? To
older 8.2 installs or what? Won't those older installs request the 10
nbms anyhow? So, I don't see how those nbms would get so many
downloads.
We can put the smaller updates.xml.gz anywhere, it won't make any
impact on bandwidth.
Dear all,
I have to bring up this old item again. According to the Apache release
processes, I'd need to archive the current 9.0 release from the site.
this means that our 9.0 NBM-s are going to be removed from there as
well. The files are going to be available on archive.apache.org which is
On Sat, Apr 14, 2018 at 8:57 AM, Emilian Bold
wrote:
> Ah, so it's a matter of repackaging them?
>
Yes, the (my) current idea for OSGi bundles is to wrap them into NBMs with
LICENSE, etc. This is when creating an update center for the NB
distribution, others may still produce update centers with
AFAIK Jan is currently working on that:
https://github.com/apache/incubator-netbeans/pull/494
Un abrazo,
Antonio
P.S.: Current generated artifacts are at:
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-linux/lastSuccessfulBuild/artifact/nbbuild/nbms/
On 14/04/18 0
Ah, so it's a matter of repackaging them?
--emi
‐‐‐ Original Message ‐‐‐
On 14 April 2018 9:54 AM, Antonio wrote:
> On 14/04/18 08:27, Emilian Bold wrote:
>
> > > 1- It seems we won't be able to host some OSGi bundles in the mirror
> > >
> > > system due to licensing issues?
> >
> >
On 14/04/18 08:27, Emilian Bold wrote:
1- It seems we won't be able to host some OSGi bundles in the mirror
system due to licensing issues?
If we are able to make a release with this dependency how are we not allowed to
distribute the binaries?
As Jan said 2018/04/10 (13:08), quoting:
"On
> 1- It seems we won't be able to host some OSGi bundles in the mirror
system due to licensing issues?
If we are able to make a release with this dependency how are we not allowed to
distribute the binaries?
--emi
‐‐‐ Original Message ‐‐‐
On 11 April 2018 9:39 AM, Antonio wrote:
> H
Hi all,
In order to understand this long thread (about NETBEANS-330 [1]) I tried
to summarize it. Please review and send corrections & questions as
appropriate.
Kind regards,
Antonio
== Objectives
Host the NetBeans 9.0 Update Center on Apache infrastructure.
== Constraints/facts/options
-
13 matches
Mail list logo
