date:20190715

Some comments inlined below

El 16/7/19 a las 1:36, Michał Dymecki escribió:

I'm that "someone else" - author of the PR.

You say that "If it ain't broke, don't fix it...". The problem is, it is
broke and even the source code says it itself:

// @TODO - source maps not currently working

https://github.com/apache/netbeans-website/blame/a808570c4425c11fa490573f97307325f73a2646/netbeans.apache.org/build.gradle#L49

Also the full Foundation framework is used and now it generates 131kb
css file (!). And that mess cannot be debugged without source maps:

https://github.com/apache/netbeans-website/blame/a808570c4425c11fa490573f97307325f73a2646/netbeans.apache.org/src/content/scss/netbeans.scss#L28

Neil and Antonio commited that not working code into the repository, now
they want to close the PR that fixes their code, and when Chris wants to

The PR won't fix anything. On the contrary: it will break everything.

It will break the current jenkins jobs, for instance. So we'll need
"someone else" to decide which node/npm versions are required, and then
we'll need "someone else" to set-up the jenkins jobs to download several
hundred megabytes (node + npm + dependencies) just to add support for
source maps. And then we'll need "someone else" to maintain the
resulting build system.

What's being said in the PR, and in the mailing list, is that the effort
would pay off if we can get rid of gradle. This is, the PR is in the
right direction (and appreciated) but falls short in extent.

Adding node (8, 10, 12?) and npm (which version?) and third-party
dependencies (open versions? non-reproducible builds?) is adding too
much complexity to the build system (and to everybody's laptops). The
build system will be so complex that the current "someone else's" we
have in the Team won't be able to put up with it.

they want to close the PR that fixes their code, and when Chris wants to > help
with fixing it too, he's being disrespected. Did I miss something?

I don't think Chris is being disrespected in any way. On the contrary,
Neil and Eric and Geertjan and Wade and Emilian and Junichi and other
contributors (including Antonio) that have built the website are being
disrespected by people that just complain about the current status of
affairs from their comfortable sofas without proposing _working_
alternatives.

The big power of Apache Projects and Communities is that if you don't
like something you're free to propose new _working_ ways of doing things
(as you have done). Complaining in the mailing lists expecting that
"someone else" do something you can do yourself is not the way to go, I
think. Nor is trying to force committers to merge PRs that will add more
mainteinance effort and reduce little their spare time.

So thank you for your PR, Michał, really. We'll try to find "someone
else" in the future to allocate some of their spare time to replace
gradle with node+npm support for the _whole_ website build system,
including the jenkins jobs.

Meanwhile we'll use our shrinking spare time in migrating content to
Apache repositories, before the Oracle servers are out of service and
content is lost forever, even though we have to go without source maps
one additional year.

Kind regards,
Antonio

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: website build system: moving to node/npm?

2019-07-15 Thread Michał Dymecki


I'm that "someone else" - author of the PR.

You say that "If it ain't broke, don't fix it...". The problem is, it is 
broke and even the source code says it itself:

    // @TODO - source maps not currently working

https://github.com/apache/netbeans-website/blame/a808570c4425c11fa490573f97307325f73a2646/netbeans.apache.org/build.gradle#L49

Also the full Foundation framework is used and now it generates 131kb 
css file (!). And that mess cannot be debugged without source maps:


https://github.com/apache/netbeans-website/blame/a808570c4425c11fa490573f97307325f73a2646/netbeans.apache.org/src/content/scss/netbeans.scss#L28

Neil and Antonio commited that not working code into the repository, now 
they want to close the PR that fixes their code, and when Chris wants to 
help with fixing it too, he's being disrespected. Did I miss something?


The mentioned projects Apache Tamaya (Incubating) and Apache Incubator 
are not the best examples because they don't even use Sass and there are 
no frontend assets to compile. And Chris is right - with Gradle (or some 
other Java tool) we won't get too far with frontend assets.


Best regards,
Michael


On 15.07.2019 23:39, Geertjan Wielenga wrote:

On Mon, Jul 15, 2019 at 9:14 PM Christian Lenz 
wrote:

  So I’m for merge and there is someone else who wants to work on it, if

this changes.



You're for merging the PR and there is someone else who wants to work on
it, if this changes? If what changes? And who is "someone else"?

Gj






Cheers

Chris



Von: Antonio
Gesendet: Montag, 15. Juli 2019 20:59
An: dev@netbeans.apache.org
Betreff: Re: AW: website build system: moving to node/npm?

Thanks, Chris!

So let's await for those "frontend guys" with "> 10 years" of experience
to build a "common frontend stack" so they can "work on the page" with
"VuePress, Nuxt, Hugo or Hexo".

Meanwhile let's stick with the "guys working on that page" (no matter
whether backend or frontend) and let's close PR#375 [1].

As Geertjan suggested, "If it ain't broke, don't fix it...".

Thanks again & kind regards,
Antonio


[1]
https://github.com/apache/netbeans-website/pull/375


El 15/7/19 a las 15:30, Christian Lenz escribió:

We only need frontend guys working on that page and there are a lot of

