Ant build of NetBeans RCP with --release

[Neil C Smith]

Hi All,

I'm currently working on updating PraxisLIVE to use NB11 as a base.  I
was looking at making it possible (not for releases for now) to
compile on JDK11 using the --release flag.  At the moment I've just
added that in as an attribute for the javac task in the harness
common.xml  Might be a useful PR for those of us stuck using Ant?  But
...

So, the problem is that this works fine from the command line, but
fails from the IDE with the message "error: release version 8 not
supported".  Same Ant, and as far as I can tell same compiler
arguments.  Any idea if there's something obvious I'm missing here?

Thanks and best wishes,

Neil

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

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

Re: Maven Remote

[Geertjan Wielenga]

Tell him to join this mailing list and ask and discuss here.

https://netbeans.apache.org/community/mailing-lists.html

Gj

On Tue, Apr 30, 2019 at 7:53 PM Kenneth Fogel 
wrote:

> A follower on LinkedIn has asked me who he could contact to contribute to
> NetBeans to support remote development such as for a Raspberry Pi with a
> Maven based project. Let me know how he can get involved and I'll pass it
> on.
>
> Ken
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Maven Remote

[Kenneth Fogel]

A follower on LinkedIn has asked me who he could contact to contribute to 
NetBeans to support remote development such as for a Raspberry Pi with a Maven 
based project. Let me know how he can get involved and I'll pass it on.

Ken 



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

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

Fwd: Re: Donation Request for kotlin-netbeans

[Laszlo Kishalmi]

They are competitors, they have proprietary stuff as well, but they are 
not necessary evil.


 Forwarded Message 
Subject:Re: Donation Request for kotlin-netbeans
Date:   Tue, 30 Apr 2019 12:18:37 +0200
From:   Dmitry Jemerov 
To: Laszlo Kishalmi 
CC: m...@jetbrains.com



Hi Laszlo,

We'd be happy to hand over the development of the plugin to your team 
and to transfer the code to Apache NetBeans. We'll still need to figure 
out the technical issues, because the plugin depends on code that wasn't 
very cleanly extracted from Kotlin and IntelliJ (see this comment 
). 
(All the code in question is also Apache licensed, but we'll need to set 
up a sane build procedure so that you could depend on published 
artifacts and not commit jars to the repository).


I'll be happy to be the technical point of contact for the transition 
process for the beginning.


On Tue, Apr 30, 2019 at 11:12 AM Laszlo Kishalmi 
mailto:laszlo.kisha...@gmail.com>> wrote:


   Dear Dmitry,

   I'm a member of Apache NetBeans PMC and the release manager of the last
   two Apache NetBeans releases. It seems there are some interest on
   Kotlin
   support inside NetBeans and we came across that there is actually an
   unmaintained plugin from JetBrains for that.

   I've read through the
   https://github.com/JetBrains/kotlin-netbeans/issues/122 issue and
   realized, that wit all that talk, we have never asked for donating that
   code to Apache NetBeans.

   So here I'm asking you, that is it possible that we take over that code
   and maintain it in our repositories, we would maintain and probably
   release that along with the IDE?

   As the current code is already in Apache 2.0 license, an e-mail from a
   responsible person would be enough to do the donation.

   Thank you in advance!

   Laszlo Kishalmi

Re: "incubating" on Downloads page

[Antonio Vieiro]

Also download links in Apache mirrors need the incubator directory, AFAIK.

El El mar, 30 abr 2019 a las 14:47, Bertrand Delacretaz <
bdelacre...@apache.org> escribió:

> Hi,
>
> On Tue, Apr 30, 2019 at 2:41 PM Geertjan Wielenga 
> wrote:
> > ...Is there anything blocking us from removing 'incubating' everywhere
> on this
> > page:
> > https://netbeans.apache.org/download/nb110/nb110.html ..
>
> Releases which were made during incubation need to keep the
> "incubating" qualifier but for later releases it can be removed.
>
> It might be useful to create an explanation page about the "just out
> of incubation" status and link to that from such places.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: "incubating" on Downloads page

[Bertrand Delacretaz]

Hi,

On Tue, Apr 30, 2019 at 2:41 PM Geertjan Wielenga  wrote:
> ...Is there anything blocking us from removing 'incubating' everywhere on this
> page:
> https://netbeans.apache.org/download/nb110/nb110.html ..

