Conventions for vote email threads closure

[Ate Douma]

I noticed that several vote threads recently were 'cancelled' implicitly
without explicit conclusion by the release manager.
Or accepted (like below), without clear heads-up stating the result.

The convention is that the release manager sends a final reply with
subject prefix [RESULT][VOTE], with a clear tally of the vote counts.

And the convention is also that the release manager sends a final replay
with subject prefix [CANCELLED][VOTE], otherwise.

Thanks,
Ate

On 27/11/2018 06.10, Jaroslav Tulach wrote:

On 2018/11/23 17:36:27, Jaroslav Tulach  wrote:

Thank you Justin and Ate for your votes. Now we are +2 binding, but I guess
I still need one more, right?
Anyone else willing to cast another  +1 binding vote?>


Bertrand voted +1 on Monday.

Votes by Justin, Ate and Bertrand make me believe the release 1.6 of NetBeans
HTML/Java API has been approved. I perform necessary release actions over the
weekend


Good!



Thank you for your reviews.
-jt


I've reported https://issues.apache.org/jira/browse/NETBEANS-1739 to track

the >

issues found by Justin. I'll keep that in mind and fix it by next release. >
Thanks for the findings.>

-jt>

On 2018/11/21 05:00:56, Justin Mclean  wrote: >

Hi,> >



+1 binding but there’s a LICENSE issue than needs to be fixed in the next


release.> >



I checkered:> >
- incubating in name> >
- signatures and hashes correct> >
- DISCLAIMER exists (although name of the project inside is a little odd)>



- LICENSE and NOTICE have a few minor issues (see below)> >
- No unexpected binary files> >
- All ASF file have ASF headers> >
- Can compile from source> >



The tests also passed.> >



The NOTICE copyright year is “2017-2017” that should be 2017-2018 right?>





The LICENSE is missing mention of (and license text) of MIT licensed >

Knockout [1]> >



Thanks,> >
Justin> >



1. incubator-netbeans-html4j/ko4j/src/main/resources/org/netbeans/html/

ko4j/>

knockout-3.4.0.js> >






-> >
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org> >
For additional commands, e-mail: general-h...@incubator.apache.org> >







->
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org>
For additional commands, e-mail: general-h...@incubator.apache.org>






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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

Re: module source location..

[John McDonnell]

Hi Brad,

Have a look at [1], this page tracks the Apache Transition steps.  The CND
modules are part of the forth code donation, I don't think there is an
estimated ETA, as it looks like it's going to be done after the
documentation donation is complete, and then it would have to be reviewed
by Oracle for any license issues, etc.


[1]: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition


Regards

John

On Tue, 27 Nov 2018 at 03:48, Brad Walker  wrote:

> I realize that Netbeans is still in the incubator stage and therefore
> modules might be getting less attention.
>
> As I'm  new to the IDE platform, can someone point me to where I might find
> the source to the CND module. This module is the C/C++ one.
>
> I've tried to track down the old source from the svn.netbeans.org site.
> But, I can't seem to find it there.
>
> Any suggestions are welcome..
>
> Thanks.
>
> -brad w.
>

Re: [RESULT] Release 1.6 of NetBeans HTML/Java API

[Jaroslav Tulach]

On 2018/11/23 17:36:27, Jaroslav Tulach  wrote: 
> Thank you Justin and Ate for your votes. Now we are +2 binding, but I guess
> I still need one more, right? 
> Anyone else willing to cast another  +1 binding vote?> 

Bertrand voted +1 on Monday.

Votes by Justin, Ate and Bertrand make me believe the release 1.6 of NetBeans 
HTML/Java API has been approved. I perform necessary release actions over the 
weekend.

Thank you for your reviews.
-jt

> I've reported https://issues.apache.org/jira/browse/NETBEANS-1739 to track 
the > 
> issues found by Justin. I'll keep that in mind and fix it by next release. > 
> Thanks for the findings.> 
> 
> -jt> 
> 
> On 2018/11/21 05:00:56, Justin Mclean  wrote: > 
> > Hi,> > 
> > > 
> > +1 binding but there’s a LICENSE issue than needs to be fixed in the next 
> 
> release.> > 
> > > 
> > I checkered:> > 
> > - incubating in name> > 
> > - signatures and hashes correct> > 
> > - DISCLAIMER exists (although name of the project inside is a little odd)> 
> 
> > - LICENSE and NOTICE have a few minor issues (see below)> > 
> > - No unexpected binary files> > 
> > - All ASF file have ASF headers> > 
> > - Can compile from source> > 
> > > 
> > The tests also passed.> > 
> > > 
> > The NOTICE copyright year is “2017-2017” that should be 2017-2018 right?> 
> 
> > > 
> > The LICENSE is missing mention of (and license text) of MIT licensed > 
> Knockout [1]> > 
> > > 
> > Thanks,> > 
> > Justin> > 
> > > 
> > 1. incubator-netbeans-html4j/ko4j/src/main/resources/org/netbeans/html/
ko4j/> 
> knockout-3.4.0.js> > 
> > > 
> > > 
> > > 
> > > 
> > -> > 
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org> > 
> > For additional commands, e-mail: general-h...@incubator.apache.org> > 
> > > 
> > > 
> 
> 
> 
> -> 
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org> 
> For additional commands, e-mail: general-h...@incubator.apache.org> 
> 
> 



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

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

module source location..

[Brad Walker]

I realize that Netbeans is still in the incubator stage and therefore
modules might be getting less attention.

As I'm  new to the IDE platform, can someone point me to where I might find
the source to the CND module. This module is the C/C++ one.

I've tried to track down the old source from the svn.netbeans.org site.
But, I can't seem to find it there.

Any suggestions are welcome..

Thanks.

-brad w.

Re: 10-vc5

[John McDonnell]

A less serious issue to some mentioned, but [1] will additional support for
parameterized tests for JUnit 5.

Regards

John

On Sat, 24 Nov 2018 at 18:52, Matthias Bläsing 
wrote:

> Hi,
>
> Am Samstag, den 24.11.2018, 10:35 -0800 schrieb Laszlo Kishalmi:
> > Hi all PR-973 broke HTML5, PHP. Going to revert the patch from
> > release100
>
> please wait and give Svatopluk some time to react - else I see the next
> one voting -1 because the old Javascript parser is bundled (with GPLv2-
> CPE license...)
>
> Greetings
>
> Matthias
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: 10-vc5

[John McDonnell]

Apologies...
[1] refers to https://github.com/apache/incubator-netbeans/pull/1019 :)

On Mon, 26 Nov 2018 at 21:43, John McDonnell 
wrote:

> A less serious issue to some mentioned, but [1] will additional support
> for parameterized tests for JUnit 5.
>
> Regards
>
> John
>
> On Sat, 24 Nov 2018 at 18:52, Matthias Bläsing 
> wrote:
>
>> Hi,
>>
>> Am Samstag, den 24.11.2018, 10:35 -0800 schrieb Laszlo Kishalmi:
>> > Hi all PR-973 broke HTML5, PHP. Going to revert the patch from
>> > release100
>>
>> please wait and give Svatopluk some time to react - else I see the next
>> one voting -1 because the old Javascript parser is bundled (with GPLv2-
>> CPE license...)
>>
>> Greetings
>>
>> Matthias
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>

Re: Are we working from "release" branches or from master ahead of a release? I think Jenkins suggests "release*" is the case. Now wondering processes etc.

[Geertjan Wielenga]

We put changes into the main branch, then cherry pick those that are needed
in the release branch.

Thanks,

Gj

On Mon, Nov 26, 2018 at 5:01 PM Wade Chandler 
wrote:

> Hey all. I was building from master recently, and had various
> issues/exceptions, and of course know we have a vote on 10 going on.
> Knowing NetBeans past, I looked for the release branches, and saw branch
> release100 out there. I wasn’t sure the current process as I had been out
> of touch for a while (work and all).
>
> Is the idea to create a release branch, and then work there when we get
> “close” to shooting for a release? Too, how are we keeping items synced up
> between master and release* after we we start that process if so? Maybe
> even a link will work if the process is documented. I’m assuming changes in
> both master and release for the near term, so just looking for guidance.
>
> Jenkins suggests yes on the release branch, but not sure the rest
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/configure
> <
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/configure>
>
>
> Thanks much,
>
> Wade
>
> ===
>
> Wade Chandler
> e: cons...@wadechandler.com
> t: @wadechandler
> https://www.linkedin.com/in/wade-chandler
>
>
>
>

Re: another netbeans warning..

[Emilian Bold]

These are "ok". Same category I mentioned in the other email.

--emi

On Mon, Nov 26, 2018 at 9:51 PM Brad Walker  wrote:
>
> Here is another netbeans warning..
>
> Does this look familiar?
>
> I'm actively using the C/C++ module in Netbeans and I'm aware that it is
> not "fully supported" yet. But, I would be happy to help since I use this
> as part of my day-to-day work..
>
> -brad w.
>
> ...
>org.apache.commons.lang [2.6 2.6]
> com.jcraft.jzlib [1.0.7 1.0.7]
> com.googlecode.javaewah.JavaEWAH [0.7.9 0.7.9]
> com.google.guava [15.0.0 15.0.0]
> INFO [org.netbeans.core.netigso.Netigso]: bundle
> org.eclipse.osgi@3.9.1.v20140110-1610 started
> INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
> proxy resolver: no suitable found, using fallback.
> INFO [org.netbeans.core.network.proxy.fallback.FallbackNetworkProxy]:
> Fallback system proxy resolver: no http_proxy variable found
> INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
> proxy reloading succeeded.
> INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
> proxy - mode: direct
> INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
> proxy: fell to default (correct if direct mode went before)
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.netbeans.core.windows.view.ui.MainWindow
> (jar:file:/home/bwalker/netbeans-9.0/platform/modules/org-netbeans-core-windows.jar!/)
> to field sun.awt.X11.XToolkit.awtAppClassName
> WARNING: Please consider reporting this to the maintainers of
> org.netbeans.core.windows.view.ui.MainWindow
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> INFO [org.netbeans.modules.cnd.utils.cache.CndFileUtils]: C/C++ File Utils:
> using case-sensitive file system
> WARNING [org.netbeans.TopSecurityManager]: use of system property
> netbeans.home has been obsoleted in favor of InstalledFileLocator/Places at
> org.netbeans.modules.java.j2seplatform.platformdefinition.Util.removeNBArtifacts(Util.java:337)
> WARNING [org.netbeans.TopSecurityManager]: use of system property
> netbeans.user has been obsoleted in favor of InstalledFileLocator/Places at
> org.netbeans.modules.nativeexecution.support.hostinfo.impl.HostInfoFactory.getNBKey(HostInfoFactory.java:394)
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Resolving dependencies took: 2 ms
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Complete indexing of 0 binary roots took: 0 ms
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Complete indexing of 0 source roots took: 0 ms (New or modified files: 0,
> Deleted files: 0) [Adding listeners took: 0 ms]
> Configuration updated:
> 0 deleted items
> ...

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

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

Re: netbeans warning..

[Brad Walker]

Thanks!

I did make that change and it fixed that issue for me..

-brad w.


On Mon, Nov 26, 2018 at 11:16 AM Matthias Bläsing 
wrote:

> Hi,
>
> Am Montag, den 26.11.2018, 19:51 +0200 schrieb Emilian Bold:
> > * at least one warning seems interesting and a potential bug:
> >
> > > WARNING [nativeexecution.support.logger]: [931 ms.]
> > > UnixHostInfoProvider:
> > > sed: -e expression #1, char 6: unterminated `s' command
>
> Agreed, that would be:
>
> https://issues.apache.org/jira/browse/NETBEANS-1727
>
> with
>
> https://github.com/apache/incubator-netbeans/pull/1028
>
> Greetings
>
> Matthias
>

Re: netbeans warning..

[Brad Walker]

I'm more of a user of Netbeans vs. a developer of the IDE. Having said
that, I could possibly fix a deprecation warning or two if I had a little
bit of insight/help from others.

I also agree with your comments about WARNING..

-brad w.

On Mon, Nov 26, 2018 at 10:52 AM Emilian Bold 
wrote:

> Oddly enough I was just tweeting today that we could easily fix some
> of these 'WARNING' messages.
>
> I think we are abusing them and confusing users in the process.
>
> Normally each such WARNING should have meaning and getting one should
> be interesting information.
>
> From the looks of it:
>
> * a few warnings are minor deprecation warnings in our own code which
> we should either fix or just not print the warning (whitelist)
>
> * a few warning are due to the Java 9 module system. I doubt we can
> ever get right of those illegal reflective access we want since there
> probably are no APIs for that stuff. Here having some whitelist and
> just not print stuff would help reduce the load on users.
>
> * at least one warning seems interesting and a potential bug:
>
> > WARNING [nativeexecution.support.logger]: [931 ms.] UnixHostInfoProvider:
> > sed: -e expression #1, char 6: unterminated `s' command
>
> --emi
> On Mon, Nov 26, 2018 at 6:33 PM Brad Walker  wrote:
> >
> > I'm using Apache Netbeans 9.0 to do a bunch of C/C++ development. I see
> > this warning when starting up and thought I might bring it to your
> > attention.
> >
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.netbeans.core.windows.view.ui.MainWindow
> >
> (jar:file:/home/bwalker/netbeans-9.0/platform/modules/org-netbeans-core-windows.jar!/)
> > to field sun.awt.X11.XToolkit.awtAppClassName
> > WARNING: Please consider reporting this to the maintainers of
> > org.netbeans.core.windows.view.ui.MainWindow
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > INFO [org.netbeans.modules.cnd.utils.cache.CndFileUtils]: C/C++ File
> Utils:
> > using case-sensitive file system
> > WARNING [org.netbeans.TopSecurityManager]: use of system property
> > netbeans.home has been obsoleted in favor of InstalledFileLocator/Places
> at
> >
> org.netbeans.modules.java.j2seplatform.platformdefinition.Util.removeNBArtifacts(Util.java:337)
> > INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> > Resolving dependencies took: 5 ms
> > INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> > Complete indexing of 0 binary roots took: 0 ms
> > INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> > Complete indexing of 0 source roots took: 0 ms (New or modified files: 0,
> > Deleted files: 0) [Adding listeners took: 0 ms]
> > WARNING [org.netbeans.TopSecurityManager]: use of system property
> > netbeans.user has been obsoleted in favor of InstalledFileLocator/Places
> at
> >
> org.netbeans.modules.nativeexecution.support.hostinfo.impl.HostInfoFactory.getNBKey(HostInfoFactory.java:394)
> > WARNING [nativeexecution.support.logger]: [931 ms.] UnixHostInfoProvider:
> > sed: -e expression #1, char 6: unterminated `s' command
> >
> > I would assume this is something that I can ignore. But, did think you
> > should know about it.
> >
> > -brad w.
>
>

another netbeans warning..

[Brad Walker]

Here is another netbeans warning..

Does this look familiar?

I'm actively using the C/C++ module in Netbeans and I'm aware that it is
not "fully supported" yet. But, I would be happy to help since I use this
as part of my day-to-day work..

-brad w.

...
   org.apache.commons.lang [2.6 2.6]
