Re: Maven embedded licence

2020-03-11 Thread Enrico Olivelli 
Eric,
Mostra probably it is the original file bundled with a library with EPL
license.
Unfortunately there is no standard format


Enrico


Il Mer 11 Mar 2020, 18:18 Eric Barboni  ha scritto:

> Hi
>
> During my attempt to embedd maven 3.6.3
>
>
>
> I found some strange formatted licence. Why are the license in "html"
> source
> ?  and not plain text ?
>
>
> https://github.com/apache/netbeans/blob/87af9d7f07a6b0fc63417e705e84d02fb2a6
> 84a6/java/maven.embedder/external/apache-maven-3.6.3-epl-license.txt
> 
>
>
>
> Best Regards
>
> Eric
>
>

Re: Opening Gradle + Kotlin DSL (was Re: Building NetBeans with Gradle)

2020-03-01 Thread Enrico Olivelli 
I have nuked my .cache and .netbeans folders.
Fresh new NetBeans 11.3.
Initially it did not recognize Calcite folder.
Then I have started the 'create project' wizard selecting Gradle Application,
then I saw the activation of Java (nbjavac, javafx) and then the
Activation of Groovy module

Now I able to open Calcite with NetBeans !!

Thank you so much
You saved me from using IntelliJ !!!

Enrico

Il giorno sab 29 feb 2020 alle ore 07:30 Laszlo Kishalmi
 ha scritto:
>
> Are you on 11.3? Because with that the project is recognized, I can open
> it, it downloads a ton of external library but generally works, even sub
> projects can be opened. The only thing does not work is recognizing the
> Kotlin sourcesets, though that support could be in 12.0
>
> On 2/28/20 10:05 PM, Enrico Olivelli wrote:
> > Il Ven 28 Feb 2020, 22:43 Laszlo Kishalmi  ha
> > scritto:
> >
> >> NetBeans Gradle Plugin recognizes projects with Kotlin DSL  (from 11.3).
> >>
> > I am trying to open Apache Calcite but NB doesn't recognize the folder as a
> > project.
> >
> > https://github.com/apache/calcite
> >
> > I was going to try IntelliJ but your news is sooo cool, I really would like
> > to use NB!
> >
> > Can you please check?
> >
> > Enrico
> >
> > We have some Kotlin support via TextMate lexer, so some syntax
> >> highlighting is there as well.
> >>
> >> On 2/27/20 11:09 PM, Mario Schroeder wrote:
> >>> Hi Lazlo,
> >>>
> >>> those are great news. Thanks for sharing.
> >>>
> >>> I also hope that the Kotlin support is taking up speed than we could even
> >>> support the Gradle Kotlin DSL.
> >>>
> >>> Laszlo Kishalmi  schrieb am Fr., 28. Feb.
> >> 2020,
> >>> 02:23:
> >>>
> >>>> Dear all,
> >>>>
> >>>> I just would like to share the progress of my secret project: build
> >>>> NetBeans with Gradle
> >>>>
> >>>> I'm still not sure how far I would like to go with this experiment, but
> >>>> if nothing else it could be a good test data for the Gradle Support.
> >>>>
> >>>> I had the following milestones in my mind:
> >>>>
> >>>> M0: Done: Get the project dependencies straight, without having circular
> >>>> dependencies: Right now it has 813 sub-projects in the known clusters
> >>>>
> >>>> M1: Done: Get the modules in the Platform cluster (and the harness
> >>>> cluster) compileable.
> >>>>
> >>>> M2: TBD: Make the unit tests pass for the Platform Cluster.
> >>>>
> >>>> M3: TBD: Make the output of the Platform cluster actually runable.
> >>>>
> >>>> How it works:
> >>>>
> >>>> I have a specific NetBeans Gradle Plugin which reads the
> >>>> nbproject/clusters.properties and each module nbproject/project.xml file
> >>>> to get the dependency configuration. other configuration items are read
> >>>> from the nbproject.properties file. In theory we do not have to do any
> >>>> changes for an ordinary module it shall work out of the box without even
> >>>> having a build.gradle file. There are however some special cases where
> >>>> build.gradle file is required. Unfortunately there are some dependency
> >>>> tangles between the modules causing circular dependency in Gradle. In
> >>>> these cases I had to split up the modules between test and source
> >> projects.
> >>>> If anyone would like to have a look:
> >>>>
> >>>> please clone the gradle2 branch of my fork:
> >>>> https://github.com/lkishalmi/netbeans
> >>>>
> >>>> The Gradle build right now needs the help to fetch the external
> >>>> dependencies: ant download-all-extbins
> >>>>
> >>>> But after that one:
> >>>>
> >>>> ./gradlew buildPlatformCluster -x check
> >>>>
> >>>> shall work. (It currently requires JDK 11 or up)
> >>>>
> >>>>
> >>>> -
> >>>> 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:
> >>>&g