Releases which were made during incubation need to keep the
"incubating" qualifier but for later releases it can be removed.

It might be useful to create an explanation page about the "just out
of incubation" status and link to that from such places.

-Bertrand

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

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

"incubating" on Downloads page

[Geertjan Wielenga]

Hi all,

Is there anything blocking us from removing 'incubating' everywhere on this
page:

https://netbeans.apache.org/download/nb110/nb110.html

Just checking,

Gj

Re: kotlin support

[Geertjan Wielenga]

https://github.com/JetBrains/kotlin-netbeans/issues/137

Gj

On Tue, Apr 30, 2019 at 12:40 PM Antonio Vieiro  wrote:

> I’d suggest asking them first. After all we’re polite guys...
>
> El El mar, 30 abr 2019 a las 10:47, Christian Lenz  >
> escribió:
>
> > Is there a Need to ask them for the code? Why not fork the code and add
> it
> > into the codebase? It is still Apache 2.0. Is it still possible that they
> > say: no we don’t want to see the code inside the core code? I’m not a
> > lawyer, just asking.
> >
> >
> > Cheers
> >
> > Chris
> >
> >
> >
> > Von: Antonio
> > Gesendet: Dienstag, 30. April 2019 09:52
> > An: dev@netbeans.apache.org
> > Betreff: Re: kotlin support
> >
> > Wise words!
> >
> > El 30/04/2019 a las 9:50, Laszlo Kishalmi escribió:
> > > Apache 2.0 licensed, so on that part there is nothing wrong with that.
> > >
> > > We have just never actually did the simple thing to ask for their code.
> > >
> > > I do not say we shall not do the LSP, we shall keep on that route as
> > well.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
> >
>

Re: kotlin support

[Antonio Vieiro]

I’d suggest asking them first. After all we’re polite guys...

El El mar, 30 abr 2019 a las 10:47, Christian Lenz 
escribió:

> Is there a Need to ask them for the code? Why not fork the code and add it
> into the codebase? It is still Apache 2.0. Is it still possible that they
> say: no we don’t want to see the code inside the core code? I’m not a
> lawyer, just asking.
>
>
> Cheers
>
> Chris
>
>
>
> Von: Antonio
> Gesendet: Dienstag, 30. April 2019 09:52
> An: dev@netbeans.apache.org
> Betreff: Re: kotlin support
>
> Wise words!
>
> El 30/04/2019 a las 9:50, Laszlo Kishalmi escribió:
> > Apache 2.0 licensed, so on that part there is nothing wrong with that.
> >
> > We have just never actually did the simple thing to ask for their code.
> >
> > I do not say we shall not do the LSP, we shall keep on that route as
> well.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>

AW: kotlin support

[Christian Lenz]

Is there a Need to ask them for the code? Why not fork the code and add it into 
the codebase? It is still Apache 2.0. Is it still possible that they say: no we 
don’t want to see the code inside the core code? I’m not a lawyer, just asking.


Cheers

Chris



Von: Antonio
Gesendet: Dienstag, 30. April 2019 09:52
An: dev@netbeans.apache.org
Betreff: Re: kotlin support

Wise words!

El 30/04/2019 a las 9:50, Laszlo Kishalmi escribió:
> Apache 2.0 licensed, so on that part there is nothing wrong with that.
> 
> We have just never actually did the simple thing to ask for their code.
> 
> I do not say we shall not do the LSP, we shall keep on that route as well.

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

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

Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

[Laszlo Kishalmi]

To be honest, I do not think that would be needed.

There would be no API/SPI changes in the patches, and yes I'm still 
talking about Gradle Support specific patch, as I can manage that easily 
on my own. So make a dependency on them would probably not worth the 
effort. I'm just trying to keep this as simple as I could.


On 4/30/19 1:14 AM, Eric Barboni wrote:

Hi,
As a maven fanboy.

Once we vote on a release110_patch I think we can manage a "RELEASE110-PATCH1" 
release base on the sources of the voted patch ? It will generate every bits but will 
work I guess.

Regards
Eric


-Message d'origine-
De : Christian Lenz 
Envoyé : mardi 30 avril 2019 09:31
À : dev@netbeans.apache.org
Objet : AW: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

The stuff from Jaroslav sounds good to me 


Cheers

Chris