frontend guys out there. There is Nothing half baked. Look at Github what
they have use a more common frontend stack. For me as a frontend developer
for > 10 Years, it is farly not Java or JBake or JVM whatever. This is not
a common frontend stack and the case why I didn’t work on the page is
exactly that using of the stack.

We don’t Need Java backend guys working on that page. Just a couple of

frontend guys and I guess david will aslo help here and me too.

My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents.


Cheers

Chris



Von: Neil C Smith
Gesendet: Montag, 15. Juli 2019 12:50
An: dev
Cc: Apache NetBeans
Betreff: Re: website build system: moving to node/npm?

On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga 

wrote:

If it ain't broke, don't fix it...

And do we expect lots of people to work on the site just because we

switch

from Gradle to Gulp? Do we need lots of people working on the site,
especially since everything's working fine the way it is?

Switching to an equally bespoke and arcane build system in Gulp, no.
Moving to a popular static generator ( https://www.staticgen.com/ )
and using it in a somewhat standard fashion (which we're not with
JBake as I recall) might be a good move to reduce technical debt.

If we did stay JVM, then Orchid might be worth looking into, as it
claims both to support JBake configuration and the additional things
we're doing in the custom build process?!

If someone has a proposal for a JS (or other) SSG that can do the full
job of what we have now in a standard way then I think it's strongly
worth considering.  But it needs to be a complete plan.  At my old
company I did take a brief look at Gatsby, but in the end mostly made
use of Jekyll due to the better (at the time) client-side CMS options
- or in other words, there are always other considerations in play!
:-)

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






--
Pozdrawiam,
Michał Dymecki


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail:

Re: AW: website build system: moving to node/npm?





El 16/7/19 a las 0:06, Neil C Smith escribió:

As you yourself said on that PR though,  some simplification would be good.
I've worked with a variety of SSG's over the years, and ours is it not
exactly easy to work on. A plan to reduce technical complexity would help
future work. Running Gulp on top of what's there now seems a step in the
wrong direction.


Agreed!

The Apache Incubator [1] uses jbake as well, and so does Apache Tamaya 
(Incubating) [2]. Those may be a source of inspiration to reduce complexity.


Anyway I think we should concentrate in 11.1 and in website content 
first. There're thousands of files at [3] with Platform Tutorials that 
need to be migrated to the Apache repositories (hopefully very soon).


Cheers,
Antonio


[1]
https://github.com/apache/incubator

[2]
https://github.com/apache/incubator-tamaya-site

[3]
https://svn.netbeans.org/svn/platform~platform-content/trunk/tutorials/


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: website build system: moving to node/npm?

On Mon, 15 Jul 2019, 19:59 Antonio,  wrote:

> So let's await for those "frontend guys" with "> 10 years" of experience
> to build a "common frontend stack" so they can "work on the page" with
> "VuePress, Nuxt, Hugo or Hexo".
>

:-)

> Meanwhile let's stick with the "guys working on that page" (no matter
> whether backend or frontend) and let's close PR#375 [1].
>

+1

> As Geertjan suggested, "If it ain't broke, don't fix it...".
>

As you yourself said on that PR though,  some simplification would be good.
I've worked with a variety of SSG's over the years, and ours is it not
exactly easy to work on. A plan to reduce technical complexity would help
future work. Running Gulp on top of what's there now seems a step in the
wrong direction.

I need to get my local website build working again this week to look at the
release download section. Time to remind myself how complicated it is!

Best wishes,

Neil

>

? about project properties..

2019-07-15 Thread Brad Walker

We have 417 project.properties files in the git repo..

These seem to be part of a Netbeans project for the various different
components.

I've noticed the project.properties file contains the following:

javac.source=1.6

Should we not think about maybe bumping that to 1.8?

-brad w.

JavaFX Wrapper should be updated

2019-07-15 Thread Zoran Sevarac

 Whats the plan with org.netbeans.libs.javafx ?
At the moment it wraps ${java.home}/lib/ext/jfxrt.jar which is not there
since Java 8


-- 
Zoran Sevarac, PhD, Associate Professor
Department of Software Engineering
University of Belgrade, Faculty of Organisational Sciences

Deep Netts   Co-founder & CEO  | Oracle
Groundbreaker Ambassador | Java Champion

Open source: Neuroph founder, Apache Net
Beans  contributor
Homepage: http://www.zoransevarac.com

AW: AW: website build system: moving to node/npm?

As you can see, there is Need for that:

➢ This PR adds support for Gulp task runner. Using Gulp / node.js tools for 
building frontend assets is a standard practice today. It offers more packages 
than Gradle and it will be easier to find new frontend developers.


It is not only my opinion and BTW, I wasn’t the author of the PR . So I’m for 
merge and there is someone else who wants to work on it, if this changes.


Cheers

Chris



Von: Antonio
Gesendet: Montag, 15. Juli 2019 20:59
An: dev@netbeans.apache.org
Betreff: Re: AW: website build system: moving to node/npm?

Thanks, Chris!