Opening Gradle + Kotlin DSL (was Re: Building NetBeans with Gradle)

2020-02-28 Thread Enrico Olivelli 
Il Ven 28 Feb 2020, 22:43 Laszlo Kishalmi  ha
scritto:

> NetBeans Gradle Plugin recognizes projects with Kotlin DSL  (from 11.3).
>

I am trying to open Apache Calcite but NB doesn't recognize the folder as a
project.

https://github.com/apache/calcite

I was going to try IntelliJ but your news is sooo cool, I really would like
to use NB!

Can you please check?

Enrico

We have some Kotlin support via TextMate lexer, so some syntax
> highlighting is there as well.
>
> On 2/27/20 11:09 PM, Mario Schroeder wrote:
> > Hi Lazlo,
> >
> > those are great news. Thanks for sharing.
> >
> > I also hope that the Kotlin support is taking up speed than we could even
> > support the Gradle Kotlin DSL.
> >
> > Laszlo Kishalmi  schrieb am Fr., 28. Feb.
> 2020,
> > 02:23:
> >
> >> Dear all,
> >>
> >> I just would like to share the progress of my secret project: build
> >> NetBeans with Gradle
> >>
> >> I'm still not sure how far I would like to go with this experiment, but
> >> if nothing else it could be a good test data for the Gradle Support.
> >>
> >> I had the following milestones in my mind:
> >>
> >> M0: Done: Get the project dependencies straight, without having circular
> >> dependencies: Right now it has 813 sub-projects in the known clusters
> >>
> >> M1: Done: Get the modules in the Platform cluster (and the harness
> >> cluster) compileable.
> >>
> >> M2: TBD: Make the unit tests pass for the Platform Cluster.
> >>
> >> M3: TBD: Make the output of the Platform cluster actually runable.
> >>
> >> How it works:
> >>
> >> I have a specific NetBeans Gradle Plugin which reads the
> >> nbproject/clusters.properties and each module nbproject/project.xml file
> >> to get the dependency configuration. other configuration items are read
> >> from the nbproject.properties file. In theory we do not have to do any
> >> changes for an ordinary module it shall work out of the box without even
> >> having a build.gradle file. There are however some special cases where
> >> build.gradle file is required. Unfortunately there are some dependency
> >> tangles between the modules causing circular dependency in Gradle. In
> >> these cases I had to split up the modules between test and source
> projects.
> >>
> >> If anyone would like to have a look:
> >>
> >> please clone the gradle2 branch of my fork:
> >> https://github.com/lkishalmi/netbeans
> >>
> >> The Gradle build right now needs the help to fetch the external
> >> dependencies: ant download-all-extbins
> >>
> >> But after that one:
> >>
> >> ./gradlew buildPlatformCluster -x check
> >>
> >> shall work. (It currently requires JDK 11 or up)
> >>
> >>
> >> -
> >> 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: Building NetBeans with Gradle

2020-02-28 Thread Enrico Olivelli 
Interesting.

Was also Robert working on building Netbeans with Maven?

Enrico

Il Ven 28 Feb 2020, 08:09 Mario Schroeder  ha
scritto:

> Hi Lazlo,
>
> those are great news. Thanks for sharing.
>
> I also hope that the Kotlin support is taking up speed than we could even
> support the Gradle Kotlin DSL.
>
> Laszlo Kishalmi  schrieb am Fr., 28. Feb. 2020,
> 02:23:
>
> > Dear all,
> >
> > I just would like to share the progress of my secret project: build
> > NetBeans with Gradle
> >
> > I'm still not sure how far I would like to go with this experiment, but
> > if nothing else it could be a good test data for the Gradle Support.
> >
> > I had the following milestones in my mind:
> >
> > M0: Done: Get the project dependencies straight, without having circular
> > dependencies: Right now it has 813 sub-projects in the known clusters
> >
> > M1: Done: Get the modules in the Platform cluster (and the harness
> > cluster) compileable.
> >
> > M2: TBD: Make the unit tests pass for the Platform Cluster.
> >
> > M3: TBD: Make the output of the Platform cluster actually runable.
> >
> > How it works:
> >
> > I have a specific NetBeans Gradle Plugin which reads the
> > nbproject/clusters.properties and each module nbproject/project.xml file
> > to get the dependency configuration. other configuration items are read
> > from the nbproject.properties file. In theory we do not have to do any
> > changes for an ordinary module it shall work out of the box without even
> > having a build.gradle file. There are however some special cases where
> > build.gradle file is required. Unfortunately there are some dependency
> > tangles between the modules causing circular dependency in Gradle. In
> > these cases I had to split up the modules between test and source
> projects.
> >
> > If anyone would like to have a look:
> >
> > please clone the gradle2 branch of my fork:
> > https://github.com/lkishalmi/netbeans
> >
> > The Gradle build right now needs the help to fetch the external
> > dependencies: ant download-all-extbins
> >
> > But after that one:
> >
> > ./gradlew buildPlatformCluster -x check
> >
> > shall work. (It currently requires JDK 11 or up)
> >
> >
> > -
> > 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: [NOTICE] Apache NetBeans 12.0 merge windows OPEN

2020-02-25 Thread Enrico Olivelli 
Eric,
I have filed this issue about the integration with Apache Tomcat, that
does not work with latest  Tomcat release
https://issues.apache.org/jira/browse/NETBEANS-3917

I am trying to work on it,
is it possible to list it in the candidates for 12.0 ?

Enrico

Il giorno mar 25 feb 2020 alle ore 23:06 Josh Juneau
 ha scritto:
>
> Thanks Eric, looking forward to 12.0!
>
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
>
> > On Feb 25, 2020, at 8:27 AM, Eric Barboni  wrote:
> >
> > Hi folks,
> >
> >
> >
> > All post release commits are done (sigtests and spec version increments).
> > Consider master mergeable again.
> >
> >
> >
> > Feature freeze for Apache 12.0 is in a few week (March 15th ). This will be
> > the LTS version with NetCAT process.
> >
> > So maybe not the time for complete new breaking changes :p
> >
> > Thanks to everyone for collaboration.
> >
> >
> >
> > Just in case:
> >
> > I'm up to do release manager another round but any volunteer welcome.
> >
> >
> >
> > Best Regards,
> >
> > Eric
> >
> > (lvl2 release manager)
> >

-
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: [VOTE] Release Apache NetBeans 11.3 [vote candidate 1]

2020-02-21 Thread Enrico Olivelli 
Il Ven 21 Feb 2020, 17:20 Geertjan Wielenga  ha
scritto:

> This will involve quite some work and it is too late for 11.3, I suggest we
> leave this for 12.0, scheduled for April.
>

Makes sense.


> In the meantime, the more investigation you can do on this, the better --
> AFAIK no one is specifically working on Tomcat integration and if you could
> pick this up by at least identifying where in the code the problem comes
> from, that would be great.
>

I will create a ticket and eventually ask for pointers in code.


Enrico