Von: Laszlo Kishalmi
Gesendet: Dienstag, 30. April 2019 08:07
An: dev@netbeans.apache.org
Betreff: Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release


On 4/29/19 9:56 PM, Jaroslav Tulach wrote:

Hello Laszlo.

NetBeans used to be doing "patch releases" in the past. They consist
of generating new catalog with NBM files which then automatically
appears in the IDEs.

That is significantly easier than full release. In the context of Apache, I'd:

- create branch release110_patch1 rooted at release110
- selectively backported some fixes from master to that branch
- whenever a backport is made, update version numbers + dependencies
of affected modules only

Then we need to vote and release the source ZIP file and upload the
NBMs. No need to upload the binary ZIP file itself. IDE update center
catalog then needs to point to the new NBMs.


Yes, that's what I thought to be needed, then people turned this discussion 
into a general release.

Dne neděle 28. dubna 2019 15:47:20 CEST, Laszlo Kishalmi napsal(a):

In order to be able to produce real time based releases our release
process and it's infrastructure have to be improved. Right now the
process consists of ~30 steps out of which ~15 require changes on the
actual code to be released. These includes:

* New Splash Screens (As you see on the list I'm trying to work on
  this as well now)

That isn't needed.


* New versions to display in several places

That isn't needed either.


* Bumping the versions of the modules on two branches

Only bump versions of modules that are affected - only those will be
downloaded by Plugin Manager.


* API Signature sealing

We can live without this. At least our past experience shows that
there are very little API changes in the patch releases anyway.

Overall this could be significantly less work than regular release.
I'd suggest to start with a branch and a builder that builds source ZIP and 
NBMs.
Then we can start testing the updated modules.
-jt




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

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




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

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






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

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





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

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

RE: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

[Eric Barboni]

Hi,
As a maven fanboy.

Once we vote on a release110_patch I think we can manage a "RELEASE110-PATCH1" 
release base on the sources of the voted patch ? It will generate every bits 
but will work I guess.

Regards
Eric


-Message d'origine-
De : Christian Lenz  
Envoyé : mardi 30 avril 2019 09:31
À : dev@netbeans.apache.org
Objet : AW: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

The stuff from Jaroslav sounds good to me 


Cheers

Chris



Von: Laszlo Kishalmi
Gesendet: Dienstag, 30. April 2019 08:07
An: dev@netbeans.apache.org
Betreff: Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release


On 4/29/19 9:56 PM, Jaroslav Tulach wrote:
> Hello Laszlo.
>
> NetBeans used to be doing "patch releases" in the past. They consist 
> of generating new catalog with NBM files which then automatically 
> appears in the IDEs.
>
> That is significantly easier than full release. In the context of Apache, I'd:
>
> - create branch release110_patch1 rooted at release110
> - selectively backported some fixes from master to that branch
> - whenever a backport is made, update version numbers + dependencies 
> of affected modules only
>
> Then we need to vote and release the source ZIP file and upload the 
> NBMs. No need to upload the binary ZIP file itself. IDE update center 
> catalog then needs to point to the new NBMs.
>
Yes, that's what I thought to be needed, then people turned this discussion 
into a general release.
> Dne neděle 28. dubna 2019 15:47:20 CEST, Laszlo Kishalmi napsal(a):
>> In order to be able to produce real time based releases our release 
>> process and it's infrastructure have to be improved. Right now the 
>> process consists of ~30 steps out of which ~15 require changes on the 
>> actual code to be released. These includes:
>>
>>* New Splash Screens (As you see on the list I'm trying to work on
>>  this as well now)
> That isn't needed.
>
>>* New versions to display in several places
> That isn't needed either.
>
>>* Bumping the versions of the modules on two branches
> Only bump versions of modules that are affected - only those will be 
> downloaded by Plugin Manager.
>
>>* API Signature sealing
> We can live without this. At least our past experience shows that 
> there are very little API changes in the patch releases anyway.
>
> Overall this could be significantly less work than regular release. 
> I'd suggest to start with a branch and a builder that builds source ZIP and 
> NBMs.
> Then we can start testing the updated modules.
> -jt
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

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

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






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

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

Gradle Java EE Support

[Laszlo Kishalmi]

Dear all,

As I promised I made a PR with a my Gradle Support for Java EE projects: 
https://github.com/apache/netbeans/pull/1215