com.jcraft.jzlib [1.0.7 1.0.7]
com.googlecode.javaewah.JavaEWAH [0.7.9 0.7.9]
com.google.guava [15.0.0 15.0.0]
INFO [org.netbeans.core.netigso.Netigso]: bundle
org.eclipse.osgi@3.9.1.v20140110-1610 started
INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
proxy resolver: no suitable found, using fallback.
INFO [org.netbeans.core.network.proxy.fallback.FallbackNetworkProxy]:
Fallback system proxy resolver: no http_proxy variable found
INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
proxy reloading succeeded.
INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
proxy - mode: direct
INFO [org.netbeans.core.network.proxy.NetworkProxyReloader]: System network
proxy: fell to default (correct if direct mode went before)
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.netbeans.core.windows.view.ui.MainWindow
(jar:file:/home/bwalker/netbeans-9.0/platform/modules/org-netbeans-core-windows.jar!/)
to field sun.awt.X11.XToolkit.awtAppClassName
WARNING: Please consider reporting this to the maintainers of
org.netbeans.core.windows.view.ui.MainWindow
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
INFO [org.netbeans.modules.cnd.utils.cache.CndFileUtils]: C/C++ File Utils:
using case-sensitive file system
WARNING [org.netbeans.TopSecurityManager]: use of system property
netbeans.home has been obsoleted in favor of InstalledFileLocator/Places at
org.netbeans.modules.java.j2seplatform.platformdefinition.Util.removeNBArtifacts(Util.java:337)
WARNING [org.netbeans.TopSecurityManager]: use of system property
netbeans.user has been obsoleted in favor of InstalledFileLocator/Places at
org.netbeans.modules.nativeexecution.support.hostinfo.impl.HostInfoFactory.getNBKey(HostInfoFactory.java:394)
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Resolving dependencies took: 2 ms
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Complete indexing of 0 binary roots took: 0 ms
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Complete indexing of 0 source roots took: 0 ms (New or modified files: 0,
Deleted files: 0) [Adding listeners took: 0 ms]
Configuration updated:
0 deleted items
...

Re: netbeans warning..

[Emilian Bold]

:-)

--emi

On Mon, Nov 26, 2018 at 8:16 PM Matthias Bläsing
 wrote:
>
> Hi,
>
> Am Montag, den 26.11.2018, 19:51 +0200 schrieb Emilian Bold:
> > * at least one warning seems interesting and a potential bug:
> >
> > > WARNING [nativeexecution.support.logger]: [931 ms.]
> > > UnixHostInfoProvider:
> > > sed: -e expression #1, char 6: unterminated `s' command
>
> Agreed, that would be:
>
> https://issues.apache.org/jira/browse/NETBEANS-1727
>
> with
>
> https://github.com/apache/incubator-netbeans/pull/1028
>
> Greetings
>
> Matthias
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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

Re: netbeans warning..

[Matthias Bläsing]

Hi,

Am Montag, den 26.11.2018, 19:51 +0200 schrieb Emilian Bold:
> * at least one warning seems interesting and a potential bug:
> 
> > WARNING [nativeexecution.support.logger]: [931 ms.]
> > UnixHostInfoProvider:
> > sed: -e expression #1, char 6: unterminated `s' command

Agreed, that would be:

https://issues.apache.org/jira/browse/NETBEANS-1727

with

https://github.com/apache/incubator-netbeans/pull/1028

Greetings

Matthias


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

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

Re: netbeans warning..

[Emilian Bold]

Oddly enough I was just tweeting today that we could easily fix some
of these 'WARNING' messages.

I think we are abusing them and confusing users in the process.

Normally each such WARNING should have meaning and getting one should
be interesting information.

>From the looks of it:

* a few warnings are minor deprecation warnings in our own code which
we should either fix or just not print the warning (whitelist)

* a few warning are due to the Java 9 module system. I doubt we can
ever get right of those illegal reflective access we want since there
probably are no APIs for that stuff. Here having some whitelist and
just not print stuff would help reduce the load on users.

* at least one warning seems interesting and a potential bug:

> WARNING [nativeexecution.support.logger]: [931 ms.] UnixHostInfoProvider:
> sed: -e expression #1, char 6: unterminated `s' command

--emi
On Mon, Nov 26, 2018 at 6:33 PM Brad Walker  wrote:
>
> I'm using Apache Netbeans 9.0 to do a bunch of C/C++ development. I see
> this warning when starting up and thought I might bring it to your
> attention.
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.netbeans.core.windows.view.ui.MainWindow
> (jar:file:/home/bwalker/netbeans-9.0/platform/modules/org-netbeans-core-windows.jar!/)
> to field sun.awt.X11.XToolkit.awtAppClassName
> WARNING: Please consider reporting this to the maintainers of
> org.netbeans.core.windows.view.ui.MainWindow
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> INFO [org.netbeans.modules.cnd.utils.cache.CndFileUtils]: C/C++ File Utils:
> using case-sensitive file system
> WARNING [org.netbeans.TopSecurityManager]: use of system property
> netbeans.home has been obsoleted in favor of InstalledFileLocator/Places at
> org.netbeans.modules.java.j2seplatform.platformdefinition.Util.removeNBArtifacts(Util.java:337)
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Resolving dependencies took: 5 ms
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Complete indexing of 0 binary roots took: 0 ms
> INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
> Complete indexing of 0 source roots took: 0 ms (New or modified files: 0,
> Deleted files: 0) [Adding listeners took: 0 ms]
> WARNING [org.netbeans.TopSecurityManager]: use of system property
> netbeans.user has been obsoleted in favor of InstalledFileLocator/Places at
> org.netbeans.modules.nativeexecution.support.hostinfo.impl.HostInfoFactory.getNBKey(HostInfoFactory.java:394)
> WARNING [nativeexecution.support.logger]: [931 ms.] UnixHostInfoProvider:
> sed: -e expression #1, char 6: unterminated `s' command
>
> I would assume this is something that I can ignore. But, did think you
> should know about it.
>
> -brad w.

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

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

Re: NetBeans Platform 9

[Christian Bourque]

Hi Jean-Marc,

This is very interesting thanks a lot! I'll give it a shot for sure!

Christian

On Mon, Nov 26, 2018 at 4:51 AM Jean-Marc Borer  wrote:

> Hi Christian,
>
> I recently did it myself. You need to download and compile the deploy
> plugin yourself, because I could not find it on central or elsewhere. Get
> it from :
>
>
> https://github.com/apache/incubator-netbeans-mavenutils/tree/master/nb-repository-plugin
>
> Then go the sources you have cloned from
> https://github.com/apache/incubator-netbeans and do:
>
> ant
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:download
> -DnexusIndexDirectory=..\nbrepoidx
> -DrepositoryUrl=https://repo.maven.apache.org/maven2ant build-nbms
> ant build-source-zips
> ant build-javadoc
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
> -DnexusIndexDirectory=..\nbrepoidx -DforcedVersion=RELEASE90
> -DnetbeansInstallDirectory=nbbuild\netbeans
> -DnetbeansNbmDirectory=nbbuild\nbms
> -DnetbeansSourcesDirectory=nbbuild\build\source-zips
> -DnetbeansJavadocDirectory=nbbuild\build\javadoc
>
>
>
> Above it is for a local deployment of the artifacts. If you want to deploy
> the artifacts into your own repository:
>
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
> -DnexusIndexDirectory=../nbrepoidx -DforcedVersion=RELEASE90
> -DnetbeansInstallDirectory=nbbuild/netbeans
> -DnetbeansNbmDirectory=nbbuild/nbms
> -DnetbeansSourcesDirectory=nbbuild/build/source-zips -Ddetails=true
> -DgeneratePom=true -DdeployUrl=http://
>
> Hope it helps,
>
> JMB
>
> On Wed, Nov 21, 2018 at 8:38 PM Christian Bourque <
> christian.bour...@gmail.com> wrote:
>
> > Thanks a lot Neil!
> >
> > On Wed, Nov 21, 2018 at 1:45 PM Neil C Smith 
> > wrote:
> >
> > > On Wed, 21 Nov 2018 at 18:39, Christian Bourque
> > >  wrote:
> > > > I'm looking for the Maven repository that contains the binary
> > artefacts!
> > >
> > > There isn't one currently.  Look through the archive here for a few
> > > threads on this, or this issue which has some info on building sources
> > > for use with Maven -
> > > https://issues.apache.org/jira/browse/NETBEANS-467
> > >
> > > Best wishes,
> > >
> > > Neil
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> dev-h...@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
>

Re: Surefire plugin issue

[Jean-Marc Borer]

If you can't get the zip from the list, you can grab it from
https://issues.apache.org/jira/browse/NETBEANS-635

On Mon, Nov 26, 2018 at 4:50 PM Jean-Marc Borer  wrote:

> Ok I could reproduce it with very small sample project. Just clean and
> build and you will see that there will be no stacktrace parsing...
>
> On Mon, Nov 26, 2018 at 4:43 PM Jean-Marc Borer  wrote:
>
>> Can you see the screenshot I attached my last message (the one with the
>> XML)?
>>
>> On Mon, Nov 26, 2018 at 4:30 PM Enrico Olivelli 
>> wrote:
>>
>>> Jan-Marc,
>>> I am sorry, I can't reproduce your problem. Maybe it is something
>>> releated
>>> to the stacktrace.
>>> I am not aware of how NetBeans deals with surefire. I hope others on this
>>> list will provide help.
>>> Maybe adding a sample stacktrace may help
>>>
>>> Enrico
>>> --
>>>
>>>
>>> -- Enrico Olivelli
>>>
>>

Re: Surefire plugin issue

[Jean-Marc Borer]

Ok I could reproduce it with very small sample project. Just clean and
build and you will see that there will be no stacktrace parsing...

On Mon, Nov 26, 2018 at 4:43 PM Jean-Marc Borer  wrote:

> Can you see the screenshot I attached my last message (the one with the
> XML)?
>
> On Mon, Nov 26, 2018 at 4:30 PM Enrico Olivelli 
> wrote:
>
>> Jan-Marc,
>> I am sorry, I can't reproduce your problem. Maybe it is something releated
>> to the stacktrace.
>> I am not aware of how NetBeans deals with surefire. I hope others on this
>> list will provide help.
>> Maybe adding a sample stacktrace may help
>>
>> Enrico
>> --
>>
>>
>> -- Enrico Olivelli
>>
>
<>

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

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

Re: Surefire plugin issue

[Jean-Marc Borer]

Can you see the screenshot I attached my last message (the one with the
XML)?

On Mon, Nov 26, 2018 at 4:30 PM Enrico Olivelli  wrote:

> Jan-Marc,
> I am sorry, I can't reproduce your problem. Maybe it is something releated
> to the stacktrace.
> I am not aware of how NetBeans deals with surefire. I hope others on this
> list will provide help.
> Maybe adding a sample stacktrace may help
>
> Enrico
> --
>
>
> -- Enrico Olivelli
>

netbeans warning..

[Brad Walker]

I'm using Apache Netbeans 9.0 to do a bunch of C/C++ development. I see
this warning when starting up and thought I might bring it to your
attention.

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.netbeans.core.windows.view.ui.MainWindow
(jar:file:/home/bwalker/netbeans-9.0/platform/modules/org-netbeans-core-windows.jar!/)
to field sun.awt.X11.XToolkit.awtAppClassName
WARNING: Please consider reporting this to the maintainers of
org.netbeans.core.windows.view.ui.MainWindow
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
INFO [org.netbeans.modules.cnd.utils.cache.CndFileUtils]: C/C++ File Utils:
using case-sensitive file system
WARNING [org.netbeans.TopSecurityManager]: use of system property
netbeans.home has been obsoleted in favor of InstalledFileLocator/Places at
org.netbeans.modules.java.j2seplatform.platformdefinition.Util.removeNBArtifacts(Util.java:337)
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Resolving dependencies took: 5 ms
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Complete indexing of 0 binary roots took: 0 ms
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]:
Complete indexing of 0 source roots took: 0 ms (New or modified files: 0,
Deleted files: 0) [Adding listeners took: 0 ms]
WARNING [org.netbeans.TopSecurityManager]: use of system property
netbeans.user has been obsoleted in favor of InstalledFileLocator/Places at
org.netbeans.modules.nativeexecution.support.hostinfo.impl.HostInfoFactory.getNBKey(HostInfoFactory.java:394)
WARNING [nativeexecution.support.logger]: [931 ms.] UnixHostInfoProvider:
sed: -e expression #1, char 6: unterminated `s' command

I would assume this is something that I can ignore. But, did think you
should know about it.

-brad w.

Re: Surefire plugin issue

[Enrico Olivelli]

Jan-Marc,
I am sorry, I can't reproduce your problem. Maybe it is something releated
to the stacktrace.
I am not aware of how NetBeans deals with surefire. I hope others on this
list will provide help.
Maybe adding a sample stacktrace may help

Enrico
-- 


-- Enrico Olivelli

Re: Profiler crash for NB10

[Peter Hull]

Thanks everyone for taking the time to look into this. Answers below
but there is a big caveat.
On Mon, Nov 26, 2018 at 3:54 PM Emilian Bold  wrote:
> Peter, is it OK to consider your binaries under the Apache license for
> redistribution?
On the github repo where the binaries are, I also checked in the
source for the changes plus the updated build script. So anyone with
the source and the Microsoft C compiler (v19) should be able to
reproduce the build. In terms of using the actual binaries, that's
fine by me.
> So, just to confirm, does profiling still work with Java 8?
Yes, I checked it was still working with openjdk 1.8.

The problem with this 'quick fix' is that it relies on an assumption
about the JVM which is not guaranteed to be correct, specifically the
values that jmethodid, a JNI type, can take. I have asked for some
guidance on this from the JDK mailing list, see:
http://mail.openjdk.java.net/pipermail/discuss/2018-November/004916.html
(sorry about all these multiple sources of information!)

In short - what we have now seems to work but I'd like to request more
time to fix this properly. Once I've done this I would appreciate a
bit of help from Windows and non-Windows users to check it's working
correctly.
Thanks,
Peter

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

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

RE: Profiler crash for NB10

[Eirik Bakke]

I tested again with some more JDK versions. The new DLL works for me without 
crashing on all of the following:
* Java 8.0.181
* Java 9.0.7.1
* Java 10.0.2
* Java 11.0.1
* Java 12ea