So let's await for those "frontend guys" with "> 10 years" of experience 
to build a "common frontend stack" so they can "work on the page" with 
"VuePress, Nuxt, Hugo or Hexo".

Meanwhile let's stick with the "guys working on that page" (no matter 
whether backend or frontend) and let's close PR#375 [1].

As Geertjan suggested, "If it ain't broke, don't fix it...".

Thanks again & kind regards,
Antonio


[1]
https://github.com/apache/netbeans-website/pull/375


El 15/7/19 a las 15:30, Christian Lenz escribió:
> We only need frontend guys working on that page and there are a lot of 
> frontend guys out there. There is Nothing half baked. Look at Github what 
> they have use a more common frontend stack. For me as a frontend developer 
> for > 10 Years, it is farly not Java or JBake or JVM whatever. This is not a 
> common frontend stack and the case why I didn’t work on the page is exactly 
> that using of the stack.
> 
> We don’t Need Java backend guys working on that page. Just a couple of 
> frontend guys and I guess david will aslo help here and me too.
> 
> My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents.
> 
> 
> Cheers
> 
> Chris
> 
> 
> 
> Von: Neil C Smith
> Gesendet: Montag, 15. Juli 2019 12:50
> An: dev
> Cc: Apache NetBeans
> Betreff: Re: website build system: moving to node/npm?
> 
> On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga  wrote:
>>
>> If it ain't broke, don't fix it...
>>
>> And do we expect lots of people to work on the site just because we switch
>> from Gradle to Gulp? Do we need lots of people working on the site,
>> especially since everything's working fine the way it is?
> 
> Switching to an equally bespoke and arcane build system in Gulp, no.
> Moving to a popular static generator ( https://www.staticgen.com/ )
> and using it in a somewhat standard fashion (which we're not with
> JBake as I recall) might be a good move to reduce technical debt.
> 
> If we did stay JVM, then Orchid might be worth looking into, as it
> claims both to support JBake configuration and the additional things
> we're doing in the custom build process?!
> 
> If someone has a proposal for a JS (or other) SSG that can do the full
> job of what we have now in a standard way then I think it's strongly
> worth considering.  But it needs to be a complete plan.  At my old
> company I did take a brief look at Gatsby, but in the end mostly made
> use of Jekyll due to the better (at the time) client-side CMS options
> - or in other words, there are always other considerations in play!
> :-)
> 
> Best wishes,
> 
> Neil
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: website build system: moving to node/npm?


Thanks, Chris!

So let's await for those "frontend guys" with "> 10 years" of experience 
to build a "common frontend stack" so they can "work on the page" with 
"VuePress, Nuxt, Hugo or Hexo".


Meanwhile let's stick with the "guys working on that page" (no matter 
whether backend or frontend) and let's close PR#375 [1].


As Geertjan suggested, "If it ain't broke, don't fix it...".

Thanks again & kind regards,
Antonio


[1]
https://github.com/apache/netbeans-website/pull/375


El 15/7/19 a las 15:30, Christian Lenz escribió:

We only need frontend guys working on that page and there are a lot of frontend 
guys out there. There is Nothing half baked. Look at Github what they have use a 
more common frontend stack. For me as a frontend developer for > 10 Years, it 
is farly not Java or JBake or JVM whatever. This is not a common frontend stack 
and the case why I didn’t work on the page is exactly that using of the stack.

We don’t Need Java backend guys working on that page. Just a couple of frontend 
guys and I guess david will aslo help here and me too.

My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents.


Cheers

Chris



Von: Neil C Smith
Gesendet: Montag, 15. Juli 2019 12:50
An: dev
Cc: Apache NetBeans
Betreff: Re: website build system: moving to node/npm?

On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga  wrote:


If it ain't broke, don't fix it...

And do we expect lots of people to work on the site just because we switch
from Gradle to Gulp? Do we need lots of people working on the site,
especially since everything's working fine the way it is?


Switching to an equally bespoke and arcane build system in Gulp, no.
Moving to a popular static generator ( https://www.staticgen.com/ )
and using it in a somewhat standard fashion (which we're not with
JBake as I recall) might be a good move to reduce technical debt.

If we did stay JVM, then Orchid might be worth looking into, as it
claims both to support JBake configuration and the additional things
we're doing in the custom build process?!

If someone has a proposal for a JS (or other) SSG that can do the full
job of what we have now in a standard way then I think it's strongly
worth considering.  But it needs to be a complete plan.  At my old
company I did take a brief look at Gatsby, but in the end mostly made
use of Jekyll due to the better (at the time) client-side CMS options
- or in other words, there are always other considerations in play!
:-)

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NetBeans fails to validate web.xml - bug or missing feature?

2019-07-15 Thread Josh Juneau

Hi Thomas,

I cannot reproduce with 11.1 beta 4.  The web.xml does not show a red X.  Have 
you tried with a clean userdir?   Thanks!


Josh Juneau
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866