> Gj
>
> On Fri, Feb 21, 2020 at 5:12 PM Enrico Olivelli 
> wrote:
>
> > Hi Eric,
> > I am testing the staged binaries and I see that NetBeans 11.3 is not
> > able to use Apache Tomcat 9.0.31.
> > It works with Apache Tomcat 9.0.30.
> >
> > The very same issue is with NetBeans 11.2.
> >
> > As Apache Tomcat 9.0.31 is the latest and greatest version of Tomcat I
> > feel it would be better to make the latest and greatest NetBeans work
> > with it out of the box.
> >
> > I can create a JIRA, but I don't know NetBeans internals and I cannot
> > provide a quick fix (I should learn how NetBeans works) and I expect
> > that you want to cut a new release candidate soon
> >
> > Hope that helps
> > Enrico
> >
> >
> > Il giorno ven 21 feb 2020 alle ore 14:32 Josh Juneau
> >  ha scritto:
> > >
> > > +1 (other than the LICENSE as pointed out by Matthias)
> > >
> > > Tested on OSX 10.14.6
> > > OpenJDK Runtime Environment (Zulu 8.42.0.23-CA-macosx) (build
> > 1.8.0_232-b18)
> > >
> > > Josh Juneau
> > > juneau...@gmail.com
> > > http://jj-blogger.blogspot.com
> > > https://www.apress.com/us/search?query=Juneau
> > > <https://www.apress.com/index.php/author/author/view/id/1866>
> > >
> > >
> > >
> > > On Wed, Feb 19, 2020 at 10:19 AM Eric Barboni 
> wrote:
> > >
> > > > Dear community,
> > > >
> > > >
> > > >
> > > > Sorry for the delay, artefacts are ready since 3 days but we hit a
> per
> > file
> > > > size limitation on the distribution server. Thanks to INFRA this now
> > ok.
> > > >
> > > >
> > > >
> > > > This is our first voting candidate for the 11.3 release of Apache
> > NetBeans.
> > > > Note that this is our first release vote where you are required to
> > check
> > > > both sources and convenience binaries before voting!
> > > >
> > > >
> > > >
> > > > See requirements below.
> > > >
> > > > Apache NetBeans 11.3 constitutes all clusters in the Apache NetBeans
> > Git
> > > > repo, which together provide the NetBeans Platform (i.e., the
> > underlying
> > > > application framework), as well as all the modules that provide the
> > Java
> > > > SE,
> > > > Java EE, PHP, JavaScript and Groovy features of Apache NetBeans.
> > > >
> > > >
> > > >
> > > > Build artefacts are available here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/
> > > >
> > > >
> > > >
> > > > They were built by the Jenkins pipeline and moved to their place:
> > > >
> > > >
> > > >
> >
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> > > > ns/job/release113/13
> > > > <
> >
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release113/13
> > >
> > > >
> > > >
> > > >
> > > > We are primarily voting on:
> > > >
> > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/netbeans-11.3-
> > > > source.zip
> > > > <
> >
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/netbeans-11.3-source.zip
> > >
> > > >
> > > >
> > > >
> > > > SHA512:
> > > >
> > > >
> > > >
> >
> 5c9152d571993f116c94fe968066ec8ca288c76353b4406c0de4d6e0941a4678724c73447444
> > > > 8128f9f9ff4dd79a944598d5760311ecea7695437d4debcde75c
> > > > netbeans-11.3-source.zip
> > > >
> > > >
> > >

Re: [VOTE] Release Apache NetBeans 11.3 [vote candidate 1]

2020-02-21 Thread Enrico Olivelli 
Hi Eric,
I am testing the staged binaries and I see that NetBeans 11.3 is not
able to use Apache Tomcat 9.0.31.
It works with Apache Tomcat 9.0.30.

The very same issue is with NetBeans 11.2.

As Apache Tomcat 9.0.31 is the latest and greatest version of Tomcat I
feel it would be better to make the latest and greatest NetBeans work
with it out of the box.

I can create a JIRA, but I don't know NetBeans internals and I cannot
provide a quick fix (I should learn how NetBeans works) and I expect
that you want to cut a new release candidate soon

Hope that helps
Enrico


Il giorno ven 21 feb 2020 alle ore 14:32 Josh Juneau
 ha scritto:
>
> +1 (other than the LICENSE as pointed out by Matthias)
>
> Tested on OSX 10.14.6
> OpenJDK Runtime Environment (Zulu 8.42.0.23-CA-macosx) (build 1.8.0_232-b18)
>
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> 
>
>
>
> On Wed, Feb 19, 2020 at 10:19 AM Eric Barboni  wrote:
>
> > Dear community,
> >
> >
> >
> > Sorry for the delay, artefacts are ready since 3 days but we hit a per file
> > size limitation on the distribution server. Thanks to INFRA this now ok.
> >
> >
> >
> > This is our first voting candidate for the 11.3 release of Apache NetBeans.
> > Note that this is our first release vote where you are required to check
> > both sources and convenience binaries before voting!
> >
> >
> >
> > See requirements below.
> >
> > Apache NetBeans 11.3 constitutes all clusters in the Apache NetBeans Git
> > repo, which together provide the NetBeans Platform (i.e., the underlying
> > application framework), as well as all the modules that provide the Java
> > SE,
> > Java EE, PHP, JavaScript and Groovy features of Apache NetBeans.
> >
> >
> >
> > Build artefacts are available here:
> >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/
> >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/
> >
> >
> >
> > They were built by the Jenkins pipeline and moved to their place:
> >
> >
> > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> > ns/job/release113/13
> > 
> >
> >
> >
> > We are primarily voting on:
> >
> >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/netbeans-11.3-
> > source.zip
> > 
> >
> >
> >
> > SHA512:
> >
> >
> > 5c9152d571993f116c94fe968066ec8ca288c76353b4406c0de4d6e0941a4678724c73447444
> > 8128f9f9ff4dd79a944598d5760311ecea7695437d4debcde75c
> > netbeans-11.3-source.zip
> >
> >
> >
> > KEYS file:
> >
> > https://dist.apache.org/repos/dist/release/netbeans/KEYS
> >
> >
> >
> > --
> >
> >
> >
> > Associated to the primary source item you will have (generated with
> > pipeline
> > mentioned above)
> >
> > under https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/
> >
> >   binaries associated to the source
> >
> >   netbeans-11.3-bin.zip
> >
> >   as well as update content under nbms folder
> >
> >
> >
> > under
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/
> >
> >   you will find platform cluster build
> >
> >   netbeans-platform-11.3-bin
> >
> >   netbeans-platform-11.3-source
> >
> >
> >
> > Associated Apache Maven artefacts RELEASE113 can be found at
> > https://repository.apache.org/content/repositories/orgapachenetbeans-1055
> >
> > Artefacts are composed of jars,nbm,sources,javadocs,pom.
> >
> > --
> >
> >
> >
> > Apache NetBeans Git Repo tag: 11.3-vc1 :
> >
> > https://github.com/apache/netbeans/tree/11.3-vc1
> >
> >
> >
> >
> >
> > Release specific wiki page:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.3
> >
> >
> >
> >
> >
> > Before voting +1 you are required to download the signed source code
> > package, compile it as provided, and test the resulting executable on your
> > own platform, along with also verifying that the package meets the
> > requirements of the ASF policy on releases - see
> > http://www.apache.org/legal/release-policy.html#management
> >
> >
> >
> > In particular, you should (at least) follow these steps.
> >
> >
> >
> > 1. Download the artefact to be voted on and unzip it.
> >
> > 2. Check that the artefact does not contain any jar files, except for:
> >
> > -
> >
> > platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/
> > empty.jar
> >
> > - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
> >
> > - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
> >
> > - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
> >
> > - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
> >
> > which are only jars by their name
> >
> > 3. Verify the cryptographic signatures, the

Re: Code One Java IDE Wars

2019-08-06 Thread Enrico Olivelli 
Netbeans is the best IDE for Maven

My 2 cents

Enrico

Il mar 6 ago 2019, 07:58 Tomas Poledny  ha scritto:

> From my POV killer fetures are:
> Maven support - everything works from installing like a charm.
> Java EE support - it was amazing in age of 8.2 and I hope that it will be
> amazing again (I still miss support for Wildfly).
>
>
> On Tue, Aug 6, 2019 at 7:12 AM John Neffenger  wrote:
>
> > On 8/5/19 11:30 AM, Kenneth Fogel wrote:
> > > Please suggest any part of NetBeans that makes it superior to Eclipse,
> > IntelliJ or Visual Studio Code.
> >
> > I'm not familiar with Visual Studio Code, but I've used NetBeans,
> > Eclipse, and IntelliJ off and on for years. NetBeans is the only IDE
> > that makes it easy to develop software for all of the following:
> >
> > - native C libraries,
> > - cross-platform C libraries (compiling for ARM on Intel),
> > - Java applications,
> > - Java Web applications (servlets), and
> > - all the browser stuff (HTML, CSS, JavaScript).
> >
> > Furthermore, I can set up remote Java platforms to run and debug my Java
> > applications on remote devices over an SSH connection. And NetBeans does
> > it almost out of the box after installing a few trouble-free plug-ins.
> >
> > The only thing that made me keep trying the others was the decade-long
> > font problem that NetBeans had on Debian distributions like Ubuntu. [1]
> > All that time, Eclipse and IntelliJ had great-looking fonts. But now
> > even that problem is fixed! [2]
> >
> > Thanks,
> > John
> >
> > [1] https://github.com/jgneff/openjdk-freetype
> >
> > [2]
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Font+Rendering+Issues
> >
> > -
> > 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: [VOTE] Release Apache NetBeans 11.1 [vote candidate 2]

2019-07-17 Thread Enrico Olivelli 
+1 (non binding)
the upgrade from 11.0 work like charm
tested the binaries on Linux + AdoptOpenJDK12

Enrico


Il giorno mer 17 lug 2019 alle ore 14:50 Mike Billman <
mikebill...@qcsoftware.com> ha scritto:

> +1 (non-binding)
>
> The one issue I had with beta2 is resolved 
>
> Mike
>
> -Original Message-
> From: John McDonnell 
> Sent: Wednesday, July 17, 2019 4:17 AM
> To: dev@netbeans.apache.org
> Subject: Re: [VOTE] Release Apache NetBeans 11.1 [vote candidate 2]
>
> +1 binding
>
> On Wed, 17 Jul 2019 at 08:54, Kai Uwe Pel  wrote:
>
> > +1   binding
> >
> > Thanks
> > Kai
> >
> >
> > On 7/16/2019 5:57 PM, Neil C Smith wrote:
> > > Dear all,
> > >
> > > This is our second voting candidate for the 11.1 release of Apache
> > > NetBeans, following 11.1-beta4 and a fix to the critical issue that
> > > made us pull the first vote.  There have been no changes between
> > > beta4 and this voting candidate.
> > >
> > > Apache NetBeans 11.1 constitutes all clusters in the Apache NetBeans
> > > Git repo, which together provide the NetBeans Platform (i.e., the
> > > underlying application framework), as well as all the modules that
> > > provide the Java SE, Java EE, PHP, JavaScript and Groovy features of
> > > Apache NetBeans.
> > >
> > > Build artefacts are available here:
> > > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc2/
> > >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.1
> > -vc2/
> > >
> > > Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and
> > > NOTICE files, as well as a README file with build instructions,
> > > which are the same as these:
> > > https://github.com/apache/netbeans/blob/release111/README.md
> > >
> > > We are voting on:
> > >
> > https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc2/netb
> > eans-11.1-vc2-source.zip
> > >
> > > SHA512:
> > >
> > 44d551f579587eafea30b3b3d9a9095520fb2dc028d63a1e7a31c6e52882c371c8f8f1
> > ac32d836694fefea269e52bf092e1976cf2c58accd36c816e009248e08
> > >   ./netbeans-11.1-vc2-source.zip
> > >
> > > KEYS file:
> > > https://dist.apache.org/repos/dist/release/netbeans/KEYS
> > >
> > > Apache NetBeans Git Repo tag: 11.1-vc2 :
> > > https://github.com/apache/netbeans/tree/11.1-vc2
> > >
> > > Note: NetBeans license violation checks are managed via the
> > > rat-exclusions.txt file:
> > >
> > https://github.com/apache/netbeans/blob/release111/nbbuild/rat-exclusi
> > ons.txt
> > >
> > > Rat report shows no unknown licenses, except for license files:
> > >
> > https://builds.apache.org/job/netbeans-release/428/artifact/rat-releas
> > e-temp/nbbuild/build/rat-report.txt
> > >
> > > Release specific wiki page:
> > >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+1
> > 1.1
> > >
> > >
> > > How (and what) to try out with the release:
> > >
> > > 1. Download the artefact to be voted on and unzip it.
> > > 2. Check that the artefact does not contain any jar files, except for:
> > >  -
> > platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate
> > /data/empty.jar
> > >  - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
> > >  -
> enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
> > >  - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
> > >  - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
> > >  which are only jars by their name 3. Verify the cryptographic
> > > signatures, the NOTICE and LICENSE file 4. Build it using the README
> > > provided by the artefact.
> > > 5. Look in nbbuild/netbeans for the NetBeans installation created by
> > > the build process and try running it.
> > >
> > > This vote is going to be open at least 72 hours, vote with +1, 0,
> > > and
> > > -1 as usual.  Please mark your vote with (binding) if you're a
> > > NetBeans PMC member to help with voting admin.  NetBeans 11.1 will
> > > be released if and when this vote passes.
> > >
> > > Convenience binaries, not relevant for voting purposes, are staged
> > > at the build artefacts links above.
> > >
> > > Thank you for all the hard work!
> > >
> > > Best wishes,
> > >
> > > Neil
> > > Volunteer Release Manager for Apache NetBeans 11.1
> > >
> > > 
> > > - 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: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1

2019-05-05 Thread Enrico Olivelli 
Il dom 5 mag 2019, 09:26 Geertjan Wielenga  ha scritto:

> Is it a requirement that the volunteer release manager is a PMC
> member/committer? Or does it make it easier, or does it not make
> a difference?
>

It should be at least a committer, who has access to all staging resources
and he can sign the artifacts.
No need to be a PMC


Enrico