It is needed to be polished and tested, but the "happy paths" are 
working. Like let's suppose you have a Glassfish installed, then it is 
possible to create a Gradle project with a new project Wizard and that 
could be compiled and deployed to the target application server. JSP and 
JSF code completions are working as well.


I might added support for HTML5/JS parts, but I'm not sure how they 
work, I guess all I did is to add some JS support service through the 
module layers.


My latest real update on that is: 
https://blog.lkishalmi.eu/2016/11/08/gradle-web-projects-are-coming/



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

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

Re: kotlin support

[Antonio]

Wise words!

El 30/04/2019 a las 9:50, Laszlo Kishalmi escribió:

Apache 2.0 licensed, so on that part there is nothing wrong with that.

We have just never actually did the simple thing to ask for their code.

I do not say we shall not do the LSP, we shall keep on that route as well.


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

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

Re: kotlin support

[Laszlo Kishalmi]

Well, actually the JetBrains plugin is Open Source, even Apache 2.0 
licensed, so on that part there is nothing wrong with that.


We have just never actually did the simple thing to ask for their code.

I do not say we shall not do the LSP, we shall keep on that route as well.

On 4/30/19 12:33 AM, Antonio wrote:

Hi,

That's one more reason to depend on community based plugins (or 
language servers) than on proprietary ones.


Cheers,
Antonio

El 30/04/2019 a las 8:54, Geertjan Wielenga escribió:

Yup, that makes sense to me, at least, to focus on LSP instead.

Indeed, we should have asked in that discussion whether they'd like to
donate their Kotlin plugin to Apache NetBeans. Personally, I ended up 
being
very frustrated with their continual "well, there was never much 
interest

in this plugin and Kotlin in general from the NetBean community", etc,
while that very clearly was not true and they never created a solid 
plugin

to begin with.

Gj

On Tue, Apr 30, 2019 at 9:29 AM Antonio  wrote:


Hi all,

There's a Kotlin Language Server here [1] that seems to be well
supported (11 contributors) and is available under the MIT license.

Maybe we should focus our efforts in helping out the LSP support in
NetBeans [2], which is a long time effort by Jan.

If we help out Jan with the LSP support our users would be able to use
NetBeans for a wide range of languages [3], from Fortran, Nim and Rust
to Lua, TypeScript and PowerShell (but for refactoring, which is 
lacking

in LSP AFAIK) and, with [1] for Kotlin.

Cheers,
Antonio


[1]
https://github.com/fwcd/KotlinLanguageServer

[2]
https://github.com/apache/netbeans/pull/926

[3]
https://microsoft.github.io/language-server-protocol/implementors/servers/ 



El 29/04/2019 a las 19:58, Mike Billman escribió:
I was curious what kind of kotlin support currently exists for 
netbeans.


Mike Billman
Senior Software Engineer
CPTE

[qclogo]

11800 Conrey Rd
Suite 150
Cincinnati, OH 45249

T +1 513 469 1424
E mikebill...@qcsoftware.com
F +1 513 469 1425




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

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








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

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





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

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

Re: kotlin support

[Antonio]

Hi,

That's one more reason to depend on community based plugins (or language 
servers) than on proprietary ones.


Cheers,
Antonio

El 30/04/2019 a las 8:54, Geertjan Wielenga escribió:

Yup, that makes sense to me, at least, to focus on LSP instead.

Indeed, we should have asked in that discussion whether they'd like to
donate their Kotlin plugin to Apache NetBeans. Personally, I ended up being
very frustrated with their continual "well, there was never much interest
in this plugin and Kotlin in general from the NetBean community", etc,
while that very clearly was not true and they never created a solid plugin
to begin with.

Gj

On Tue, Apr 30, 2019 at 9:29 AM Antonio  wrote:


Hi all,

There's a Kotlin Language Server here [1] that seems to be well
supported (11 contributors) and is available under the MIT license.

Maybe we should focus our efforts in helping out the LSP support in
NetBeans [2], which is a long time effort by Jan.

If we help out Jan with the LSP support our users would be able to use
NetBeans for a wide range of languages [3], from Fortran, Nim and Rust
to Lua, TypeScript and PowerShell (but for refactoring, which is lacking
in LSP AFAIK) and, with [1] for Kotlin.

Cheers,
Antonio


[1]
https://github.com/fwcd/KotlinLanguageServer

[2]
https://github.com/apache/netbeans/pull/926