> On Jul 15, 2019, at 1:40 AM, Thomas Kellerer  wrote:
> 
> Josh,
> 
> it's not a big thing, because everything works even editing the web.xml with 
> the "wizard".
> 
> Only the Projects window shows a little red cross next to the file.
> 
> It's a (very old) Maven project and it's using JavaEE 7
> 
>
>  javax
>  javaee-web-api
>  7.0
>  provided
>
> 
> Regards
> Thomas
> 
> 
> Josh Juneau schrieb am 12.07.2019 um 16:10:
>> Hi Thomas,
>> 
>> There is a PR that has been submitted which may repair these issues.  There
>> is a similar issue that is repaired in the PR which addresses validation of
>> the web-app_4_0.xsd.
>> 
>> Is your project running a very old (pre-Java EE 5) version of Java EE?
>> Even J2EE perhaps?
>> 
>> Thanks
>> 
>>> On Fri, Jul 12, 2019 at 8:48 AM Shammat  wrote:
>>> 
>>> NetBeans 11.1-vc1 fails to alidate a valid web.xml
>>> 
>>> When I open my web.xml from my project and click on the "Validate XML"
>>> button (the two down arrows), it shows the following error message:
>>> 
>>> XML validation started.
>>> Checking file:/C:/**/src/main/webapp/WEB-INF/web.xml...
>>> schema_reference.4: Failed to read schema document
>>> 'nbres:/org/netbeans/modules/j2ee/ddloaders/catalog/resources/web-app_2_4.xsd',
>>> because 1) could not find the document; 2) the document could not be read;
>>> 3) the root element of the document is not . [2]
>>> cvc-elt.1.a: Cannot find the declaration of element 'web-app'. [2]
>>> 
>>> However, the file "web-app_2_4.xsd" is contained in several jar files.
>>> 
>>> It is contained in "org-netbeans-modules-j2ee-dd.jar", but inside that jar
>>> file it's in the package/directory:
>>> 
>>>   org/netbeans/modules/j2ee/dd/impl/resources
>>> 
>>> rather than "org/netbeans/modules/j2ee/ddloaders/catalog/resources" where
>>> the editor seems to expect it.
>>> 
>>> And it's also part of servlet3.1-jsp2.3-api.jar, but there it's in the
>>> package/directory "resources/schemas"
>>> 
>>> Thomas
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
>>> For additional commands, e-mail: dev-h...@netbeans.apache.org
>>> 
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> 
>>> 
>>> 
>>> --
>> Josh Juneau
>> juneau...@gmail.com
>> http://jj-blogger.blogspot.com
>> https://www.apress.com/us/search?query=Juneau
>> 
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
>

Re: Re: HyperlinkProvider::performClickAction won't fire

2019-07-15 Thread Peter Cheung

Thank you Christian. I am too new to the dev community and not familar with 
Jira.

From: Christian Lenz 
Sent: Monday, July 15, 2019 9:21 PM
To: dev@netbeans.apache.org
Subject: AW: Re: HyperlinkProvider::performClickAction won't fire

Hey Peter,

please have a deeper look. If you really mean this bug, it is resolved, yes, 
but for NB 11.1 (See fix Version).

So it is not part of 11 nor with a patch or anything else. It will come with 
NetBeans 11.1

Cheers

Chris

Von: Peter Cheung
Gesendet: Montag, 15. Juli 2019 14:49
An: Apache NetBeans
Betreff: Re: Re: HyperlinkProvider::performClickAction won't fire

Yes. But the bug status is marked resolved, problem still happen in Netbeans 11

Thanks
>From Peter

From: Eric Bresie 
Sent: Saturday, July 13, 2019 8:44 PM
To: Apache NetBeans
Subject: Re: Re: HyperlinkProvider::performClickAction won't fire

Did you mean this https://issues.apache.org/jira/browse/NETBEANS-2343 ?

Eric Bresie
ebre...@gmail.com
> On July 13, 2019 at 3:47:26 AM CDT, Neil C Smith  
> wrote:
> On Sat, 13 Jul 2019 at 09:43, Peter Cheung  wrote:
> >
> > If i ctrl-click on some space/tab position, it fires. It seems netbeans 11 
> > eating the event when i ctrl-click on words. I am not sure.
>
> If this is what I think it is, please try in NB 11.1-beta4 later today.
>
> Thanks,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Re: bits.netbeans.org/maven2 is down?

How huge is huge? 4GB wouldn't be much. 8.x probably the most important anyhow.

--emi

On Mon, Jul 15, 2019 at 3:16 PM Eric Barboni  wrote:
>
> Hi,
>  OSUOSL can host maven repository ?
>  Do not forget that it's huge amount of bits, about 20 version of NetBeans 
> (with everything javaee,c and so on)
>
>  Regards
> Eric
>
> -Message d'origine-
> De : Emilian Bold 
> Envoyé : lundi 15 juillet 2019 09:10
> À : Antonio 
> Cc : dev@netbeans.apache.org
> Objet : Re: bits.netbeans.org/maven2 is down?
>
> Oh, right. OSUOSL seems perfect for this.
>
> --emi
>
> On Mon, Jul 15, 2019 at 10:01 AM Antonio  wrote:
> >
> > This is probably the way to go. We could upload that to OSOUSL and
> > redirect bits.netbeans.org/maven2 to there for the binaries, for instance.
> >
> > Problem being that the Oracle server is currently down, so no way to
> > do a "wget -R".
> >
> > Cheers,
> > Antonio
> >
> > El 15/07/2019 a las 8:57, Emilian Bold escribió:
> > > I could create a mirror of bits.netbeans.org/maven2 on another server.
> > > Any way to download the whole thing easily (wget -R?)?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: website build system: moving to node/npm?