(I'm on Windows 10.)

Note that when testing, I used the DLL with NetBeans 9.0-vc3 (rather than the 
latest NetBeans 10 candidate, which I haven't migrated to yet).

-- Eirik

-Original Message-
From: Emilian Bold  
Sent: Monday, November 26, 2018 10:54 AM
To: NetBeans Dev@ ; peterhul...@gmail.com
Subject: Re: Profiler crash for NB10

Peter, is it OK to consider your binaries under the Apache license for 
redistribution?

I have yet to check this but I'm happy about Eirik's report.

So, just to confirm, does profiling still work with Java 8?

--emi

On Mon, Nov 26, 2018 at 5:42 PM Eirik Bakke  wrote:
>
> I tested the new DLL--it works!!
>
> Here's what I did:
> 1) Start a Java profiling session via the "-agentpath" JVM argument and 
> invoking "Attach to External Process". Shortly thereafter the JVM crashes 
> with the "SUREFIRE-859: #  EXCEPTION_ACCESS_VIOLATION (0xc005) at 
> pc=0x5f131f25, pid=10112, tid=23396" error (and a long JVM dump).
> 2) Download Peter Hull's recompiled profiler binaries from 
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha , and 
> paste the two files (profilerinterface.dll and profilerinterface.map) into 
> NetBeans\profiler\lib\deployed\jdk16\windows-amd64 (overwriting the two 
> existing files).
> 3) Repeat (1) again. No crash this time, everything works fine!
>
> This is great. Very happy that the profiler functionality will be working 
> again, for newer JDKs. Thanks, Peter!
>
> -- Eirik
>
> -Original Message-
> From: Peter Hull 
> Sent: Friday, November 16, 2018 5:58 AM
> To: dev@netbeans.incubator.apache.org
> Subject: Re: Profiler crash for NB10
>
> On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold  wrote:
> > PS: @Peter: if you could also make a recompiled .DLL available 
> > together with the branch it would be great.
> Right, I have put changes into a fork here:
> https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> and the binaries (just the native code dll) 
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
>
> I have tested it and it seems to be working on Windows 64. I've tested 
> it compiles on Windows 32. I have not tested or looked at any other 
> platform (though I don't think my changes should cause problems)
>
> I speculate the problem was some incorrect casting (can't cast a 64 bit 
> pointer to long on Windows?) which maybe didn't manifest on previous JDKs 
> because the values of jmethodid.
> I don't know enough about the internals of the JVM but I'm still not sure if 
> the method used to convert a jmethodid to a jint is robust going forward.
>
> Please let me know what you think,
> Pete
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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

Are we working from "release" branches or from master ahead of a release? I think Jenkins suggests "release*" is the case. Now wondering processes etc.

[Wade Chandler]

Hey all. I was building from master recently, and had various 
issues/exceptions, and of course know we have a vote on 10 going on. Knowing 
NetBeans past, I looked for the release branches, and saw branch release100 out 
there. I wasn’t sure the current process as I had been out of touch for a while 
(work and all).

Is the idea to create a release branch, and then work there when we get “close” 
to shooting for a release? Too, how are we keeping items synced up between 
master and release* after we we start that process if so? Maybe even a link 
will work if the process is documented. I’m assuming changes in both master and 
release for the near term, so just looking for guidance.

Jenkins suggests yes on the release branch, but not sure the rest 
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/configure
 

 

Thanks much,

Wade

===

Wade Chandler
e: cons...@wadechandler.com
t: @wadechandler
https://www.linkedin.com/in/wade-chandler

Re: Profiler crash for NB10

[Emilian Bold]

Peter, is it OK to consider your binaries under the Apache license for
redistribution?

I have yet to check this but I'm happy about Eirik's report.

So, just to confirm, does profiling still work with Java 8?

--emi

On Mon, Nov 26, 2018 at 5:42 PM Eirik Bakke  wrote:
>
> I tested the new DLL--it works!!
>
> Here's what I did:
> 1) Start a Java profiling session via the "-agentpath" JVM argument and 
> invoking "Attach to External Process". Shortly thereafter the JVM crashes 
> with the "SUREFIRE-859: #  EXCEPTION_ACCESS_VIOLATION (0xc005) at 
> pc=0x5f131f25, pid=10112, tid=23396" error (and a long JVM dump).
> 2) Download Peter Hull's recompiled profiler binaries from 
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha , and 
> paste the two files (profilerinterface.dll and profilerinterface.map) into 
> NetBeans\profiler\lib\deployed\jdk16\windows-amd64 (overwriting the two 
> existing files).
> 3) Repeat (1) again. No crash this time, everything works fine!
>
> This is great. Very happy that the profiler functionality will be working 
> again, for newer JDKs. Thanks, Peter!
>
> -- Eirik
>
> -Original Message-
> From: Peter Hull 
> Sent: Friday, November 16, 2018 5:58 AM
> To: dev@netbeans.incubator.apache.org
> Subject: Re: Profiler crash for NB10
>
> On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold  wrote:
> > PS: @Peter: if you could also make a recompiled .DLL available
> > together with the branch it would be great.
> Right, I have put changes into a fork here:
> https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> and the binaries (just the native code dll) 
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
>
> I have tested it and it seems to be working on Windows 64. I've tested it 
> compiles on Windows 32. I have not tested or looked at any other platform 
> (though I don't think my changes should cause problems)
>
> I speculate the problem was some incorrect casting (can't cast a 64 bit 
> pointer to long on Windows?) which maybe didn't manifest on previous JDKs 
> because the values of jmethodid.
> I don't know enough about the internals of the JVM but I'm still not sure if 
> the method used to convert a jmethodid to a jint is robust going forward.
>
> Please let me know what you think,
> Pete
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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

RE: Profiler crash for NB10

[Eirik Bakke]

I tested the new DLL--it works!!

Here's what I did:
1) Start a Java profiling session via the "-agentpath" JVM argument and 
invoking "Attach to External Process". Shortly thereafter the JVM crashes with 
the "SUREFIRE-859: #  EXCEPTION_ACCESS_VIOLATION (0xc005) at 
pc=0x5f131f25, pid=10112, tid=23396" error (and a long JVM dump).
2) Download Peter Hull's recompiled profiler binaries from 
https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha , and 
paste the two files (profilerinterface.dll and profilerinterface.map) into 
NetBeans\profiler\lib\deployed\jdk16\windows-amd64 (overwriting the two 
existing files).
3) Repeat (1) again. No crash this time, everything works fine!

This is great. Very happy that the profiler functionality will be working 
again, for newer JDKs. Thanks, Peter!

-- Eirik

-Original Message-
From: Peter Hull  
Sent: Friday, November 16, 2018 5:58 AM
To: dev@netbeans.incubator.apache.org
Subject: Re: Profiler crash for NB10

On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold  wrote:
> PS: @Peter: if you could also make a recompiled .DLL available 
> together with the branch it would be great.
Right, I have put changes into a fork here:
https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
and the binaries (just the native code dll) 
https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha

I have tested it and it seems to be working on Windows 64. I've tested it 
compiles on Windows 32. I have not tested or looked at any other platform 
(though I don't think my changes should cause problems)

I speculate the problem was some incorrect casting (can't cast a 64 bit pointer 
to long on Windows?) which maybe didn't manifest on previous JDKs because the 
values of jmethodid.
I don't know enough about the internals of the JVM but I'm still not sure if 
the method used to convert a jmethodid to a jint is robust going forward.

Please let me know what you think,
Pete

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

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

AW: NetBeans - the UI for Maven

[Anton Epple]

OK, will do, but let's move discussion about the current PR to the PR. It's 
easier to keep track (

Am 26.11.18, 14:56 schrieb "Christian Lenz" :

This is what I meant, I would prefer also to have Java Maven or smth with 
Maven and Java Ant otherwise than only haven Java and Java Ant.


Cheers

Chris



Von: Neil C Smith
Gesendet: Montag, 26. November 2018 14:52
An: dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven

On Sun, 25 Nov 2018 at 20:53, Tim Boudreau  wrote:
> There's a UI principle Joel Spolsky expounded years ago:  Never force the
> user into a choice they don't care about.

Not sure if that was meant as a direct reply to me or not, but I
completely agree with that ...

> A lot of users of NetBeans are new to Java or new to programming
> altogether. They don't know what Ant, Maven or Gradle are, and won't
> understand what they are for a long time.

... however, from a couple of conversations I've had recently with
new-ish programmers, I'm not sure I agree with hiding the fact that
there *is* a build system when not forcing a decision.

I'm mostly +1 to Toni's PR as a good first step, but personally I
think it would be better to be more explicit in the name and
description that the project uses Maven -

eg. Java Application with Maven - A Java application using the default
Maven build system.

Is there also an issue if we just move the Maven template with the
same name in place of the Ant one that a load of old tutorials, etc.
will be confusingly wrong?

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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

Re: bits.netbeans.org / javadocs / mavenutils

[Emilian Bold]

netbeans-vm is just a hostname. Nothing to do with a software project
like visualvm or jvm.

--emi

On Mon, Nov 26, 2018 at 2:56 PM Jean-Marc Borer  wrote:
>
> Got it. Anyway my first thought was: netbeans-vm like visualvm or jvm? VM
> becomes confusing nowadays.
>
> On Mon, Nov 26, 2018 at 12:53 PM Geertjan Wielenga
>  wrote:
>
> > netbeans-vm is our virtual machine at Apache.
> >
> > Gj
> >
> > On Mon, Nov 26, 2018 at 1:42 PM Eric Barboni  wrote:
> >
> > > Hi
> > >  It will be to host apidoc for Apache Netbeans  and also the website for
> > > Apache NetBeans Maven Utilities.
> > >
> > >  Maven Artifacts for Apache NetBeans 9 and will I hope be on central.
> > >
> > >  I try to have it asap but, without website for utilities the migration
> > > after code donation is stuck.
> > >
> > > Best Regards
> > > Eric
> > > -Message d'origine-
> > > De : Jean-Marc Borer 
> > > Envoyé : lundi 26 novembre 2018 12:48
> > > À : dev@netbeans.incubator.apache.org
> > > Objet : Re: bits.netbeans.org / javadocs / mavenutils
> > >
> > > May I ask why "netbeans-vm"? This name makes no sense to me.
> > >
> > > On Mon, Nov 12, 2018 at 1:12 PM Antonio  wrote:
> > >
> > > > Hi,
> > > >
> > > > So infra suggested using ci.apache.org.
> > > >
> > > > Do we want to use that or not? Maybe we would build the artifacts
> > > > using our current jenkins setup and them transfer those to
> > > > netbeans-vm.apache.org?
> > > >
> > > > Now that the domains are operated within the ASF we could redirect
> > > > bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
> > > >
> > > > Thoughts?
> > > >
> > > > Cheers,
> > > > Antonio
> > > >
> > > > El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > > > > Thanks for the work Antonio
> > > > >
> > > > >   Where should we help and what we can do now?
> > > > >
> > > > > Regards
> > > > > Eric
> > > > > -Message d'origine-
> > > > > De : Antonio 
> > > > > Envoyé : mercredi 7 novembre 2018 14:13 À :
> > > > > dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > > > > javadocs / mavenutils
> > > > >
> > > > > Hi Eric,
> > > > >
> > > > > I think the point is that javadoc is published automatically. For
> > > > instance, for the apex-core project, see
> > > > >
> > > > >
> > > > https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4
> > > > /index.html
> > > > >
> > > > > Anyway feel free to ask whatever questions you consider to the JIRA
> > > > ticket with Infra. They know more than I do :-)
> > > > >
> > > > > Cheers,
> > > > > Antonio
> > > > >
> > > > >
> > > > > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> > > > >> Hi Antonio
> > > > >>I did not get the point here. What is the difference using
> > > > >> between
> > > > build.apache.org vs buildbot.apache ? Why do we need another type of
> > ci
> > > ?
> > > > >>
> > > > >> Regards
> > > > >> Eric
> > > > >>
> > > > >> -Message d'origine-
> > > > >> De : Antonio 
> > > > >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> > > > >> dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > > > >> javadocs / mavenutils
> > > > >>
> > > > >> Hi all,
> > > > >>
> > > > >> Gavin from infra is suggesting [1] that we use the Apache buildbot
> > > > >> [2]
> > > > to generate javadocs and other stuff (JNLP/Maven).
> > > > >>
> > > > >> I think it's a great idea, is it ok if I request one of these for
> > > > >> us
> > > > and we give it a go?
> > > > >>
> > > > >> Cheers,
> > > > >> Antonio
> > > > >>
> > > > >> [1]
> > > > >> https://issues.apache.org/jira/browse/INFRA-17202
> > > > >>
> > > > >> [2]
> > > > >> https://ci.apache.org/projects/
> > > > >>
> > > > >> El 2/11/18 a las 18:48, Antonio escribió:
> > > > >>> Hi,
> > > > >>>
> > > > >>> javadoc.tgz is just an example binary, probably not very
> > > > representative.
> > > > >>>
> > > > >>> The real problem arises when we want to host _development_ maven
> > > > >>> artifacts or JNLP binaries. That is big, and we just can't do that
> > > > >>> each eight hours using a git branch, I think.
> > > > >>>
> > > > >>> For releases I'd suggest:
> > > > >>>
> > > > >>> - Creating javadoc.tgz and distributing it along the rest of
> > > > >>> release binaries through the mirror system, as sources are. This
> > > > >>> may require chaning the release process.
> > > > >>> - Publishing the javadoc at netbeans.apache.org under an
> > > > >>> appropriate
> > > > >>> 9.0/10.0 subdirectory.
> > > > >>> - Linking from bits.netbeans.org back to netbeans.apache.org for
> > > > >>> these javadoc.
> > > > >>>
> > > > >>> Thoughts?
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Antonio
> > > > >>>
> > > > >>>
> > > > >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
> > > >  On Fri, 2 Nov 2018 at 16:52, Antonio  wrote:
> > > > > Generating a 51Mb. binary file and hosting it in a git branch
> > > > > each eight hours simply won't scale.
> > > > 
> > > >  No kidding! :-)
> > > > 
> > > >  This is mea

Re: [PPMC] We need volunteers for NetBeans lists moderation (+ [MENTORS] , want to step down?)

[Geertjan Wielenga]

There is really no need to nudge. Everyone here wants NetBeans to be a top
level Apache project. :-)

Gj

On Monday, November 26, 2018, Bertrand Delacretaz 
wrote:

> On Mon, Nov 26, 2018 at 2:09 PM Geertjan Wielenga
>  wrote:
> > > In view of the project's graduation
> >
> > Just note that we haven't started that discussion yet, though will do so
> > ASAP, the Apache NetBeans 10 release is taking all our time at the
> moment...
>
> No problem, that was just a friendly subconscious nudge ;-)
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Profiler crash for NB10

[Geertjan Wielenga]

Can you try Peter’s solution, if you’re on Windows and using the Profiler?

Gj

On Monday, November 26, 2018, Jean-Marc Borer  wrote:

> Yes, your are right. It concerned the profiler (was my "typo"). I actually
> meant the profiler. OK. If I run into this issue, I'll report it.
>
> On Mon, Nov 26, 2018 at 1:25 PM Geertjan Wielenga
>  wrote:
>
> > AFAIK this has nothing to do with debugging, but with profiling, and not
> > all profiling but a specific subset of profiling.
> >
> > Gj
> >
> > On Mon, Nov 26, 2018 at 2:24 PM Jean-Marc Borer 
> wrote:
> >
> > > So does it mean that without Peter's fix, no chance to debug Java code
> on
> > > Windows or does it just occur sometimes?
> > >
> > > JMB
> > >
> > > On Mon, Nov 26, 2018 at 1:07 PM Geertjan Wielenga
> > >  wrote:
> > >
> > > > So far Peter has had no responses from anyone, no indication that
> > anyone
> > > > has tried his solution.
> > > >
> > > > Can you try it and give feedback? Too late now for inclusion in
> Apache
> > > > NetBeans 10, but the feedback would be useful.
> > > >
> > > > Gj
> > > >
> > > >
> > > > On Mon, Nov 26, 2018 at 2:00 PM Jean-Marc Borer 
> > > wrote:
> > > >
> > > > > Peter,
> > > > >
> > > > > Will your fix be included in the release of NB 10?
> > > > >
> > > > > Cheers
> > > > >
> > > > > JM
> > > > >
> > > > > On Fri, Nov 16, 2018 at 11:08 AM Peter Hull  >
> > > > wrote:
> > > > >
> > > > > > On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold <
> > emilian.b...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > PS: @Peter: if you could also make a recompiled .DLL available
> > > > > > > together with the branch it would be great.
> > > > > > Right, I have put changes into a fork here:
> > > > > > https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> > > > > > and the binaries (just the native code dll)
> > > > > >
> > > https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
> > > > > >
> > > > > > I have tested it and it seems to be working on Windows 64. I've
> > > tested
> > > > > > it compiles on Windows 32. I have not tested or looked at any
> other
> > > > > > platform (though I don't think my changes should cause problems)
> > > > > >
> > > > > > I speculate the problem was some incorrect casting (can't cast a
> 64
> > > > > > bit pointer to long on Windows?) which maybe didn't manifest on
> > > > > > previous JDKs because the values of jmethodid.
> > > > > > I don't know enough about the internals of the JVM but I'm still
> > not
> > > > > > sure if the method used to convert a jmethodid to a jint is
> robust
> > > > > > going forward.
> > > > > >
> > > > > > Please let me know what you think,
> > > > > > Pete
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail:
> > > dev-unsubscr...@netbeans.incubator.apache.org
> > > > > > For additional commands, e-mail:
> > > > dev-h...@netbeans.incubator.apache.org
> > > > > >
> > > > > > For further information about the NetBeans mailing lists, visit:
> > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/
> Mailing+lists
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

AW: NetBeans - the UI for Maven

[Christian Lenz]

This is what I meant, I would prefer also to have Java Maven or smth with Maven 
and Java Ant otherwise than only haven Java and Java Ant.


Cheers

Chris



Von: Neil C Smith
Gesendet: Montag, 26. November 2018 14:52
An: dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven

On Sun, 25 Nov 2018 at 20:53, Tim Boudreau  wrote:
> There's a UI principle Joel Spolsky expounded years ago:  Never force the
> user into a choice they don't care about.

Not sure if that was meant as a direct reply to me or not, but I
completely agree with that ...

> A lot of users of NetBeans are new to Java or new to programming
> altogether. They don't know what Ant, Maven or Gradle are, and won't
> understand what they are for a long time.

... however, from a couple of conversations I've had recently with
new-ish programmers, I'm not sure I agree with hiding the fact that
there *is* a build system when not forcing a decision.

I'm mostly +1 to Toni's PR as a good first step, but personally I
think it would be better to be more explicit in the name and
description that the project uses Maven -

eg. Java Application with Maven - A Java application using the default
Maven build system.

Is there also an issue if we just move the Maven template with the
same name in place of the Ant one that a load of old tutorials, etc.
will be confusingly wrong?

Best wishes,

Neil

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

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

Re: NetBeans - the UI for Maven

[Neil C Smith]

On Sun, 25 Nov 2018 at 20:53, Tim Boudreau  wrote:
> There's a UI principle Joel Spolsky expounded years ago:  Never force the
> user into a choice they don't care about.

Not sure if that was meant as a direct reply to me or not, but I
completely agree with that ...

> A lot of users of NetBeans are new to Java or new to programming
> altogether. They don't know what Ant, Maven or Gradle are, and won't
> understand what they are for a long time.

... however, from a couple of conversations I've had recently with
new-ish programmers, I'm not sure I agree with hiding the fact that
there *is* a build system when not forcing a decision.

I'm mostly +1 to Toni's PR as a good first step, but personally I
think it would be better to be more explicit in the name and
description that the project uses Maven -

eg. Java Application with Maven - A Java application using the default
Maven build system.

Is there also an issue if we just move the Maven template with the
same name in place of the Ant one that a load of old tutorials, etc.
will be confusingly wrong?

Best wishes,

Neil

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

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

Re: [PPMC] We need volunteers for NetBeans lists moderation (+ [MENTORS] , want to step down?)

[Bertrand Delacretaz]

On Mon, Nov 26, 2018 at 2:09 PM Geertjan Wielenga
 wrote:
> > In view of the project's graduation
>
> Just note that we haven't started that discussion yet, though will do so
> ASAP, the Apache NetBeans 10 release is taking all our time at the moment...

No problem, that was just a friendly subconscious nudge ;-)

-Bertrand

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

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

Re: Windows security warning constantly popping when startingNetbeans 9.0

[Jean-Marc Borer]