[3]
https://microsoft.github.io/language-server-protocol/implementors/servers/

El 29/04/2019 a las 19:58, Mike Billman escribió:

I was curious what kind of kotlin support currently exists for netbeans.

Mike Billman
Senior Software Engineer
CPTE

[qclogo]

11800 Conrey Rd
Suite 150
Cincinnati, OH 45249

T +1 513 469 1424
E mikebill...@qcsoftware.com
F +1 513 469 1425




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

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








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

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

AW: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

[Christian Lenz]

The stuff from Jaroslav sounds good to me 


Cheers

Chris



Von: Laszlo Kishalmi
Gesendet: Dienstag, 30. April 2019 08:07
An: dev@netbeans.apache.org
Betreff: Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release


On 4/29/19 9:56 PM, Jaroslav Tulach wrote:
> Hello Laszlo.
>
> NetBeans used to be doing "patch releases" in the past. They consist of
> generating new catalog with NBM files which then automatically appears in the
> IDEs.
>
> That is significantly easier than full release. In the context of Apache, I'd:
>
> - create branch release110_patch1 rooted at release110
> - selectively backported some fixes from master to that branch
> - whenever a backport is made, update version numbers + dependencies of
> affected modules only
>
> Then we need to vote and release the source ZIP file and upload the NBMs. No
> need to upload the binary ZIP file itself. IDE update center catalog then
> needs to point to the new NBMs.
>
Yes, that's what I thought to be needed, then people turned this 
discussion into a general release.
> Dne neděle 28. dubna 2019 15:47:20 CEST, Laszlo Kishalmi napsal(a):
>> In order to be able to produce real time based releases our release
>> process and it's infrastructure have to be improved. Right now the
>> process consists of ~30 steps out of which ~15 require changes on the
>> actual code to be released. These includes:
>>
>>* New Splash Screens (As you see on the list I'm trying to work on
>>  this as well now)
> That isn't needed.
>
>>* New versions to display in several places
> That isn't needed either.
>
>>* Bumping the versions of the modules on two branches
> Only bump versions of modules that are affected - only those will be
> downloaded by Plugin Manager.
>
>>* API Signature sealing
> We can live without this. At least our past experience shows that there are
> very little API changes in the patch releases anyway.
>
> Overall this could be significantly less work than regular release. I'd
> suggest to start with a branch and a builder that builds source ZIP and NBMs.
> Then we can start testing the updated modules.
> -jt
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

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

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

Re: kotlin support

[Geertjan Wielenga]

Yup, that makes sense to me, at least, to focus on LSP instead.

Indeed, we should have asked in that discussion whether they'd like to
donate their Kotlin plugin to Apache NetBeans. Personally, I ended up being
very frustrated with their continual "well, there was never much interest
in this plugin and Kotlin in general from the NetBean community", etc,
while that very clearly was not true and they never created a solid plugin
to begin with.

Gj

On Tue, Apr 30, 2019 at 9:29 AM Antonio  wrote:

> Hi all,
>
> There's a Kotlin Language Server here [1] that seems to be well
> supported (11 contributors) and is available under the MIT license.
>
> Maybe we should focus our efforts in helping out the LSP support in
> NetBeans [2], which is a long time effort by Jan.
>
> If we help out Jan with the LSP support our users would be able to use
> NetBeans for a wide range of languages [3], from Fortran, Nim and Rust
> to Lua, TypeScript and PowerShell (but for refactoring, which is lacking
> in LSP AFAIK) and, with [1] for Kotlin.
>
> Cheers,
> Antonio
>
>
> [1]
> https://github.com/fwcd/KotlinLanguageServer
>
> [2]
> https://github.com/apache/netbeans/pull/926
>
> [3]
> https://microsoft.github.io/language-server-protocol/implementors/servers/
>
> El 29/04/2019 a las 19:58, Mike Billman escribió:
> > I was curious what kind of kotlin support currently exists for netbeans.
> >
> > Mike Billman
> > Senior Software Engineer
> > CPTE
> >
> > [qclogo]
> >
> > 11800 Conrey Rd
> > Suite 150
> > Cincinnati, OH 45249
> >
> > T +1 513 469 1424
> > E mikebill...@qcsoftware.com
> > F +1 513 469 1425
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: kotlin support

[Antonio]

Hi all,

There's a Kotlin Language Server here [1] that seems to be well 
supported (11 contributors) and is available under the MIT license.