On Mon, 15 Jul 2019 at 14:30, Christian Lenz  wrote:
> My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents.

Well, Hugo would be an odd choice.  If you don't want Java, why would
you pick Go! ;-)

So, put together a migration proposal that handles everything the
current stack has to handle then!  The proposal is half-baked at
present because that doesn't exist.  There is no suggestion of a JBake
replacement or proposal in place to manage migration of content and
config.

And please stop making this some false dichotomy between frontend and
backend developers, or between choice of language of the SSG.  It
isn't one.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

AW: website build system: moving to node/npm?

We only need frontend guys working on that page and there are a lot of frontend 
guys out there. There is Nothing half baked. Look at Github what they have use 
a more common frontend stack. For me as a frontend developer for > 10 Years, it 
is farly not Java or JBake or JVM whatever. This is not a common frontend stack 
and the case why I didn’t work on the page is exactly that using of the stack.

We don’t Need Java backend guys working on that page. Just a couple of frontend 
guys and I guess david will aslo help here and me too.

My proposals are: VuePress, Nuxt, Hugo or Hexo. My 2 cents.

Cheers

Chris

Von: Neil C Smith
Gesendet: Montag, 15. Juli 2019 12:50
An: dev
Cc: Apache NetBeans
Betreff: Re: website build system: moving to node/npm?

On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga  wrote:
>
> If it ain't broke, don't fix it...
>
> And do we expect lots of people to work on the site just because we switch
> from Gradle to Gulp? Do we need lots of people working on the site,
> especially since everything's working fine the way it is?

Switching to an equally bespoke and arcane build system in Gulp, no.
Moving to a popular static generator ( https://www.staticgen.com/ )
and using it in a somewhat standard fashion (which we're not with
JBake as I recall) might be a good move to reduce technical debt.

If we did stay JVM, then Orchid might be worth looking into, as it
claims both to support JBake configuration and the additional things
we're doing in the custom build process?!

If someone has a proposal for a JS (or other) SSG that can do the full
job of what we have now in a standard way then I think it's strongly
worth considering.  But it needs to be a complete plan.  At my old
company I did take a brief look at Gatsby, but in the end mostly made
use of Jekyll due to the better (at the time) client-side CMS options
- or in other words, there are always other considerations in play!
:-)

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Re: HyperlinkProvider::performClickAction won't fire

On Mon, 15 Jul 2019 at 14:22, Christian Lenz  wrote:
> So it is not part of 11 nor with a patch or anything else. It will come with 
> NetBeans 11.1

Oh, yes, missed that.  That bug is marked resolved because it's fixed
in NB 11.1-beta4 - see the beta thread for links if you want to test
early, or wait until the imminent release.  And it might not be
related anyway.

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

AW: Re: HyperlinkProvider::performClickAction won't fire

Hey Peter,

please have a deeper look. If you really mean this bug, it is resolved, yes, 
but for NB 11.1 (See fix Version).

So it is not part of 11 nor with a patch or anything else. It will come with 
NetBeans 11.1

Cheers

Chris

Von: Peter Cheung
Gesendet: Montag, 15. Juli 2019 14:49
An: Apache NetBeans
Betreff: Re: Re: HyperlinkProvider::performClickAction won't fire

Yes. But the bug status is marked resolved, problem still happen in Netbeans 11

Thanks
>From Peter

From: Eric Bresie 
Sent: Saturday, July 13, 2019 8:44 PM
To: Apache NetBeans
Subject: Re: Re: HyperlinkProvider::performClickAction won't fire

Did you mean this https://issues.apache.org/jira/browse/NETBEANS-2343 ?

Eric Bresie
ebre...@gmail.com
> On July 13, 2019 at 3:47:26 AM CDT, Neil C Smith  
> wrote:
> On Sat, 13 Jul 2019 at 09:43, Peter Cheung  wrote:
> >
> > If i ctrl-click on some space/tab position, it fires. It seems netbeans 11 
> > eating the event when i ctrl-click on words. I am not sure.
>
> If this is what I think it is, please try in NB 11.1-beta4 later today.
>
> Thanks,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Re: Re: HyperlinkProvider::performClickAction won't fire

On Mon, 15 Jul 2019 at 13:49, Peter Cheung  wrote:
> Yes. But the bug status is marked resolved, problem still happen in Netbeans 
> 11

In which case, it's a different bug!  Sorry about that, just wondered
if the causes were related.

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: bits.netbeans.org/maven2 is down?

2019-07-15 Thread Geertjan Wielenga