>
> Gj
>
> On Sat, May 4, 2019 at 4:48 PM Laszlo Kishalmi 
> wrote:
>
> > The main responsibilities are: herding people, PR-s, JIRA issues towards
> > the goal of forming a healthy release.
> >
> > Some other useful reading:
> >
> >   * https://www.apache.org/dev/release-publishing.html
> >   * https://www.apache.org/dev/release-distribution.html
> >   * https://www.apache.org/legal/release-policy.html
> >   *
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
> >   * https://issues.apache.org/jira/browse/NETBEANS-2052
> >   * https://issues.apache.org/jira/browse/NETBEANS-1321
> >
> > On 5/3/19 11:22 PM, Vano Beridze wrote:
> >
> > > Hello,
> > >
> > > What are the responsibilities?
> > >
> > > Vano
> > >
> > > On Sat, May 4, 2019, 10:10 AM Laszlo Kishalmi <
> laszlo.kisha...@gmail.com
> > >
> > > wrote:
> > >
> > >> Dear all,
> > >>
> > >> I've sent this one earlier, maybe too early, though there was not a
> > >> single response to this.
> > >>
> > >> Probably we shall agree on how would we imagine the 11.1 release. For
> me
> > >> the theme would be:
> > >>
> > >>* Bugfixes
> > >>* Java EE 8 Support
> > >>* Java EE Support for Gradle
> > >>
> > >> Of course we can do something else, like just do a few module updates,
> > >> or completely opt out for 11.1...
> > >>
> > >>
> > >> I know that 11.0 is just has been pushed out the door, but if we would
> > >> like to do a NetBeans 11.1 in June we need someone who takes the
> reins.
> > >> We need a release schedule, the way of work (branching, JIRA, etc.)
> > soon.
> > >>
> > >> I've already taken this position twice, it has been quite a journey,
> > >> thank you!
> > >>
> > >> Beside the usual RM stuff which we did do far I see the following new
> > >> challenges:
> > >>
> > >>   1. This is a minor release, probably coordinating changes would be a
> > >>  bit easier.
> > >>  I guess we'd just branch off release110 to release111 and
> continue
> > >>  to cherry-picking from master.
> > >>   2. This would be the first release as Apache top level project
> > >>   3. Probably we need to experiment releasing patches, or release 11.1
> > as
> > >>  a set of parches...
> > >>   4. Codes for 12.0 will be run in parallel on master, so JIRA
> tracking
> > >>  could be a bit harder.
> > >>
> > >> As of myself, I'd concentrating on development and bug-fixing in the
> > >> next couple of cycles.
> > >>
> > >> So think about it!
> > >>
> > >> Volunteers we Need you!
> > >>
> > >> Laszlo Kishalmi
> > >>
> > >> Former Release Manager of Apache NetBeans
> > >>
> > >>
> >
>

Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

2019-04-27 Thread Enrico Olivelli 
Il giorno sab 27 apr 2019 alle ore 09:02 Laszlo Kishalmi
 ha scritto:
>
> Well, I'd avoid changing the version number of the IDE and with that
> releasing the complete code-base.

I agree. NB is more that one single module.

>
> The users would be able to build the patch release by downloading the
> 11.0 sources and overwrite the files released in the patch, it just
> another step in the process and does not make it impossible to build.
>
> AFAIK Apache releases are just a set of source code.

yes, that is was I am trying to say.

Enrico