I'll do it this evening. I cannot access those "free" image repos from my
company: they are blacklisted :(

On Mon, Nov 26, 2018 at 1:40 PM Christian Lenz 
wrote:

> I don’t think that the mailinglist will work with attachments, only
> guessing. Can you please upload the Image to Maybe imgur or smth similar
> please?
>
>
> Cheers
>
> Chris
>
>
>
> Von: Jean-Marc Borer
> Gesendet: Montag, 26. November 2018 14:29
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Windows security warning constantly popping when
> startingNetbeans 9.0
>
> Sorry, it was an embbed image in "rich" email. I attached it.
>
> On Mon, Nov 26, 2018 at 1:26 PM Christian Lenz 
> wrote:
> Unfortunately I can’t see the Image.
>
>
>
> Von: Jean-Marc Borer
> Gesendet: Montag, 26. November 2018 13:37
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Windows security warning constantly popping when
> startingNetbeans 9.0
>
> I'll answer to myself: I can uncheck the "Always ask before opening this
> file". So isn't it possible anyway to have a proper publisher set
> eventually?
>
> Cheers
>
> On Mon, Nov 26, 2018 at 12:30 PM Jean-Marc Borer 
> wrote:
>
> Hi all,
>
> I am wondering if I am the only one experiencing this Windows security
> alert with Netbeans 9.0 every time I launch the IDE?
>
>
>
> Product Version: Apache NetBeans IDE 9.0 (Build
> incubator-netbeans-release-334-on-20180708)
> Java: 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12
> Runtime: Java(TM) SE Runtime Environment 1.8.0_191-b12
> System: Windows 7 version 6.1 running on amd64; Cp1252; en (nb)
> User directory: C:\projects\.netbeans\9.0
> Cache directory: C:\projects\.netbeans\cache\9.0
>
> Best regards
>
> JMB
>
>

AW: Windows security warning constantly popping when startingNetbeans 9.0

[Christian Lenz]

I don’t think that the mailinglist will work with attachments, only guessing. 
Can you please upload the Image to Maybe imgur or smth similar please?


Cheers

Chris



Von: Jean-Marc Borer
Gesendet: Montag, 26. November 2018 14:29
An: dev@netbeans.incubator.apache.org
Betreff: Re: Windows security warning constantly popping when startingNetbeans 
9.0

Sorry, it was an embbed image in "rich" email. I attached it.

On Mon, Nov 26, 2018 at 1:26 PM Christian Lenz  wrote:
Unfortunately I can’t see the Image.



Von: Jean-Marc Borer
Gesendet: Montag, 26. November 2018 13:37
An: dev@netbeans.incubator.apache.org
Betreff: Re: Windows security warning constantly popping when startingNetbeans 
9.0

I'll answer to myself: I can uncheck the "Always ask before opening this file". 
So isn't it possible anyway to have a proper publisher set eventually?

Cheers

On Mon, Nov 26, 2018 at 12:30 PM Jean-Marc Borer  wrote:

Hi all,

I am wondering if I am the only one experiencing this Windows security alert 
with Netbeans 9.0 every time I launch the IDE?



Product Version: Apache NetBeans IDE 9.0 (Build 
incubator-netbeans-release-334-on-20180708) 
Java: 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12 
Runtime: Java(TM) SE Runtime Environment 1.8.0_191-b12 
System: Windows 7 version 6.1 running on amd64; Cp1252; en (nb) 
User directory: C:\projects\.netbeans\9.0 
Cache directory: C:\projects\.netbeans\cache\9.0

Best regards

JMB       

Re: Profiler crash for NB10

[Jean-Marc Borer]

Yes, your are right. It concerned the profiler (was my "typo"). I actually
meant the profiler. OK. If I run into this issue, I'll report it.

On Mon, Nov 26, 2018 at 1:25 PM Geertjan Wielenga
 wrote:

> AFAIK this has nothing to do with debugging, but with profiling, and not
> all profiling but a specific subset of profiling.
>
> Gj
>
> On Mon, Nov 26, 2018 at 2:24 PM Jean-Marc Borer  wrote:
>
> > So does it mean that without Peter's fix, no chance to debug Java code on
> > Windows or does it just occur sometimes?
> >
> > JMB
> >
> > On Mon, Nov 26, 2018 at 1:07 PM Geertjan Wielenga
> >  wrote:
> >
> > > So far Peter has had no responses from anyone, no indication that
> anyone
> > > has tried his solution.
> > >
> > > Can you try it and give feedback? Too late now for inclusion in Apache
> > > NetBeans 10, but the feedback would be useful.
> > >
> > > Gj
> > >
> > >
> > > On Mon, Nov 26, 2018 at 2:00 PM Jean-Marc Borer 
> > wrote:
> > >
> > > > Peter,
> > > >
> > > > Will your fix be included in the release of NB 10?
> > > >
> > > > Cheers
> > > >
> > > > JM
> > > >
> > > > On Fri, Nov 16, 2018 at 11:08 AM Peter Hull 
> > > wrote:
> > > >
> > > > > On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold <
> emilian.b...@gmail.com
> > >
> > > > > wrote:
> > > > > > PS: @Peter: if you could also make a recompiled .DLL available
> > > > > > together with the branch it would be great.
> > > > > Right, I have put changes into a fork here:
> > > > > https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> > > > > and the binaries (just the native code dll)
> > > > >
> > https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
> > > > >
> > > > > I have tested it and it seems to be working on Windows 64. I've
> > tested
> > > > > it compiles on Windows 32. I have not tested or looked at any other
> > > > > platform (though I don't think my changes should cause problems)
> > > > >
> > > > > I speculate the problem was some incorrect casting (can't cast a 64
> > > > > bit pointer to long on Windows?) which maybe didn't manifest on
> > > > > previous JDKs because the values of jmethodid.
> > > > > I don't know enough about the internals of the JVM but I'm still
> not
> > > > > sure if the method used to convert a jmethodid to a jint is robust
> > > > > going forward.
> > > > >
> > > > > Please let me know what you think,
> > > > > Pete
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail:
> > dev-unsubscr...@netbeans.incubator.apache.org
> > > > > For additional commands, e-mail:
> > > dev-h...@netbeans.incubator.apache.org
> > > > >
> > > > > For further information about the NetBeans mailing lists, visit:
> > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Windows security warning constantly popping when startingNetbeans 9.0

[Jean-Marc Borer]

Sorry, it was an embbed image in "rich" email. I attached it.

On Mon, Nov 26, 2018 at 1:26 PM Christian Lenz 
wrote:

> Unfortunately I can’t see the Image.
>
>
>
> Von: Jean-Marc Borer
> Gesendet: Montag, 26. November 2018 13:37
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Windows security warning constantly popping when
> startingNetbeans 9.0
>
> I'll answer to myself: I can uncheck the "Always ask before opening this
> file". So isn't it possible anyway to have a proper publisher set
> eventually?
>
> Cheers
>
> On Mon, Nov 26, 2018 at 12:30 PM Jean-Marc Borer 
> wrote:
>
> Hi all,
>
> I am wondering if I am the only one experiencing this Windows security
> alert with Netbeans 9.0 every time I launch the IDE?
>
>
>
> Product Version: Apache NetBeans IDE 9.0 (Build
> incubator-netbeans-release-334-on-20180708)
> Java: 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12
> Runtime: Java(TM) SE Runtime Environment 1.8.0_191-b12
> System: Windows 7 version 6.1 running on amd64; Cp1252; en (nb)
> User directory: C:\projects\.netbeans\9.0
> Cache directory: C:\projects\.netbeans\cache\9.0
>
> Best regards
>
> JMB
>
>

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

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

Re: Surefire plugin issue

[Jean-Marc Borer]

I just tried with 2.22.1. It is not working for me

[image: image.png]

org.apache.maven.plugins
maven-surefire-plugin
2.22.1

1
false

-Dfile.encoding=${project.build.sourceEncoding}
-Duser.timezone=UTC

true

false



Any idea why it doesn't work for me?

*Product Version:* Apache NetBeans IDE 9.0 (Build
incubator-netbeans-release-334-on-20180708)

*Java:* 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12

*Runtime:* Java(TM) SE Runtime Environment 1.8.0_191-b12

*System:* Windows 7 version 6.1 running on amd64; Cp1252; en (nb)

*User directory:* C:\projects\.netbeans\9.0

*Cache directory:* C:\projects\.netbeans\cache\9.0



On Mon, Nov 26, 2018 at 1:12 PM Enrico Olivelli  wrote:

> Jean-Marc
> Did you try latest surefire ?
>
> I have no problem with NB 9 + surefire
>
> Enrico
>
> Il lun 26 nov 2018, 13:42 Jean-Marc Borer  ha scritto:
>
> > Hi all,
> >
> > Guys, we are planning to move away from Ant in favor of Maven. This will
> > only be possible if the Maven echosystem is properly supported.
> Currently,
> > surefire error logs are still broken since 2.19 as I described in
> > https://issues.apache.org/jira/browse/NETBEANS-635
> >
> > For example with surefire 2.19.1:
> >
> > [image: image.png]
> > You can see that when I click on the link, an error message is displayed
> > in the status bar in the lower left corner.
> >
> > This was broken in NB 8.2 and still is in NB 9.0
> >
> > Am I missing something here?
> >
> > Cheers,
> >
> > JMB
> >
> > --
>
>
> -- Enrico Olivelli
>

AW: Windows security warning constantly popping when startingNetbeans 9.0

[Christian Lenz]

Unfortunately I can’t see the Image.



Von: Jean-Marc Borer
Gesendet: Montag, 26. November 2018 13:37
An: dev@netbeans.incubator.apache.org
Betreff: Re: Windows security warning constantly popping when startingNetbeans 
9.0

I'll answer to myself: I can uncheck the "Always ask before opening this file". 
So isn't it possible anyway to have a proper publisher set eventually?

Cheers

On Mon, Nov 26, 2018 at 12:30 PM Jean-Marc Borer  wrote:

Hi all,

I am wondering if I am the only one experiencing this Windows security alert 
with Netbeans 9.0 every time I launch the IDE?



Product Version: Apache NetBeans IDE 9.0 (Build 
incubator-netbeans-release-334-on-20180708) 
Java: 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12 
Runtime: Java(TM) SE Runtime Environment 1.8.0_191-b12 
System: Windows 7 version 6.1 running on amd64; Cp1252; en (nb) 
User directory: C:\projects\.netbeans\9.0 
Cache directory: C:\projects\.netbeans\cache\9.0

Best regards

JMB       

Re: Profiler crash for NB10

[Geertjan Wielenga]

AFAIK this has nothing to do with debugging, but with profiling, and not
all profiling but a specific subset of profiling.

Gj

On Mon, Nov 26, 2018 at 2:24 PM Jean-Marc Borer  wrote:

> So does it mean that without Peter's fix, no chance to debug Java code on
> Windows or does it just occur sometimes?
>
> JMB
>
> On Mon, Nov 26, 2018 at 1:07 PM Geertjan Wielenga
>  wrote:
>
> > So far Peter has had no responses from anyone, no indication that anyone
> > has tried his solution.
> >
> > Can you try it and give feedback? Too late now for inclusion in Apache
> > NetBeans 10, but the feedback would be useful.
> >
> > Gj
> >
> >
> > On Mon, Nov 26, 2018 at 2:00 PM Jean-Marc Borer 
> wrote:
> >
> > > Peter,
> > >
> > > Will your fix be included in the release of NB 10?
> > >
> > > Cheers
> > >
> > > JM
> > >
> > > On Fri, Nov 16, 2018 at 11:08 AM Peter Hull 
> > wrote:
> > >
> > > > On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold  >
> > > > wrote:
> > > > > PS: @Peter: if you could also make a recompiled .DLL available
> > > > > together with the branch it would be great.
> > > > Right, I have put changes into a fork here:
> > > > https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> > > > and the binaries (just the native code dll)
> > > >
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
> > > >
> > > > I have tested it and it seems to be working on Windows 64. I've
> tested
> > > > it compiles on Windows 32. I have not tested or looked at any other
> > > > platform (though I don't think my changes should cause problems)
> > > >
> > > > I speculate the problem was some incorrect casting (can't cast a 64
> > > > bit pointer to long on Windows?) which maybe didn't manifest on
> > > > previous JDKs because the values of jmethodid.
> > > > I don't know enough about the internals of the JVM but I'm still not
> > > > sure if the method used to convert a jmethodid to a jint is robust
> > > > going forward.
> > > >
> > > > Please let me know what you think,
> > > > Pete
> > > >
> > > > -
> > > > To unsubscribe, e-mail:
> dev-unsubscr...@netbeans.incubator.apache.org
> > > > For additional commands, e-mail:
> > dev-h...@netbeans.incubator.apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Re: Profiler crash for NB10

[Jean-Marc Borer]

So does it mean that without Peter's fix, no chance to debug Java code on
Windows or does it just occur sometimes?

JMB

On Mon, Nov 26, 2018 at 1:07 PM Geertjan Wielenga
 wrote:

> So far Peter has had no responses from anyone, no indication that anyone
> has tried his solution.
>
> Can you try it and give feedback? Too late now for inclusion in Apache
> NetBeans 10, but the feedback would be useful.
>
> Gj
>
>
> On Mon, Nov 26, 2018 at 2:00 PM Jean-Marc Borer  wrote:
>
> > Peter,
> >
> > Will your fix be included in the release of NB 10?
> >
> > Cheers
> >
> > JM
> >
> > On Fri, Nov 16, 2018 at 11:08 AM Peter Hull 
> wrote:
> >
> > > On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold 
> > > wrote:
> > > > PS: @Peter: if you could also make a recompiled .DLL available
> > > > together with the branch it would be great.
> > > Right, I have put changes into a fork here:
> > > https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> > > and the binaries (just the native code dll)
> > > https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
> > >
> > > I have tested it and it seems to be working on Windows 64. I've tested
> > > it compiles on Windows 32. I have not tested or looked at any other
> > > platform (though I don't think my changes should cause problems)
> > >
> > > I speculate the problem was some incorrect casting (can't cast a 64
> > > bit pointer to long on Windows?) which maybe didn't manifest on
> > > previous JDKs because the values of jmethodid.
> > > I don't know enough about the internals of the JVM but I'm still not
> > > sure if the method used to convert a jmethodid to a jint is robust
> > > going forward.
> > >
> > > Please let me know what you think,
> > > Pete
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> dev-h...@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
>

Re: recommendation for language support

[Jean-Marc Borer]

Very interesting topic.

As it seems there are people around with knowledge of AST and source
parsing, I would like to ask if someone knows how I can get the java source
AST (property in a Document?) and how I can listen when it is updated? I am
currently working on a plugin that will handle color preview in the Java
source code.

Cheers.

JMB


On Wed, Nov 7, 2018 at 4:32 PM Mario Schroeder 
wrote:

> Hello NetBeaners,
>
> I finished my grammar based on ANTLR. The current version satisfies me.
> However since it is my first attempt I would highly appreciate if someone
> from this thread could have a look and comment if something could be
> improved. I know that you guys might be busy with the new release, so I
> will be very thankful for a little bit of your time.
>
> The the grammar can be found here:
> https://github.com/mario-s/grammars-v4/tree/cto/cto
>
> Thanks in advance!
> -Mario
>
> Am So., 4. Nov. 2018 um 05:13 Uhr schrieb Tim Boudreau <
> niftin...@gmail.com
> >:
>
> > I'd strongly recommend going with Antlr-4 - it is very nice.
> >
> > There is one impedance mismatch to be aware of, to save a few hours of
> > cursing both Antlr and NetBeans' lexer infrastructure: Antlr may give you
> > an EOF token that is non-empty - check it, or you won't consume all the
> > characters from the input, and if you don't, an exception will be thrown
> > saying you didn't consume all the characters. The LexerInput you get
> passed
> > has to get entirely consumed before you return a null to indicate you've
> > lexed the entire input. If it wasn't, the infrastructure assumes that's a
> > bug.
> >
> > One other non-obvious thing: If your grammar users channels to ignore
> > whitespace or comments when parsing, make sure:
> >  - that when you're lexing you use a stream that returns ALL the tokens
> on
> > ALL channels (if using CommonTokenStream pass -1 for the channel, if
> you're
> > wrappering LexerInput, you're all set)
> >  - conversely, when parsing, make sure you use a stream that only returns
> > channel 0 tokens, or you will think your parser is broken when it isn't)
> >
> > Having written several modules that add language support using Antlr,
> I've
> > considered factoring some of the always the same stuff (generating token
> > id's from a vocabulary, stuff like that) into a support module.
> >
> > Over the past few weeks I've been doing some heavy duty work on the
> > NetBeans Antlr plugin in github, which appears to be abandoned and was in
> > need of a few features - like being able to syntax highlight files in a
> > language under development and do error highlighting of them, and refresh
> > that when the grammar is edited (which involves a level of hackery
> > bordering in evil, since it means working around all of the declarative
> > mechanisms for languages, data loaders, mime resolvers and everything
> else
> > to be installed, to allow something to imperatively make languages appear
> > out of the ether with all their editor plumbing, then change, then
> vanish).
> > When there's something reasonably non fragile to test, I'll post here.
> >
> > I'd suggest using Maven for your plugin, as the Maven Antlr plugin is
> > pretty easy to set up, and results in a pretty easy to understand
> structure
> > for things.
> >
> > -Tim
> >
> > On Tue, Oct 30, 2018 at 3:37 PM Mario Schroeder 
> > wrote:
> >
> > > Hi,
> > >
> > > I would appreciate when someone could set me on the right track. I'm
> > > wondering what is the best way to write a plugin with a support for a
> new
> > > language.
> > >
> > > I have found this old tutorial:
> > > http://wiki.netbeans.org/How_to_create_support_for_a_new_language
> > > It uses JavaCC. The tutorial is linked to another one, which makes use
> of
> > > ANTLR. When I have a look at NetBeans source code, there are some
> > templates
> > > written with JFlex. So I'm confused. Which one should I use?
> > >
> > > I would prefer ANTLR, since there seems to be more documentation for
> it.
> > > Does anyone have a recommendation?
> > >
> > > Regards,
> > > Mario
> > >
> > --
> > http://timboudreau.com
> >
>

Re: Surefire plugin issue

[Enrico Olivelli]

Jean-Marc
Did you try latest surefire ?

I have no problem with NB 9 + surefire

Enrico

Il lun 26 nov 2018, 13:42 Jean-Marc Borer  ha scritto:

> Hi all,
>
> Guys, we are planning to move away from Ant in favor of Maven. This will
> only be possible if the Maven echosystem is properly supported. Currently,
> surefire error logs are still broken since 2.19 as I described in
> https://issues.apache.org/jira/browse/NETBEANS-635
>
> For example with surefire 2.19.1:
>
> [image: image.png]
> You can see that when I click on the link, an error message is displayed
> in the status bar in the lower left corner.
>
> This was broken in NB 8.2 and still is in NB 9.0
>
> Am I missing something here?
>
> Cheers,
>
> JMB
>
> --


-- Enrico Olivelli

Re: [PPMC] We need volunteers for NetBeans lists moderation (+ [MENTORS] , want to step down?)

[Geertjan Wielenga]

>
> In view of the project's graduation
>

Just note that we haven't started that discussion yet, though will do so
ASAP, the Apache NetBeans 10 release is taking all our time at the moment.

Gj

On Mon, Nov 26, 2018 at 1:56 PM Bertrand Delacretaz 
wrote:

> Hi NetBeans PPMC members,
>
> As per https://whimsy.apache.org/roster/ppmc/netbeans it looks like
> it's only Geertjan and mentors who are moderating the NetBeans mailing
> lists for now.
>
> In view of the project's graduation I'd like to step down and maybe
> other mentors want do to that as well?
>
> To have enough moderators, could we have a 2-3 additional volunteers
> for that task? You need to be a NetBeans PPMC member and
> https://reference.apache.org/pmc/ml has the general instructions.
>
> Currently, with a good spam filter I get just a few relevant messages
> per week to moderate so it's not a lot of work.
>
> As per https://www.apache.org/dev/infra-contact we first need to
> collect the list of people stepping down or volunteering and then send
> a single email to apm...@apache.org with the changes - unless someone
> here has karma to make those changes ourselves, I don't.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Profiler crash for NB10

[Geertjan Wielenga]

So far Peter has had no responses from anyone, no indication that anyone
has tried his solution.

Can you try it and give feedback? Too late now for inclusion in Apache
NetBeans 10, but the feedback would be useful.

Gj


On Mon, Nov 26, 2018 at 2:00 PM Jean-Marc Borer  wrote:

> Peter,
>
> Will your fix be included in the release of NB 10?
>
> Cheers
>
> JM
>
> On Fri, Nov 16, 2018 at 11:08 AM Peter Hull  wrote:
>
> > On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold 
> > wrote:
> > > PS: @Peter: if you could also make a recompiled .DLL available
> > > together with the branch it would be great.
> > Right, I have put changes into a fork here:
> > https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> > and the binaries (just the native code dll)
> > https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
> >
> > I have tested it and it seems to be working on Windows 64. I've tested
> > it compiles on Windows 32. I have not tested or looked at any other
> > platform (though I don't think my changes should cause problems)
> >
> > I speculate the problem was some incorrect casting (can't cast a 64
> > bit pointer to long on Windows?) which maybe didn't manifest on
> > previous JDKs because the values of jmethodid.
> > I don't know enough about the internals of the JVM but I'm still not
> > sure if the method used to convert a jmethodid to a jint is robust
> > going forward.
> >
> > Please let me know what you think,
> > Pete
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>

Re: Profiler crash for NB10

[Jean-Marc Borer]

Peter,

Will your fix be included in the release of NB 10?

Cheers

JM

On Fri, Nov 16, 2018 at 11:08 AM Peter Hull  wrote:

> On Thu, Nov 15, 2018 at 6:02 AM Emilian Bold 
> wrote:
> > PS: @Peter: if you could also make a recompiled .DLL available
> > together with the branch it would be great.
> Right, I have put changes into a fork here:
> https://github.com/pedro-w/incubator-netbeans/tree/profiler-tmp
> and the binaries (just the native code dll)
> https://github.com/pedro-w/incubator-netbeans/releases/tag/v0.1-alpha
>
> I have tested it and it seems to be working on Windows 64. I've tested
> it compiles on Windows 32. I have not tested or looked at any other
> platform (though I don't think my changes should cause problems)
>
> I speculate the problem was some incorrect casting (can't cast a 64
> bit pointer to long on Windows?) which maybe didn't manifest on
> previous JDKs because the values of jmethodid.
> I don't know enough about the internals of the JVM but I'm still not
> sure if the method used to convert a jmethodid to a jint is robust
> going forward.
>
> Please let me know what you think,
> Pete
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: bits.netbeans.org / javadocs / mavenutils

[Jean-Marc Borer]

Got it. Anyway my first thought was: netbeans-vm like visualvm or jvm? VM
becomes confusing nowadays.

On Mon, Nov 26, 2018 at 12:53 PM Geertjan Wielenga
 wrote:

> netbeans-vm is our virtual machine at Apache.
>
> Gj
>
> On Mon, Nov 26, 2018 at 1:42 PM Eric Barboni  wrote:
>
> > Hi
> >  It will be to host apidoc for Apache Netbeans  and also the website for
> > Apache NetBeans Maven Utilities.
> >
> >  Maven Artifacts for Apache NetBeans 9 and will I hope be on central.
> >
> >  I try to have it asap but, without website for utilities the migration
> > after code donation is stuck.
> >
> > Best Regards
> > Eric
> > -Message d'origine-
> > De : Jean-Marc Borer 
> > Envoyé : lundi 26 novembre 2018 12:48
> > À : dev@netbeans.incubator.apache.org
> > Objet : Re: bits.netbeans.org / javadocs / mavenutils
> >
> > May I ask why "netbeans-vm"? This name makes no sense to me.
> >
> > On Mon, Nov 12, 2018 at 1:12 PM Antonio  wrote:
> >
> > > Hi,
> > >
> > > So infra suggested using ci.apache.org.
> > >
> > > Do we want to use that or not? Maybe we would build the artifacts
> > > using our current jenkins setup and them transfer those to
> > > netbeans-vm.apache.org?
> > >
> > > Now that the domains are operated within the ASF we could redirect
> > > bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
> > >
> > > Thoughts?
> > >
> > > Cheers,
> > > Antonio
> > >
> > > El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > > > Thanks for the work Antonio
> > > >
> > > >   Where should we help and what we can do now?
> > > >
> > > > Regards
> > > > Eric
> > > > -Message d'origine-
> > > > De : Antonio 
> > > > Envoyé : mercredi 7 novembre 2018 14:13 À :
> > > > dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > > > javadocs / mavenutils
> > > >
> > > > Hi Eric,
> > > >
> > > > I think the point is that javadoc is published automatically. For
> > > instance, for the apex-core project, see
> > > >
> > > >
> > > https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4
> > > /index.html
> > > >
> > > > Anyway feel free to ask whatever questions you consider to the JIRA
> > > ticket with Infra. They know more than I do :-)
> > > >
> > > > Cheers,
> > > > Antonio
> > > >
> > > >
> > > > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> > > >> Hi Antonio
> > > >>I did not get the point here. What is the difference using
> > > >> between
> > > build.apache.org vs buildbot.apache ? Why do we need another type of
> ci
> > ?
> > > >>
> > > >> Regards
> > > >> Eric
> > > >>
> > > >> -Message d'origine-
> > > >> De : Antonio 
> > > >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> > > >> dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > > >> javadocs / mavenutils
> > > >>
> > > >> Hi all,
> > > >>
> > > >> Gavin from infra is suggesting [1] that we use the Apache buildbot
> > > >> [2]
> > > to generate javadocs and other stuff (JNLP/Maven).
> > > >>
> > > >> I think it's a great idea, is it ok if I request one of these for
> > > >> us
> > > and we give it a go?
> > > >>
> > > >> Cheers,
> > > >> Antonio
> > > >>
> > > >> [1]
> > > >> https://issues.apache.org/jira/browse/INFRA-17202
> > > >>
> > > >> [2]
> > > >> https://ci.apache.org/projects/
> > > >>
> > > >> El 2/11/18 a las 18:48, Antonio escribió:
> > > >>> Hi,
> > > >>>
> > > >>> javadoc.tgz is just an example binary, probably not very
> > > representative.
> > > >>>
> > > >>> The real problem arises when we want to host _development_ maven
> > > >>> artifacts or JNLP binaries. That is big, and we just can't do that
> > > >>> each eight hours using a git branch, I think.
> > > >>>
> > > >>> For releases I'd suggest:
> > > >>>
> > > >>> - Creating javadoc.tgz and distributing it along the rest of
> > > >>> release binaries through the mirror system, as sources are. This
> > > >>> may require chaning the release process.
> > > >>> - Publishing the javadoc at netbeans.apache.org under an
> > > >>> appropriate
> > > >>> 9.0/10.0 subdirectory.
> > > >>> - Linking from bits.netbeans.org back to netbeans.apache.org for
> > > >>> these javadoc.
> > > >>>
> > > >>> Thoughts?
> > > >>>
> > > >>> Thanks,
> > > >>> Antonio
> > > >>>
> > > >>>
> > > >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
> > >  On Fri, 2 Nov 2018 at 16:52, Antonio  wrote:
> > > > Generating a 51Mb. binary file and hosting it in a git branch
> > > > each eight hours simply won't scale.
> > > 
> > >  No kidding! :-)
> > > 
> > >  This is meant to be a short term fix for hosting release
> > >  Javadocs, and possibly dev Javadocs with your date fix, and will
> > >  proxy back to Oracle hosting for anything not there.  Of course,
> > >  that's not necessarily useful here.
> > > 
> > >  But do we need that .tgz generated anyway?  Maybe a .tgz of the
> > >  release docs on the mirror system alongside the release, which
> > >  was discussed previously, is enough?
>

[PPMC] We need volunteers for NetBeans lists moderation (+ [MENTORS] , want to step down?)

[Bertrand Delacretaz]

Hi NetBeans PPMC members,

As per https://whimsy.apache.org/roster/ppmc/netbeans it looks like
it's only Geertjan and mentors who are moderating the NetBeans mailing
lists for now.

In view of the project's graduation I'd like to step down and maybe
other mentors want do to that as well?

To have enough moderators, could we have a 2-3 additional volunteers
for that task? You need to be a NetBeans PPMC member and
https://reference.apache.org/pmc/ml has the general instructions.

Currently, with a good spam filter I get just a few relevant messages
per week to moderate so it's not a lot of work.

As per https://www.apache.org/dev/infra-contact we first need to
collect the list of people stepping down or volunteering and then send
a single email to apm...@apache.org with the changes - unless someone
here has karma to make those changes ourselves, I don't.

-Bertrand

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

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

Re: bits.netbeans.org / javadocs / mavenutils

[Geertjan Wielenga]

netbeans-vm is our virtual machine at Apache.

Gj

On Mon, Nov 26, 2018 at 1:42 PM Eric Barboni  wrote:

> Hi
>  It will be to host apidoc for Apache Netbeans  and also the website for
> Apache NetBeans Maven Utilities.
>
>  Maven Artifacts for Apache NetBeans 9 and will I hope be on central.
>
>  I try to have it asap but, without website for utilities the migration
> after code donation is stuck.
>
> Best Regards
> Eric
> -Message d'origine-
> De : Jean-Marc Borer 
> Envoyé : lundi 26 novembre 2018 12:48
> À : dev@netbeans.incubator.apache.org
> Objet : Re: bits.netbeans.org / javadocs / mavenutils
>
> May I ask why "netbeans-vm"? This name makes no sense to me.
>
> On Mon, Nov 12, 2018 at 1:12 PM Antonio  wrote:
>
> > Hi,
> >
> > So infra suggested using ci.apache.org.
> >
> > Do we want to use that or not? Maybe we would build the artifacts
> > using our current jenkins setup and them transfer those to
> > netbeans-vm.apache.org?
> >
> > Now that the domains are operated within the ASF we could redirect
> > bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
> >
> > Thoughts?
> >
> > Cheers,
> > Antonio
> >
> > El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > > Thanks for the work Antonio
> > >
> > >   Where should we help and what we can do now?
> > >
> > > Regards
> > > Eric
> > > -Message d'origine-
> > > De : Antonio 
> > > Envoyé : mercredi 7 novembre 2018 14:13 À :
> > > dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > > javadocs / mavenutils
> > >
> > > Hi Eric,
> > >
> > > I think the point is that javadoc is published automatically. For
> > instance, for the apex-core project, see
> > >
> > >
> > https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4
> > /index.html
> > >
> > > Anyway feel free to ask whatever questions you consider to the JIRA
> > ticket with Infra. They know more than I do :-)
> > >
> > > Cheers,
> > > Antonio
> > >
> > >
> > > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> > >> Hi Antonio
> > >>I did not get the point here. What is the difference using
> > >> between
> > build.apache.org vs buildbot.apache ? Why do we need another type of ci
> ?
> > >>
> > >> Regards
> > >> Eric
> > >>
> > >> -Message d'origine-
> > >> De : Antonio 
> > >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> > >> dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> > >> javadocs / mavenutils
> > >>
> > >> Hi all,
> > >>
> > >> Gavin from infra is suggesting [1] that we use the Apache buildbot
> > >> [2]
> > to generate javadocs and other stuff (JNLP/Maven).
> > >>
> > >> I think it's a great idea, is it ok if I request one of these for
> > >> us
> > and we give it a go?
> > >>
> > >> Cheers,
> > >> Antonio
> > >>
> > >> [1]
> > >> https://issues.apache.org/jira/browse/INFRA-17202
> > >>
> > >> [2]
> > >> https://ci.apache.org/projects/
> > >>
> > >> El 2/11/18 a las 18:48, Antonio escribió:
> > >>> Hi,
> > >>>
> > >>> javadoc.tgz is just an example binary, probably not very
> > representative.
> > >>>
> > >>> The real problem arises when we want to host _development_ maven
> > >>> artifacts or JNLP binaries. That is big, and we just can't do that
> > >>> each eight hours using a git branch, I think.
> > >>>
> > >>> For releases I'd suggest:
> > >>>
> > >>> - Creating javadoc.tgz and distributing it along the rest of
> > >>> release binaries through the mirror system, as sources are. This
> > >>> may require chaning the release process.
> > >>> - Publishing the javadoc at netbeans.apache.org under an
> > >>> appropriate
> > >>> 9.0/10.0 subdirectory.
> > >>> - Linking from bits.netbeans.org back to netbeans.apache.org for
> > >>> these javadoc.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> Thanks,
> > >>> Antonio
> > >>>
> > >>>
> > >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
> >  On Fri, 2 Nov 2018 at 16:52, Antonio  wrote:
> > > Generating a 51Mb. binary file and hosting it in a git branch
> > > each eight hours simply won't scale.
> > 
> >  No kidding! :-)
> > 
> >  This is meant to be a short term fix for hosting release
> >  Javadocs, and possibly dev Javadocs with your date fix, and will
> >  proxy back to Oracle hosting for anything not there.  Of course,
> >  that's not necessarily useful here.
> > 
> >  But do we need that .tgz generated anyway?  Maybe a .tgz of the
> >  release docs on the mirror system alongside the release, which
> >  was discussed previously, is enough?
> > 
> >  Incidentally, speaking of release Javadoc, we should work out how
> >  to build those for NB10.  I had to manually edit some files for
> >  the
> >  NB9.0 ones.
> > 
> >  Best wishes,
> > 
> >  Neil
> > 
> >  -
> >  ---
> >  - To unsubscribe, e-mail:
> >  dev-unsubscr...@netbeans.incubator.apache.org
> >  For additional comma

Surefire plugin issue

[Jean-Marc Borer]

Hi all,

Guys, we are planning to move away from Ant in favor of Maven. This will
only be possible if the Maven echosystem is properly supported. Currently,
surefire error logs are still broken since 2.19 as I described in
https://issues.apache.org/jira/browse/NETBEANS-635

For example with surefire 2.19.1:

[image: image.png]
You can see that when I click on the link, an error message is displayed in
the status bar in the lower left corner.

This was broken in NB 8.2 and still is in NB 9.0

Am I missing something here?

Cheers,

JMB

RE: bits.netbeans.org / javadocs / mavenutils

[Eric Barboni]

Hi 
 It will be to host apidoc for Apache Netbeans  and also the website for  
Apache NetBeans Maven Utilities.

 Maven Artifacts for Apache NetBeans 9 and will I hope be on central. 

 I try to have it asap but, without website for utilities the migration after 
code donation is stuck.

Best Regards
Eric
-Message d'origine-
De : Jean-Marc Borer  
Envoyé : lundi 26 novembre 2018 12:48
À : dev@netbeans.incubator.apache.org
Objet : Re: bits.netbeans.org / javadocs / mavenutils

May I ask why "netbeans-vm"? This name makes no sense to me.

On Mon, Nov 12, 2018 at 1:12 PM Antonio  wrote:

> Hi,
>
> So infra suggested using ci.apache.org.
>
> Do we want to use that or not? Maybe we would build the artifacts 
> using our current jenkins setup and them transfer those to 
> netbeans-vm.apache.org?
>
> Now that the domains are operated within the ASF we could redirect 
> bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
>
> Thoughts?
>
> Cheers,
> Antonio
>
> El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > Thanks for the work Antonio
> >
> >   Where should we help and what we can do now?
> >
> > Regards
> > Eric
> > -Message d'origine-
> > De : Antonio 
> > Envoyé : mercredi 7 novembre 2018 14:13 À : 
> > dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org / 
> > javadocs / mavenutils
> >
> > Hi Eric,
> >
> > I think the point is that javadoc is published automatically. For
> instance, for the apex-core project, see
> >
> >
> https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4
> /index.html
> >
> > Anyway feel free to ask whatever questions you consider to the JIRA
> ticket with Infra. They know more than I do :-)
> >
> > Cheers,
> > Antonio
> >
> >
> > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> >> Hi Antonio
> >>I did not get the point here. What is the difference using 
> >> between
> build.apache.org vs buildbot.apache ? Why do we need another type of ci ?
> >>
> >> Regards
> >> Eric
> >>
> >> -Message d'origine-
> >> De : Antonio 
> >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> >> dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org / 
> >> javadocs / mavenutils
> >>
> >> Hi all,
> >>
> >> Gavin from infra is suggesting [1] that we use the Apache buildbot 
> >> [2]
> to generate javadocs and other stuff (JNLP/Maven).
> >>
> >> I think it's a great idea, is it ok if I request one of these for 
> >> us
> and we give it a go?
> >>
> >> Cheers,
> >> Antonio
> >>
> >> [1]
> >> https://issues.apache.org/jira/browse/INFRA-17202
> >>
> >> [2]
> >> https://ci.apache.org/projects/
> >>
> >> El 2/11/18 a las 18:48, Antonio escribió:
> >>> Hi,
> >>>
> >>> javadoc.tgz is just an example binary, probably not very
> representative.
> >>>
> >>> The real problem arises when we want to host _development_ maven 
> >>> artifacts or JNLP binaries. That is big, and we just can't do that 
> >>> each eight hours using a git branch, I think.
> >>>
> >>> For releases I'd suggest:
> >>>
> >>> - Creating javadoc.tgz and distributing it along the rest of 
> >>> release binaries through the mirror system, as sources are. This 
> >>> may require chaning the release process.
> >>> - Publishing the javadoc at netbeans.apache.org under an 
> >>> appropriate
> >>> 9.0/10.0 subdirectory.
> >>> - Linking from bits.netbeans.org back to netbeans.apache.org for 
> >>> these javadoc.
> >>>
> >>> Thoughts?
> >>>
> >>> Thanks,
> >>> Antonio
> >>>
> >>>
> >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
>  On Fri, 2 Nov 2018 at 16:52, Antonio  wrote:
> > Generating a 51Mb. binary file and hosting it in a git branch 
> > each eight hours simply won't scale.
> 
>  No kidding! :-)
> 
>  This is meant to be a short term fix for hosting release 
>  Javadocs, and possibly dev Javadocs with your date fix, and will 
>  proxy back to Oracle hosting for anything not there.  Of course, 
>  that's not necessarily useful here.
> 
>  But do we need that .tgz generated anyway?  Maybe a .tgz of the 
>  release docs on the mirror system alongside the release, which 
>  was discussed previously, is enough?
> 
>  Incidentally, speaking of release Javadoc, we should work out how 
>  to build those for NB10.  I had to manually edit some files for 
>  the
>  NB9.0 ones.
> 
>  Best wishes,
> 
>  Neil
> 
>  -
>  ---
>  - To unsubscribe, e-mail:
>  dev-unsubscr...@netbeans.incubator.apache.org
>  For additional commands, e-mail:
>  dev-h...@netbeans.incubator.apache.org
> 
>  For further information about the NetBeans mailing lists, visit:
>  https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+list
>  s
> 
> 
> 
> >>
> >> ---
> >> -- To unsubscribe, e-mail: 
> >> dev-unsubscr...@netbeans.incu

Re: Windows security warning constantly popping when starting Netbeans 9.0

[Jean-Marc Borer]

I'll answer to myself: I can uncheck the "Always ask before opening this
file". So isn't it possible anyway to have a proper publisher set
eventually?

Cheers

On Mon, Nov 26, 2018 at 12:30 PM Jean-Marc Borer  wrote:

>
> Hi all,
>
> I am wondering if I am the only one experiencing this Windows security
> alert with Netbeans 9.0 every time I launch the IDE?
>
> [image: image.png]
>
> *Product Version:* Apache NetBeans IDE 9.0 (Build
> incubator-netbeans-release-334-on-20180708)
>
> *Java:* 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12
>
> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_191-b12
>
> *System:* Windows 7 version 6.1 running on amd64; Cp1252; en (nb)
>
> *User directory:* C:\projects\.netbeans\9.0
>
> *Cache directory:* C:\projects\.netbeans\cache\9.0
>
>
> Best regards
>
>
> JMB
>

Windows security warning constantly popping when starting Netbeans 9.0

[Jean-Marc Borer]

Hi all,

I am wondering if I am the only one experiencing this Windows security
alert with Netbeans 9.0 every time I launch the IDE?

[image: image.png]

*Product Version:* Apache NetBeans IDE 9.0 (Build
incubator-netbeans-release-334-on-20180708)

*Java:* 1.8.0_191; Java HotSpot(TM) 64-Bit Server VM 25.191-b12

*Runtime:* Java(TM) SE Runtime Environment 1.8.0_191-b12

*System:* Windows 7 version 6.1 running on amd64; Cp1252; en (nb)

*User directory:* C:\projects\.netbeans\9.0

*Cache directory:* C:\projects\.netbeans\cache\9.0


Best regards


JMB

AW: NetBeans - the UI for Maven

[Christian Lenz]

Later on, I would like to prefer seeing everything related to Java (doesn’t 
matter Ant, Web, Maven, Gradle, Swing, JFx) under the Java Project Category. Of 
Course the rest could be in Sub categories

Java
- Swing Apps
- Web Apps
- JavaFX Apps
- HTML4J Apps
- CLI / Console App
- Whatever we have here

NetBeans Modules could be a Sub category too or separated from them.


Cheers

Chris



Von: Anton Epple
Gesendet: Montag, 26. November 2018 12:13
An: dev@netbeans.incubator.apache.org
Betreff: AW: NetBeans - the UI for Maven

Done, I updated the PR:

https://github.com/apache/incubator-netbeans/pull/1038

--Toni

Am 26.11.18, 10:28 schrieb "Anton Epple" :

Fully agree, I'll remove the (ic) __

Am 26.11.18, 10:22 schrieb "Emilian Bold" :

OK, let's make the cheapest PR we can do now and see how it looks (no
"Ant(ic)" please ;-) ). Then we can have an issue (or continue on this
thread) about how to redo the wizards for multiple build systems. 
Indeed,
if we go for the perfect solution we will still be stuck with having Ant
the default for a long time...