I have a feeling that we should leave bits.netbeans.org/maven2 down, see
who complains, then see what they actually need from there, and then see
whether that makes it worth it to try to get bits.netbeans.org/maven2 up
again or whether the bits that are actually needed -- which could be a
small subset -- can be hosted somewhere else under our control.

Gj

On Mon, Jul 15, 2019 at 2:16 PM Eric Barboni  wrote:

> Hi,
>  OSUOSL can host maven repository ?
>  Do not forget that it's huge amount of bits, about 20 version of NetBeans
> (with everything javaee,c and so on)
>
>  Regards
> Eric
>
> -Message d'origine-
> De : Emilian Bold 
> Envoyé : lundi 15 juillet 2019 09:10
> À : Antonio 
> Cc : dev@netbeans.apache.org
> Objet : Re: bits.netbeans.org/maven2 is down?
>
> Oh, right. OSUOSL seems perfect for this.
>
> --emi
>
> On Mon, Jul 15, 2019 at 10:01 AM Antonio  wrote:
> >
> > This is probably the way to go. We could upload that to OSOUSL and
> > redirect bits.netbeans.org/maven2 to there for the binaries, for
> instance.
> >
> > Problem being that the Oracle server is currently down, so no way to
> > do a "wget -R".
> >
> > Cheers,
> > Antonio
> >
> > El 15/07/2019 a las 8:57, Emilian Bold escribió:
> > > I could create a mirror of bits.netbeans.org/maven2 on another server.
> > > Any way to download the whole thing easily (wget -R?)?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Re: HyperlinkProvider::performClickAction won't fire

2019-07-15 Thread Peter Cheung

Yes. But the bug status is marked resolved, problem still happen in Netbeans 11


Thanks
>From Peter

From: Eric Bresie 
Sent: Saturday, July 13, 2019 8:44 PM
To: Apache NetBeans
Subject: Re: Re: HyperlinkProvider::performClickAction won't fire

Did you mean this https://issues.apache.org/jira/browse/NETBEANS-2343 ?

Eric Bresie
ebre...@gmail.com
> On July 13, 2019 at 3:47:26 AM CDT, Neil C Smith  
> wrote:
> On Sat, 13 Jul 2019 at 09:43, Peter Cheung  wrote:
> >
> > If i ctrl-click on some space/tab position, it fires. It seems netbeans 11 
> > eating the event when i ctrl-click on words. I am not sure.
>
> If this is what I think it is, please try in NB 11.1-beta4 later today.
>
> Thanks,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

RE: bits.netbeans.org/maven2 is down?

2019-07-15 Thread Eric Barboni

Hi,
 OSUOSL can host maven repository ? 
 Do not forget that it's huge amount of bits, about 20 version of NetBeans 
(with everything javaee,c and so on)
 
 Regards
Eric

-Message d'origine-
De : Emilian Bold  
Envoyé : lundi 15 juillet 2019 09:10
À : Antonio 
Cc : dev@netbeans.apache.org
Objet : Re: bits.netbeans.org/maven2 is down?

Oh, right. OSUOSL seems perfect for this.

--emi

On Mon, Jul 15, 2019 at 10:01 AM Antonio  wrote:
>
> This is probably the way to go. We could upload that to OSOUSL and 
> redirect bits.netbeans.org/maven2 to there for the binaries, for instance.
>
> Problem being that the Oracle server is currently down, so no way to 
> do a "wget -R".
>
> Cheers,
> Antonio
>
> El 15/07/2019 a las 8:57, Emilian Bold escribió:
> > I could create a mirror of bits.netbeans.org/maven2 on another server.
> > Any way to download the whole thing easily (wget -R?)?

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Re: website build system: moving to node/npm?

2019-07-15 Thread Eric Bresie

Maybe a step back and ask
- what is the scope of this?
— what content of the website is covered by this?
— what issue/problem is being overcome?
- what is the ideal end objective?

Eric Bresie
ebre...@gmail.com
> On July 15, 2019 at 5:50:15 AM CDT, Neil C Smith  
> wrote:
> On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga  wrote:
> >
> > If it ain't broke, don't fix it...
> >
> > And do we expect lots of people to work on the site just because we switch
> > from Gradle to Gulp? Do we need lots of people working on the site,
> > especially since everything's working fine the way it is?
>
> Switching to an equally bespoke and arcane build system in Gulp, no.
> Moving to a popular static generator ( https://www.staticgen.com/ )
> and using it in a somewhat standard fashion (which we're not with
> JBake as I recall) might be a good move to reduce technical debt.
>
> If we did stay JVM, then Orchid might be worth looking into, as it
> claims both to support JBake configuration and the additional things
> we're doing in the custom build process?!
>
> If someone has a proposal for a JS (or other) SSG that can do the full
> job of what we have now in a standard way then I think it's strongly
> worth considering. But it needs to be a complete plan. At my old
> company I did take a brief look at Gatsby, but in the end mostly made
> use of Jekyll due to the better (at the time) client-side CMS options
> - or in other words, there are always other considerations in play!
> :-)
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Re: website build system: moving to node/npm?