>
> https://lists.apache.org/thread.html/ccff6dc3152cde4a278a30ef2fdba14c5a1cb54eae56dfcbc9b867ad@%3Cdev.netbeans.apache.org%3E
>
> On 4/26/19 11:11 PM, Enrico Olivelli wrote:
> > Hi,
> > IMHO If the changed files are inside the main nb repository you should
> > release a new version of the whole repository.
> > So it would be a 11.0.1 nb, with at least the zip of the sources of the
> > whole repository.
> > That fact that users would be able to upgrade the single module is just a
> > detail.
> >
> > For instance in Apache Maven, that is comprised of 100+ independent module,
> > we have a release of Maven core and every sub module (maven plugin) is
> > released independently.
> > But every project has its own repository + sources zip + convenience binary.
> >
> > I am not suggesting to split NB, I am just saying that you should release
> > the whole buildable sources bundle and not only a part.
> >
> > AFAIK in Apache we are releasing 'source code', and it is important that
> > who downloads it is able to build it.
> >
> > Just my 2 cents
> >
> > Enrico
> >
> >
> >
> > Il sab 27 apr 2019, 07:57 Laszlo Kishalmi  ha
> > scritto:
> >
> >> Dear all,
> >>
> >> As Gradle was a new out-of-the box feature, I've received some
> >> issues/feedback. I've already fixed some of them.
> >>
> >> I would like to do a release of those changes. Those fixes might be not
> >> that important, but what I'm really curious, that actually can we, and
> >> how can we roll out such a partial patch release?
> >>
> >> My plan is the following:
> >>
> >>   1. Branch the current release into something like:
> >>  release110-gradle-patch-1
> >>   2. Cherry Pick the required changes
> >>   3. Increase the patch version (3rd number on the affected modules (I
> >>  guess only gradle and gradle.java)
> >>   4. Set up a jenkins job for that branch to release.
> >>   5. The release artifacts would be
> >>   1. The new nbm modules from gradle and gradle.java
> >>   2. The source artifact would contain those module sources only.
> >>   3. I do not know what to put in there exactly:
> >>   1. The sources of the two modules keeping the directory
> >>  structure. so that would be in groovy/gradle and
> >>  groovy/gradle.java
> >>   2. LICENSE and NOTICE files
> >>   3. Is there a way to generate the DEPENDENCIES file only for
> >>  two modules?
> >>   6. Do the PGP signing with my key
> >>   7. Start a vote on the artifacts
> >>   8. If the vote would be successful:
> >>   1.   I'd upload the source artifact next to our release 11.0 one.
> >>   2. I'd upload the binary nbm-s into the 11.0 distribution UC
> >>   3. I do not know how to updates.xml, probably I keep the one
> >>  generated for the whole NB from step 5 and overwrite the current
> >>  one.
> >>   9. Again I do not know how much announcement we shall make with this
> >>  release, maybe a just our announcement list would be enough.
> >>
> >> Please think it through! Is this feasible, what else shall be done, do I
> >> have some misconceptions, etc. ?
> >>
> >> Also would like to have a peer feedback from our Release Manager Emilian.
> >>
> >> Thank you!
> >>
> >> Laszlo Kishalmi
> >>
> >>
>
> -
> 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

2019-04-27 Thread Enrico Olivelli 
Hi,
IMHO If the changed files are inside the main nb repository you should
release a new version of the whole repository.
So it would be a 11.0.1 nb, with at least the zip of the sources of the
whole repository.
That fact that users would be able to upgrade the single module is just a
detail.

For instance in Apache Maven, that is comprised of 100+ independent module,
we have a release of Maven core and every sub module (maven plugin) is
released independently.
But every project has its own repository + sources zip + convenience binary.

I am not suggesting to split NB, I am just saying that you should release
the whole buildable sources bundle and not only a part.

AFAIK in Apache we are releasing 'source code', and it is important that
who downloads it is able to build it.

Just my 2 cents

Enrico



Il sab 27 apr 2019, 07:57 Laszlo Kishalmi  ha
scritto:

> Dear all,
>
> As Gradle was a new out-of-the box feature, I've received some
> issues/feedback. I've already fixed some of them.
>
> I would like to do a release of those changes. Those fixes might be not
> that important, but what I'm really curious, that actually can we, and
> how can we roll out such a partial patch release?
>
> My plan is the following:
>
>  1. Branch the current release into something like:
> release110-gradle-patch-1
>  2. Cherry Pick the required changes
>  3. Increase the patch version (3rd number on the affected modules (I
> guess only gradle and gradle.java)
>  4. Set up a jenkins job for that branch to release.
>  5. The release artifacts would be
>  1. The new nbm modules from gradle and gradle.java
>  2. The source artifact would contain those module sources only.
>  3. I do not know what to put in there exactly:
>  1. The sources of the two modules keeping the directory
> structure. so that would be in groovy/gradle and
> groovy/gradle.java
>  2. LICENSE and NOTICE files
>  3. Is there a way to generate the DEPENDENCIES file only for
> two modules?
>  6. Do the PGP signing with my key
>  7. Start a vote on the artifacts
>  8. If the vote would be successful:
>  1.   I'd upload the source artifact next to our release 11.0 one.
>  2. I'd upload the binary nbm-s into the 11.0 distribution UC
>  3. I do not know how to updates.xml, probably I keep the one
> generated for the whole NB from step 5 and overwrite the current
> one.
>  9. Again I do not know how much announcement we shall make with this
> release, maybe a just our announcement list would be enough.
>
> Please think it through! Is this feasible, what else shall be done, do I
> have some misconceptions, etc. ?
>
> Also would like to have a peer feedback from our Release Manager Emilian.
>
> Thank you!
>
> Laszlo Kishalmi
>
>