--emi


On Mon, Nov 26, 2018 at 10:26 AM  wrote:

> I'm not rushing. I read the proposal by Jaroslav and he has a point.
> Having ANT as the default is wrong. Maven should be the default.
> So I created a PR which does exactly that (and nothing else). I 
provided a
> (good) fix for the problem.
>
> I think it's great that this spawned a discussion about if we should 
unify
> the project wizard and change the grouping completely. But my fear 
is, that
> it prevents us from solving the initial problem. Some of the ideas 
are good
> (like thinking about grouping project wizards in a more logical way), 
some
> of them are bad in my opinion (like adding an extra step). All of them
> require a lot more discussion.
>
> One example:
>
> There's a wizard for JavaFX with ANT and one with Maven. If we add a 
build
> system choice in the wizard, the user will rightfully expect that 
this only
> influences what build system is used. But actually it will do much 
more.
> Both wizards create different applications, one is using FXML and CSS
> (Maven), the other isn't (Ant). So we'll have to discuss what to do: 
For us
> it's easier to convert the ANT project, but the Maven archetype is 
very
> opinionated in promoting FXML and requires me to delete a bunch of 
files
> every time I use it. So I would suggest to create a new archetype 
instead.
> And now I'm lying under the car covered in oil, while I actually 
wanted to
> change a lightbulb in the kitchen [1]
>
> The PR is the exact solution for the initial simple problem. I 
suggest to
> treat the other changes as a different RFE. If we decide to unify the
> wizards for different build systems, this is great, and it will wipe 
out my
> changes before any user has seen them. If we don't find the time, or 
cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emilian Bold 
> Gesendet: Sonntag, 25. November 2018 18:53
> An: NetBeans Dev@ 
> Betreff: Re: NetBeans - the UI for Maven
>
> I don't think there's any kind of rush to have a PR today.
>
> I like Geertjan's idea best:
>
> > IMHO there should be a single wizard named "Java SE Application" 
and a
> > single wizard named "Java Web Applicaton", both of which, in step 
two
> > or three, should let the user choose whether they want to build 
their
> > Java application with Maven, Gradle, or Ant.
>
> If it's more work it's more work, but then users get to pick the build
> system from a combobox and we just set the default to be Maven.
>
> I don't know that area that much but perhaps a we could have some SPI 
for
> build systems and installing Gradle stuff will automatically add it 
to that
> wizard combobox.
>
> Maybe users could also have an option to set their preferred build 
system
> so it always picks Gradle (or Ant or Maven) next time.
>
> --emi
>
>
> On Sun, Nov 25, 2018 at 7:48 PM  wrote:
>
> > Yeah, I realized it and uploaded them to the PR 😊.
> >
> > If we have something like:
> >
> > Java Application:
> >- Maven based
> > - ANT based
> > Java Web Application:
> >- Maven based
> > - ANT based
> > ...
  