On Mon, 15 Jul 2019 at 11:07, Geertjan Wielenga  wrote:
>
> If it ain't broke, don't fix it...
>
> And do we expect lots of people to work on the site just because we switch
> from Gradle to Gulp? Do we need lots of people working on the site,
> especially since everything's working fine the way it is?

Switching to an equally bespoke and arcane build system in Gulp, no.
Moving to a popular static generator ( https://www.staticgen.com/ )
and using it in a somewhat standard fashion (which we're not with
JBake as I recall) might be a good move to reduce technical debt.

If we did stay JVM, then Orchid might be worth looking into, as it
claims both to support JBake configuration and the additional things
we're doing in the custom build process?!

If someone has a proposal for a JS (or other) SSG that can do the full
job of what we have now in a standard way then I think it's strongly
worth considering.  But it needs to be a complete plan.  At my old
company I did take a brief look at Gatsby, but in the end mostly made
use of Jekyll due to the better (at the time) client-side CMS options
- or in other words, there are always other considerations in play!
:-)

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: website build system: moving to node/npm?


I think we need lots of people working on the content, not on the tool :-)

El 15/07/2019 a las 12:07, Geertjan Wielenga escribió:

If it ain't broke, don't fix it...

And do we expect lots of people to work on the site just because we switch
from Gradle to Gulp? Do we need lots of people working on the site,
especially since everything's working fine the way it is?

Gj

On Mon, Jul 15, 2019 at 12:05 PM Neil C Smith  wrote:


On Mon, 15 Jul 2019 at 10:51, Antonio  wrote:

a) Keep the gradle build system, or
b) Rebuild the website build system using node/npm.

Opinions? Any other thoughts? Wishes?


Most immediate question would be what's the proposed replacement for
the JBake part of this?

Initial thought is the proposal is somewhat half-baked at present! :-)
  Sorry, couldn't resist!

A simplified stack that more people understand would be good though.
Whether that is a switch from JVM to JS static site generation or
another SSG stack really depends on preferences and skills of our
community though, IMO.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists








-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Windows nightlies

On Mon, 15 Jul 2019 at 10:41, Emilian Bold  wrote:
>
> But, what does 
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-windows/
> do? Is the -linux / -windows suffice the build server type or the
> target platform type.

Build server.

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

website build system: moving to node/npm?


Hi all,

We're received a PR [1] for the website that builds the CSS (from SCSS) 
using "gulp" [2].


As you may know the current website build system uses "gradle", "jbake" 
and "asciidoctorj", and was originally built to support many different 
formats (html/markdown/asciidoc) with metadata either embedded in the 
content file (asciidoc files) or with companion files (html, markdown).


There's a discussion in the PR [2] that proposes to either:

a) Keep the gradle build system, or
b) Rebuild the website build system using node/npm.

Opinions? Any other thoughts? Wishes?

Thanks,
Antonio

[1]
https://github.com/apache/netbeans-website/pull/375

[2]
https://gulpjs.com/

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Windows nightlies

But, what does 
https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-windows/
do? Is the -linux / -windows suffice the build server type or the
target platform type. I can see this being confusing although this
stuff isn't for public consumption.

--emi

On Mon, Jul 15, 2019 at 12:17 PM Neil C Smith  wrote:
>
> On Mon, 15 Jul 2019 at 10:04, Christian Lenz  wrote:
> >
> > Well, because of it is strange and people doesn’t understand it and asking 
> > for it, we should change it. Just saying.
>
> Then put a PR in to change the website?
>
> The name of the Jenkins task itself isn't strange.  Having both on the
> website at http://netbeans.apache.org/download/ under Daily Builds is.
> Shouldn't there just be one daily builds link that goes to
> https://builds.apache.org/job/netbeans-linux/lastSuccessfulBuild/artifact/
> ?
>
> Although, that section will move a little once NB 11.1 is out, and we
> might need a bit more of a disclaimer on the link from an Apache point
> of view.
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Thanks for not deleting javaee.wildfly

Are you doing this in the release111 branch or on master? Having on
release111 would be convenient...

--emi

On Mon, Jul 15, 2019 at 11:43 AM ehsavoie  wrote:
>
> Hello,
> I'm working into updating the schemas in the contrib part.
> Currently I'm trying to remove the old DTDs to have only ASL 2.0 schemas.
> It should be useable in 11.1 as it builds currently but can't be included
> afaik directly.
> Cheers,
> Emmanuel
> --
> Emmanuel Hugonnet
> http://www.ehsavoie.com
> http://twitter.com/ehsavoie
>
>
> On Sat, Jul 13, 2019 at 10:07 AM Emilian Bold 
> wrote:
>
> > Hello,
> >
> > I see that initially javaee.wildfly was just removed from
> > cluster.properties but it was still in place. It was easy to re-add.
> >
> > Now it has been moved to contrib. This is still OK as at least the
> > code is in the repository.
> >
> > We should probably do the same for beansbinding and some other modules
> > that got removed originally due to touching GPL code... Having them in
> > contrib/ is better then having them in random GitHub projects.
> >
> > --emi
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Windows nightlies