Maybe we should focus our efforts in helping out the LSP support in 
NetBeans [2], which is a long time effort by Jan.


If we help out Jan with the LSP support our users would be able to use 
NetBeans for a wide range of languages [3], from Fortran, Nim and Rust 
to Lua, TypeScript and PowerShell (but for refactoring, which is lacking 
in LSP AFAIK) and, with [1] for Kotlin.


Cheers,
Antonio


[1]
https://github.com/fwcd/KotlinLanguageServer

[2]
https://github.com/apache/netbeans/pull/926

[3]
https://microsoft.github.io/language-server-protocol/implementors/servers/

El 29/04/2019 a las 19:58, Mike Billman escribió:

I was curious what kind of kotlin support currently exists for netbeans.

Mike Billman
Senior Software Engineer
CPTE

[qclogo]

11800 Conrey Rd
Suite 150
Cincinnati, OH 45249

T +1 513 469 1424
E mikebill...@qcsoftware.com
F +1 513 469 1425




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

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

Re: kotlin support

[Laszlo Kishalmi]

Well, I was reading

https://github.com/JetBrains/kotlin-netbeans/issues/122

I was a bit surprised that we had not asked them about donating that 
code. I can ask a few people there, though I have no real connection to 
the JetBrains.


Also I could test how this stuff can be integrated into the NetBeans 
codebase.


On 4/29/19 10:52 PM, Geertjan Wielenga wrote:

Ideally the sources of the current state of the NetBeans Kotlin plugin
would be donated to Apache NetBeans. Does anyone have the right connections
to ask for this to happen?

Gj

On Tuesday, April 30, 2019, Mario Schroeder  wrote:


Yes, maintain as well.

Laszlo Kishalmi  schrieb am Di., 30. Apr. 2019,
00:10:


Only supporter or willing to maintain the code as well?

On 4/29/19 11:31 AM, Mario Schroeder wrote:

Count me in as a supporter.

Am Mo., 29. Apr. 2019 um 20:16 Uhr schrieb Laszlo Kishalmi <
laszlo.kisha...@gmail.com>:


There is an unmaintained plugin actually from JetBrains:

https://github.com/JetBrains/kotlin-netbeans

If there would be someone interested to support/maintain Kotlin we

might

ask JetBrains for contribute this one to Apache NetBeans.


On 4/29/19 10:58 AM, Mike Billman wrote:

I was curious what kind of kotlin support currently exists for

netbeans.

Mike Billman

Senior Software Engineer

CPTE

qclogo

11800 Conrey Rd

Suite 150

Cincinnati, OH 45249

T +1 513 469 1424

E mikebill...@qcsoftware.com 

F +1 513 469 1425


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

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






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

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

Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

[Laszlo Kishalmi]

On 4/29/19 9:56 PM, Jaroslav Tulach wrote:

Hello Laszlo.

NetBeans used to be doing "patch releases" in the past. They consist of
generating new catalog with NBM files which then automatically appears in the
IDEs.

That is significantly easier than full release. In the context of Apache, I'd:

- create branch release110_patch1 rooted at release110
- selectively backported some fixes from master to that branch
- whenever a backport is made, update version numbers + dependencies of
affected modules only

Then we need to vote and release the source ZIP file and upload the NBMs. No
need to upload the binary ZIP file itself. IDE update center catalog then
needs to point to the new NBMs.

Yes, that's what I thought to be needed, then people turned this 
discussion into a general release.

Dne neděle 28. dubna 2019 15:47:20 CEST, Laszlo Kishalmi napsal(a):

In order to be able to produce real time based releases our release
process and it's infrastructure have to be improved. Right now the
process consists of ~30 steps out of which ~15 require changes on the
actual code to be released. These includes:

   * New Splash Screens (As you see on the list I'm trying to work on
 this as well now)

That isn't needed.


   * New versions to display in several places

That isn't needed either.


   * Bumping the versions of the modules on two branches

Only bump versions of modules that are affected - only those will be
downloaded by Plugin Manager.


   * API Signature sealing

We can live without this. At least our past experience shows that there are
very little API changes in the patch releases anyway.

Overall this could be significantly less work than regular release. I'd
suggest to start with a branch and a builder that builds source ZIP and NBMs.
Then we can start testing the updated modules.
-jt




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

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





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

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