Re: bits.netbeans.org / javadocs / mavenutils

[Jean-Marc Borer]

May I ask why "netbeans-vm"? This name makes no sense to me.

On Mon, Nov 12, 2018 at 1:12 PM Antonio  wrote:

> Hi,
>
> So infra suggested using ci.apache.org.
>
> Do we want to use that or not? Maybe we would build the artifacts using
> our current jenkins setup and them transfer those to
> netbeans-vm.apache.org?
>
> Now that the domains are operated within the ASF we could redirect
> bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
>
> Thoughts?
>
> Cheers,
> Antonio
>
> El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > Thanks for the work Antonio
> >
> >   Where should we help and what we can do now?
> >
> > Regards
> > Eric
> > -Message d'origine-
> > De : Antonio 
> > Envoyé : mercredi 7 novembre 2018 14:13
> > À : dev@netbeans.incubator.apache.org
> > Objet : Re: bits.netbeans.org / javadocs / mavenutils
> >
> > Hi Eric,
> >
> > I think the point is that javadoc is published automatically. For
> instance, for the apex-core project, see
> >
> >
> https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4/index.html
> >
> > Anyway feel free to ask whatever questions you consider to the JIRA
> ticket with Infra. They know more than I do :-)
> >
> > Cheers,
> > Antonio
> >
> >
> > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> >> Hi Antonio
> >>I did not get the point here. What is the difference using between
> build.apache.org vs buildbot.apache ? Why do we need another type of ci ?
> >>
> >> Regards
> >> Eric
> >>
> >> -Message d'origine-
> >> De : Antonio 
> >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> >> dev@netbeans.incubator.apache.org Objet : Re: bits.netbeans.org /
> >> javadocs / mavenutils
> >>
> >> Hi all,
> >>
> >> Gavin from infra is suggesting [1] that we use the Apache buildbot [2]
> to generate javadocs and other stuff (JNLP/Maven).
> >>
> >> I think it's a great idea, is it ok if I request one of these for us
> and we give it a go?
> >>
> >> Cheers,
> >> Antonio
> >>
> >> [1]
> >> https://issues.apache.org/jira/browse/INFRA-17202
> >>
> >> [2]
> >> https://ci.apache.org/projects/
> >>
> >> El 2/11/18 a las 18:48, Antonio escribió:
> >>> Hi,
> >>>
> >>> javadoc.tgz is just an example binary, probably not very
> representative.
> >>>
> >>> The real problem arises when we want to host _development_ maven
> >>> artifacts or JNLP binaries. That is big, and we just can't do that
> >>> each eight hours using a git branch, I think.
> >>>
> >>> For releases I'd suggest:
> >>>
> >>> - Creating javadoc.tgz and distributing it along the rest of release
> >>> binaries through the mirror system, as sources are. This may require
> >>> chaning the release process.
> >>> - Publishing the javadoc at netbeans.apache.org under an appropriate
> >>> 9.0/10.0 subdirectory.
> >>> - Linking from bits.netbeans.org back to netbeans.apache.org for
> >>> these javadoc.
> >>>
> >>> Thoughts?
> >>>
> >>> Thanks,
> >>> Antonio
> >>>
> >>>
> >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
>  On Fri, 2 Nov 2018 at 16:52, Antonio  wrote:
> > Generating a 51Mb. binary file and hosting it in a git branch each
> > eight hours simply won't scale.
> 
>  No kidding! :-)
> 
>  This is meant to be a short term fix for hosting release Javadocs,
>  and possibly dev Javadocs with your date fix, and will proxy back to
>  Oracle hosting for anything not there.  Of course, that's not
>  necessarily useful here.
> 
>  But do we need that .tgz generated anyway?  Maybe a .tgz of the
>  release docs on the mirror system alongside the release, which was
>  discussed previously, is enough?
> 
>  Incidentally, speaking of release Javadoc, we should work out how to
>  build those for NB10.  I had to manually edit some files for the
>  NB9.0 ones.
> 
>  Best wishes,
> 
>  Neil
> 
>  
>  - To unsubscribe, e-mail:
>  dev-unsubscr...@netbeans.incubator.apache.org
>  For additional commands, e-mail:
>  dev-h...@netbeans.incubator.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.incubator.apache.org
> >> For additional commands, e-mail:
> >> dev-h...@netbeans.incubator.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.incubator.apache.org
> >> For additional commands, e-mail:
> >> dev-h...@netbeans.incubator.apache.org
> >>
> >> For further information about the NetBeans mailing li

AW: NetBeans - the UI for Maven

[Anton Epple]

Done, I updated the PR:

https://github.com/apache/incubator-netbeans/pull/1038

--Toni

Am 26.11.18, 10:28 schrieb "Anton Epple" :

Fully agree, I'll remove the (ic) __

Am 26.11.18, 10:22 schrieb "Emilian Bold" :

OK, let's make the cheapest PR we can do now and see how it looks (no
"Ant(ic)" please ;-) ). Then we can have an issue (or continue on this
thread) about how to redo the wizards for multiple build systems. 
Indeed,
if we go for the perfect solution we will still be stuck with having Ant
the default for a long time...

--emi


On Mon, Nov 26, 2018 at 10:26 AM  wrote:

> I'm not rushing. I read the proposal by Jaroslav and he has a point.
> Having ANT as the default is wrong. Maven should be the default.
> So I created a PR which does exactly that (and nothing else). I 
provided a
> (good) fix for the problem.
>
> I think it's great that this spawned a discussion about if we should 
unify
> the project wizard and change the grouping completely. But my fear 
is, that
> it prevents us from solving the initial problem. Some of the ideas 
are good
> (like thinking about grouping project wizards in a more logical way), 
some
> of them are bad in my opinion (like adding an extra step). All of them
> require a lot more discussion.
>
> One example:
>
> There's a wizard for JavaFX with ANT and one with Maven. If we add a 
build
> system choice in the wizard, the user will rightfully expect that 
this only
> influences what build system is used. But actually it will do much 
more.
> Both wizards create different applications, one is using FXML and CSS
> (Maven), the other isn't (Ant). So we'll have to discuss what to do: 
For us
> it's easier to convert the ANT project, but the Maven archetype is 
very
> opinionated in promoting FXML and requires me to delete a bunch of 
files
> every time I use it. So I would suggest to create a new archetype 
instead.
> And now I'm lying under the car covered in oil, while I actually 
wanted to
> change a lightbulb in the kitchen [1]
>
> The PR is the exact solution for the initial simple problem. I 
suggest to
> treat the other changes as a different RFE. If we decide to unify the
> wizards for different build systems, this is great, and it will wipe 
out my
> changes before any user has seen them. If we don't find the time, or 
cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emilian Bold 
> Gesendet: Sonntag, 25. November 2018 18:53
> An: NetBeans Dev@ 
> Betreff: Re: NetBeans - the UI for Maven
>
> I don't think there's any kind of rush to have a PR today.
>
> I like Geertjan's idea best:
>
> > IMHO there should be a single wizard named "Java SE Application" 
and a
> > single wizard named "Java Web Applicaton", both of which, in step 
two
> > or three, should let the user choose whether they want to build 
their
> > Java application with Maven, Gradle, or Ant.
>
> If it's more work it's more work, but then users get to pick the build
> system from a combobox and we just set the default to be Maven.
>
> I don't know that area that much but perhaps a we could have some SPI 
for
> build systems and installing Gradle stuff will automatically add it 
to that
> wizard combobox.
>
> Maybe users could also have an option to set their preferred build 
system
> so it always picks Gradle (or Ant or Maven) next time.
>
> --emi
>
>
> On Sun, Nov 25, 2018 at 7:48 PM  wrote:
>
> > Yeah, I realized it and uploaded them to the PR 😊.
> >
> > If we have something like:
> >
> > Java Application:
> >- Maven based
> > - ANT based
> > Java Web Application:
> >- Maven based
> > - ANT based
> > ...
> >
> > This doesn't really move ANT out of sight, and is only slightly 
better
> > than what we have now. It also adds one more click to the wizard.
> >
> > In my opinion, the best solution would be a selection box in the
> > wizards, with the default set to Maven and ANT as the second option
> where possible.
> > But this would require a lot more effort. That's why for now I
> > proposed this simple PR which also does the job to change the 
default
> 

Re: NetBeans Platform 9

[Jean-Marc Borer]

Actually, I would suggest to get the code from
https://github.com/apache/incubator-netbeans/releases/tag/9.0

On Mon, Nov 26, 2018 at 9:54 AM Jean-Marc Borer  wrote:

> I should add, that I compiled the tag "release90" and that this version
> still uses groupid "org.netbeans.api" and not something with apache inside.
> Therefore I could simply replace the version id RELEASE82 by RELEASE90
> without any kind of adaptations. Nice.
>
> On Mon, Nov 26, 2018 at 9:50 AM Jean-Marc Borer  wrote:
>
>> Hi Christian,
>>
>> I recently did it myself. You need to download and compile the deploy
>> plugin yourself, because I could not find it on central or elsewhere. Get
>> it from :
>>
>>
>> https://github.com/apache/incubator-netbeans-mavenutils/tree/master/nb-repository-plugin
>>
>> Then go the sources you have cloned from
>> https://github.com/apache/incubator-netbeans and do:
>>
>> ant
>> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:download 
>> -DnexusIndexDirectory=..\nbrepoidx 
>> -DrepositoryUrl=https://repo.maven.apache.org/maven2ant build-nbms
>> ant build-source-zips
>> ant build-javadoc
>> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate 
>> -DnexusIndexDirectory=..\nbrepoidx -DforcedVersion=RELEASE90 
>> -DnetbeansInstallDirectory=nbbuild\netbeans 
>> -DnetbeansNbmDirectory=nbbuild\nbms 
>> -DnetbeansSourcesDirectory=nbbuild\build\source-zips 
>> -DnetbeansJavadocDirectory=nbbuild\build\javadoc
>>
>>
>>
>> Above it is for a local deployment of the artifacts. If you want to
>> deploy the artifacts into your own repository:
>>
>> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
>> -DnexusIndexDirectory=../nbrepoidx -DforcedVersion=RELEASE90
>> -DnetbeansInstallDirectory=nbbuild/netbeans
>> -DnetbeansNbmDirectory=nbbuild/nbms
>> -DnetbeansSourcesDirectory=nbbuild/build/source-zips -Ddetails=true
>> -DgeneratePom=true -DdeployUrl=http://
>>
>> Hope it helps,
>>
>> JMB
>>
>> On Wed, Nov 21, 2018 at 8:38 PM Christian Bourque <
>> christian.bour...@gmail.com> wrote:
>>
>>> Thanks a lot Neil!
>>>
>>> On Wed, Nov 21, 2018 at 1:45 PM Neil C Smith 
>>> wrote:
>>>
>>> > On Wed, 21 Nov 2018 at 18:39, Christian Bourque
>>> >  wrote:
>>> > > I'm looking for the Maven repository that contains the binary
>>> artefacts!
>>> >
>>> > There isn't one currently.  Look through the archive here for a few
>>> > threads on this, or this issue which has some info on building sources
>>> > for use with Maven -
>>> > https://issues.apache.org/jira/browse/NETBEANS-467
>>> >
>>> > Best wishes,
>>> >
>>> > Neil
>>> >
>>> > -
>>> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>>> > For additional commands, e-mail:
>>> dev-h...@netbeans.incubator.apache.org
>>> >
>>> > For further information about the NetBeans mailing lists, visit:
>>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> >
>>> >
>>> >
>>> >
>>>
>>

Re: NetBeans Platform 9

[Jean-Marc Borer]

I should add, that I compiled the tag "release90" and that this version
still uses groupid "org.netbeans.api" and not something with apache inside.
Therefore I could simply replace the version id RELEASE82 by RELEASE90
without any kind of adaptations. Nice.

On Mon, Nov 26, 2018 at 9:50 AM Jean-Marc Borer  wrote:

> Hi Christian,
>
> I recently did it myself. You need to download and compile the deploy
> plugin yourself, because I could not find it on central or elsewhere. Get
> it from :
>
>
> https://github.com/apache/incubator-netbeans-mavenutils/tree/master/nb-repository-plugin
>
> Then go the sources you have cloned from
> https://github.com/apache/incubator-netbeans and do:
>
> ant
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:download 
> -DnexusIndexDirectory=..\nbrepoidx 
> -DrepositoryUrl=https://repo.maven.apache.org/maven2ant build-nbms
> ant build-source-zips
> ant build-javadoc
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate 
> -DnexusIndexDirectory=..\nbrepoidx -DforcedVersion=RELEASE90 
> -DnetbeansInstallDirectory=nbbuild\netbeans 
> -DnetbeansNbmDirectory=nbbuild\nbms 
> -DnetbeansSourcesDirectory=nbbuild\build\source-zips 
> -DnetbeansJavadocDirectory=nbbuild\build\javadoc
>
>
>
> Above it is for a local deployment of the artifacts. If you want to deploy
> the artifacts into your own repository:
>
> mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
> -DnexusIndexDirectory=../nbrepoidx -DforcedVersion=RELEASE90
> -DnetbeansInstallDirectory=nbbuild/netbeans
> -DnetbeansNbmDirectory=nbbuild/nbms
> -DnetbeansSourcesDirectory=nbbuild/build/source-zips -Ddetails=true
> -DgeneratePom=true -DdeployUrl=http://
>
> Hope it helps,
>
> JMB
>
> On Wed, Nov 21, 2018 at 8:38 PM Christian Bourque <
> christian.bour...@gmail.com> wrote:
>
>> Thanks a lot Neil!
>>
>> On Wed, Nov 21, 2018 at 1:45 PM Neil C Smith 
>> wrote:
>>
>> > On Wed, 21 Nov 2018 at 18:39, Christian Bourque
>> >  wrote:
>> > > I'm looking for the Maven repository that contains the binary
>> artefacts!
>> >
>> > There isn't one currently.  Look through the archive here for a few
>> > threads on this, or this issue which has some info on building sources
>> > for use with Maven -
>> > https://issues.apache.org/jira/browse/NETBEANS-467
>> >
>> > Best wishes,
>> >
>> > Neil
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>> >
>> > For further information about the NetBeans mailing lists, visit:
>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> >
>> >
>> >
>> >
>>
>