On Mon, 15 Jul 2019 at 10:04, Christian Lenz  wrote:
>
> Well, because of it is strange and people doesn’t understand it and asking 
> for it, we should change it. Just saying.

Then put a PR in to change the website?

The name of the Jenkins task itself isn't strange.  Having both on the
website at http://netbeans.apache.org/download/ under Daily Builds is.
Shouldn't there just be one daily builds link that goes to
https://builds.apache.org/job/netbeans-linux/lastSuccessfulBuild/artifact/
?

Although, that section will move a little once NB 11.1 is out, and we
might need a bit more of a disclaimer on the link from an Apache point
of view.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

AW: Windows nightlies

Well, because of it is strange and people doesn’t understand it and asking for 
it, we should change it. Just saying.

Cheers

Chris

Von: Laszlo Kishalmi
Gesendet: Freitag, 12. Juli 2019 19:36
An: dev@netbeans.apache.org
Betreff: Re: Windows nightlies

Use the binaries built on linux!

Well I know it is strange, but we build the windows binaries (exe-s) on 
Linux (with mingw) from the source. On Windows they are using the 9.0 
version (AFAIK). We had a number of fixes since that.

On 7/12/19 7:57 AM, Jake Ochs wrote:
> I see the Linux nightly binaries are available as binaries from Jenkins. How 
> can I get the Windows nightly binaries?
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Thanks for not deleting javaee.wildfly

2019-07-15 Thread ehsavoie

Hello,
I'm working into updating the schemas in the contrib part.
Currently I'm trying to remove the old DTDs to have only ASL 2.0 schemas.
It should be useable in 11.1 as it builds currently but can't be included
afaik directly.
Cheers,
Emmanuel
--
Emmanuel Hugonnet
http://www.ehsavoie.com
http://twitter.com/ehsavoie


On Sat, Jul 13, 2019 at 10:07 AM Emilian Bold 
wrote:

> Hello,
>
> I see that initially javaee.wildfly was just removed from
> cluster.properties but it was still in place. It was easy to re-add.
>
> Now it has been moved to contrib. This is still OK as at least the
> code is in the repository.
>
> We should probably do the same for beansbinding and some other modules
> that got removed originally due to touching GPL code... Having them in
> contrib/ is better then having them in random GitHub projects.
>
> --emi
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Apache NetBeans 11.1-beta4 Is Available for Testing!

2019-07-15 Thread Laszlo Kishalmi


Dear all,

I've spent the weekend driving between California and Oregon and fixing 
our production issues, so catching up now.
I've just pressed the button on the Snap build it will be available in 
an hour. You might to force the refresh to get it.

sudo snap refresh netbeans

Also I'd like to encourage you to test the source distribution, try to 
build it, start it with and without an empty user dir. Snaps are really 
convenient, but that's not our official release.


@Neil you can push that button as well: 
https://builds.apache.org/job/netbeans-snap-release/ the only parameter 
to the build is the number of the release build. Which is as of now: 426


On 7/14/19 2:47 AM, huang kai wrote:

I do the test though linux snap build, but it seems the beta 4 haven't
arrive snap store --edge channel yet, so I have to download the binaries
manually. VC1 download is as slow as beta 4. BTW, the download link from
netbeans.apache.com is super fast.


On 2019/7/14 17:40, Neil C Smith wrote:

On Sun, 14 Jul 2019, 10:26 huang kai,  wrote:


Are there any mirror to download the build artiffacts? It is too slow to
download the binaries here in china, about 15-30KB/s. Any help will be
appreciated.


Unfortunately not that I know of. For the last few releases we've linked
betas directly from the build server.

Did you try vc1? And did that download quicker? As far as I know, the
dist/dev server isn't mirrored either, but if it's quicker we may need to
consider using it for betas again in future. Unfortunately that will add
some work to producing betas.

Best wishes,

Neil



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: bits.netbeans.org/maven2 is down?

Oh, right. OSUOSL seems perfect for this.

--emi

On Mon, Jul 15, 2019 at 10:01 AM Antonio  wrote:
>
> This is probably the way to go. We could upload that to OSOUSL and
> redirect bits.netbeans.org/maven2 to there for the binaries, for instance.
>
> Problem being that the Oracle server is currently down, so no way to do
> a "wget -R".
>
> Cheers,
> Antonio
>
> El 15/07/2019 a las 8:57, Emilian Bold escribió:
> > I could create a mirror of bits.netbeans.org/maven2 on another server.
> > Any way to download the whole thing easily (wget -R?)?

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: bits.netbeans.org/maven2 is down?

This is probably the way to go. We could upload that to OSOUSL and 
redirect bits.netbeans.org/maven2 to there for the binaries, for instance.


Problem being that the Oracle server is currently down, so no way to do 
a "wget -R".


Cheers,
Antonio

El 15/07/2019 a las 8:57, Emilian Bold escribió:

I could create a mirror of bits.netbeans.org/maven2 on another server.
Any way to download the whole thing easily (wget -R?)?


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: bits.netbeans.org/maven2 is down?