Re: NetBeans Platform 9

[Jean-Marc Borer]

Hi Christian,

I recently did it myself. You need to download and compile the deploy
plugin yourself, because I could not find it on central or elsewhere. Get
it from :

https://github.com/apache/incubator-netbeans-mavenutils/tree/master/nb-repository-plugin

Then go the sources you have cloned from
https://github.com/apache/incubator-netbeans and do:

ant
mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:download
-DnexusIndexDirectory=..\nbrepoidx
-DrepositoryUrl=https://repo.maven.apache.org/maven2ant build-nbms
ant build-source-zips
ant build-javadoc
mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
-DnexusIndexDirectory=..\nbrepoidx -DforcedVersion=RELEASE90
-DnetbeansInstallDirectory=nbbuild\netbeans
-DnetbeansNbmDirectory=nbbuild\nbms
-DnetbeansSourcesDirectory=nbbuild\build\source-zips
-DnetbeansJavadocDirectory=nbbuild\build\javadoc



Above it is for a local deployment of the artifacts. If you want to deploy
the artifacts into your own repository:

mvn org.netbeans.maven:nb-repository-plugin:1.4-SNAPSHOT:populate
-DnexusIndexDirectory=../nbrepoidx -DforcedVersion=RELEASE90
-DnetbeansInstallDirectory=nbbuild/netbeans
-DnetbeansNbmDirectory=nbbuild/nbms
-DnetbeansSourcesDirectory=nbbuild/build/source-zips -Ddetails=true
-DgeneratePom=true -DdeployUrl=http://

Hope it helps,

JMB

On Wed, Nov 21, 2018 at 8:38 PM Christian Bourque <
christian.bour...@gmail.com> wrote:

> Thanks a lot Neil!
>
> On Wed, Nov 21, 2018 at 1:45 PM Neil C Smith 
> wrote:
>
> > On Wed, 21 Nov 2018 at 18:39, Christian Bourque
> >  wrote:
> > > I'm looking for the Maven repository that contains the binary
> artefacts!
> >
> > There isn't one currently.  Look through the archive here for a few
> > threads on this, or this issue which has some info on building sources
> > for use with Maven -
> > https://issues.apache.org/jira/browse/NETBEANS-467
> >
> > Best wishes,
> >
> > Neil
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>

AW: NetBeans - the UI for Maven

[Anton Epple]

Fully agree, I'll remove the (ic) __

Am 26.11.18, 10:22 schrieb "Emilian Bold" :

OK, let's make the cheapest PR we can do now and see how it looks (no
"Ant(ic)" please ;-) ). Then we can have an issue (or continue on this
thread) about how to redo the wizards for multiple build systems. Indeed,
if we go for the perfect solution we will still be stuck with having Ant
the default for a long time...

--emi


On Mon, Nov 26, 2018 at 10:26 AM  wrote:

> I'm not rushing. I read the proposal by Jaroslav and he has a point.
> Having ANT as the default is wrong. Maven should be the default.
> So I created a PR which does exactly that (and nothing else). I provided a
> (good) fix for the problem.
>
> I think it's great that this spawned a discussion about if we should unify
> the project wizard and change the grouping completely. But my fear is, 
that
> it prevents us from solving the initial problem. Some of the ideas are 
good
> (like thinking about grouping project wizards in a more logical way), some
> of them are bad in my opinion (like adding an extra step). All of them
> require a lot more discussion.
>
> One example:
>
> There's a wizard for JavaFX with ANT and one with Maven. If we add a build
> system choice in the wizard, the user will rightfully expect that this 
only
> influences what build system is used. But actually it will do much more.
> Both wizards create different applications, one is using FXML and CSS
> (Maven), the other isn't (Ant). So we'll have to discuss what to do: For 
us
> it's easier to convert the ANT project, but the Maven archetype is very
> opinionated in promoting FXML and requires me to delete a bunch of files
> every time I use it. So I would suggest to create a new archetype instead.
> And now I'm lying under the car covered in oil, while I actually wanted to
> change a lightbulb in the kitchen [1]
>
> The PR is the exact solution for the initial simple problem. I suggest to
> treat the other changes as a different RFE. If we decide to unify the
> wizards for different build systems, this is great, and it will wipe out 
my
> changes before any user has seen them. If we don't find the time, or 
cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emilian Bold 
> Gesendet: Sonntag, 25. November 2018 18:53
> An: NetBeans Dev@ 
> Betreff: Re: NetBeans - the UI for Maven
>
> I don't think there's any kind of rush to have a PR today.
>
> I like Geertjan's idea best:
>
> > IMHO there should be a single wizard named "Java SE Application" and a
> > single wizard named "Java Web Applicaton", both of which, in step two
> > or three, should let the user choose whether they want to build their
> > Java application with Maven, Gradle, or Ant.
>
> If it's more work it's more work, but then users get to pick the build
> system from a combobox and we just set the default to be Maven.
>
> I don't know that area that much but perhaps a we could have some SPI for
> build systems and installing Gradle stuff will automatically add it to 
that
> wizard combobox.
>
> Maybe users could also have an option to set their preferred build system
> so it always picks Gradle (or Ant or Maven) next time.
>
> --emi
>
>
> On Sun, Nov 25, 2018 at 7:48 PM  wrote:
>
> > Yeah, I realized it and uploaded them to the PR 😊.
> >
> > If we have something like:
> >
> > Java Application:
> >- Maven based
> > - ANT based
> > Java Web Application:
> >- Maven based
> > - ANT based
> > ...
> >
> > This doesn't really move ANT out of sight, and is only slightly better
> > than what we have now. It also adds one more click to the wizard.
> >
> > In my opinion, the best solution would be a selection box in the
> > wizards, with the default set to Maven and ANT as the second option
> where possible.
> > But this would require a lot more effort. That's why for now I
> > proposed this simple PR which also does the job to change the default
> > Java build tool in project wizards from ANT to Maven.
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Neil C Smith 
> > Gesendet: Sonntag, 25. November 2018 15:47
> > An: dev@netbeans.incubator.apache.org
> > Betreff: Re: NetBeans - the UI for Maven
> >
> > On Sun, 25 Nov 2018, 14:14 Anton Epple  >
> > > Putting all ANT related stuff in its own category has the benefit of
> > > moving it out of focus, while still keeping it around for those who
> > > need it.
> > >
> >
> > A sub-cat

Re: NetBeans - the UI for Maven

[Emilian Bold]

OK, let's make the cheapest PR we can do now and see how it looks (no
"Ant(ic)" please ;-) ). Then we can have an issue (or continue on this
thread) about how to redo the wizards for multiple build systems. Indeed,
if we go for the perfect solution we will still be stuck with having Ant
the default for a long time...

--emi


On Mon, Nov 26, 2018 at 10:26 AM  wrote:

> I'm not rushing. I read the proposal by Jaroslav and he has a point.
> Having ANT as the default is wrong. Maven should be the default.
> So I created a PR which does exactly that (and nothing else). I provided a
> (good) fix for the problem.
>
> I think it's great that this spawned a discussion about if we should unify
> the project wizard and change the grouping completely. But my fear is, that
> it prevents us from solving the initial problem. Some of the ideas are good
> (like thinking about grouping project wizards in a more logical way), some
> of them are bad in my opinion (like adding an extra step). All of them
> require a lot more discussion.
>
> One example:
>
> There's a wizard for JavaFX with ANT and one with Maven. If we add a build
> system choice in the wizard, the user will rightfully expect that this only
> influences what build system is used. But actually it will do much more.
> Both wizards create different applications, one is using FXML and CSS
> (Maven), the other isn't (Ant). So we'll have to discuss what to do: For us
> it's easier to convert the ANT project, but the Maven archetype is very
> opinionated in promoting FXML and requires me to delete a bunch of files
> every time I use it. So I would suggest to create a new archetype instead.
> And now I'm lying under the car covered in oil, while I actually wanted to
> change a lightbulb in the kitchen [1]
>
> The PR is the exact solution for the initial simple problem. I suggest to
> treat the other changes as a different RFE. If we decide to unify the
> wizards for different build systems, this is great, and it will wipe out my
> changes before any user has seen them. If we don't find the time, or cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emilian Bold 
> Gesendet: Sonntag, 25. November 2018 18:53
> An: NetBeans Dev@ 
> Betreff: Re: NetBeans - the UI for Maven
>
> I don't think there's any kind of rush to have a PR today.
>
> I like Geertjan's idea best:
>
> > IMHO there should be a single wizard named "Java SE Application" and a
> > single wizard named "Java Web Applicaton", both of which, in step two
> > or three, should let the user choose whether they want to build their
> > Java application with Maven, Gradle, or Ant.
>
> If it's more work it's more work, but then users get to pick the build
> system from a combobox and we just set the default to be Maven.
>
> I don't know that area that much but perhaps a we could have some SPI for
> build systems and installing Gradle stuff will automatically add it to that
> wizard combobox.
>
> Maybe users could also have an option to set their preferred build system
> so it always picks Gradle (or Ant or Maven) next time.
>
> --emi
>
>
> On Sun, Nov 25, 2018 at 7:48 PM  wrote:
>
> > Yeah, I realized it and uploaded them to the PR 😊.
> >
> > If we have something like:
> >
> > Java Application:
> >- Maven based
> > - ANT based
> > Java Web Application:
> >- Maven based
> > - ANT based
> > ...
> >
> > This doesn't really move ANT out of sight, and is only slightly better
> > than what we have now. It also adds one more click to the wizard.
> >
> > In my opinion, the best solution would be a selection box in the
> > wizards, with the default set to Maven and ANT as the second option
> where possible.
> > But this would require a lot more effort. That's why for now I
> > proposed this simple PR which also does the job to change the default
> > Java build tool in project wizards from ANT to Maven.
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Neil C Smith 
> > Gesendet: Sonntag, 25. November 2018 15:47
> > An: dev@netbeans.incubator.apache.org
> > Betreff: Re: NetBeans - the UI for Maven
> >
> > On Sun, 25 Nov 2018, 14:14 Anton Epple  >
> > > Putting all ANT related stuff in its own category has the benefit of
> > > moving it out of focus, while still keeping it around for those who
> > > need it.
> > >
> >
> > A sub-category could do that too? Been doing that myself recently.
> > Don't disagree with your point or approach either, just that it's
> > possible to get some way towards what Geertjan and Chris are
> > suggesting without code changes if that's the direction of travel.
> >
> > Attachments get stripped btw.
> >
> > Best wishes,
> >
> > Neil
> >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-h...

AW: NetBeans - the UI for Maven

[toni.epple]

I'm not rushing. I read the proposal by Jaroslav and he has a point. Having ANT 
as the default is wrong. Maven should be the default.
So I created a PR which does exactly that (and nothing else). I provided a 
(good) fix for the problem.

I think it's great that this spawned a discussion about if we should unify the 
project wizard and change the grouping completely. But my fear is, that it 
prevents us from solving the initial problem. Some of the ideas are good (like 
thinking about grouping project wizards in a more logical way), some of them 
are bad in my opinion (like adding an extra step). All of them require a lot 
more discussion.

One example:

There's a wizard for JavaFX with ANT and one with Maven. If we add a build 
system choice in the wizard, the user will rightfully expect that this only 
influences what build system is used. But actually it will do much more. Both 
wizards create different applications, one is using FXML and CSS (Maven), the 
other isn't (Ant). So we'll have to discuss what to do: For us it's easier to 
convert the ANT project, but the Maven archetype is very opinionated in 
promoting FXML and requires me to delete a bunch of files every time I use it. 
So I would suggest to create a new archetype instead. And now I'm lying under 
the car covered in oil, while I actually wanted to change a lightbulb in the 
kitchen [1]

The PR is the exact solution for the initial simple problem. I suggest to treat 
the other changes as a different RFE. If we decide to unify the wizards for 
different build systems, this is great, and it will wipe out my changes before 
any user has seen them. If we don't find the time, or cannot find a solution, 
then at least we've fixed the initial problem.

--Toni

[1] https://www.youtube.com/watch?v=AbSehcT19u0



-Ursprüngliche Nachricht-
Von: Emilian Bold  
Gesendet: Sonntag, 25. November 2018 18:53
An: NetBeans Dev@ 
Betreff: Re: NetBeans - the UI for Maven

I don't think there's any kind of rush to have a PR today.

I like Geertjan's idea best:

> IMHO there should be a single wizard named "Java SE Application" and a 
> single wizard named "Java Web Applicaton", both of which, in step two 
> or three, should let the user choose whether they want to build their 
> Java application with Maven, Gradle, or Ant.

If it's more work it's more work, but then users get to pick the build system 
from a combobox and we just set the default to be Maven.

I don't know that area that much but perhaps a we could have some SPI for build 
systems and installing Gradle stuff will automatically add it to that wizard 
combobox.

Maybe users could also have an option to set their preferred build system so it 
always picks Gradle (or Ant or Maven) next time.

--emi


On Sun, Nov 25, 2018 at 7:48 PM  wrote:

> Yeah, I realized it and uploaded them to the PR 😊.
>
> If we have something like:
>
> Java Application:
>- Maven based
> - ANT based
> Java Web Application:
>- Maven based
> - ANT based
> ...
>
> This doesn't really move ANT out of sight, and is only slightly better 
> than what we have now. It also adds one more click to the wizard.
>
> In my opinion, the best solution would be a selection box in the 
> wizards, with the default set to Maven and ANT as the second option where 
> possible.
> But this would require a lot more effort. That's why for now I 
> proposed this simple PR which also does the job to change the default 
> Java build tool in project wizards from ANT to Maven.
>
>
>
> -Ursprüngliche Nachricht-
> Von: Neil C Smith 
> Gesendet: Sonntag, 25. November 2018 15:47
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: NetBeans - the UI for Maven
>
> On Sun, 25 Nov 2018, 14:14 Anton Epple 
> > Putting all ANT related stuff in its own category has the benefit of 
> > moving it out of focus, while still keeping it around for those who 
> > need it.
> >
>
> A sub-category could do that too? Been doing that myself recently. 
> Don't disagree with your point or approach either, just that it's 
> possible to get some way towards what Geertjan and Chris are 
> suggesting without code changes if that's the direction of travel.
>
> Attachments get stripped btw.
>
> Best wishes,
>
> Neil
>
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-h...@netbeans.incubator.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.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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