Re: Files to License List

[Tim Boudreau]

If you're solving this, it might be nice to also integrate this into the
building of maven artifacts so POMs have a  section - lots of
people use these for product license audits.

-Tim

On Wed, Jun 19, 2019 at 4:30 PM Matthias Bläsing 
wrote:

> Hi Jaroslav,
>
> Am Mittwoch, den 19.06.2019, 15:34 +0200 schrieb Jaroslav Tulach:
> > Hello guys, especially Matthias.
> >
> > We are about to import Apache NetBeans 11.x to OracleLabs projects like
> > VisualVM and IGV. To do so we need a legal approval. Ideally we would get
> > list of files
> > for the clusters that we need with their appropriate license:
> >
> > ```
> > platform cluster
> > ├── core
> > │   ├── asm-all-5.0.1.jar - BSD
> > │   ├── core-base.jar - APL2
> > │   ├── core.jar - APL2
> > │   ├── org-netbeans-libs-asm.jar - APL2
> > │   └── org-openide-filesystems.jar - APL2
> > ├── lib
> > │   ├── boot.jar - APL2
> > │   ├── nbexec - APL2
> > │   ├── nbexec64.dll - APL2
> > ```
> >
> > possibly with a hyperlink to the actual text of the license. What
> > would be the best way to generate such document? I know we can
> > generate the
> > LICENSE and DEPENDENCIES files with
> >
> > ```
> > nbbuild$ ant build-source-config -Dcluster.config=igv
> > nbbuild$ git diff .
> > diff --git a/nbbuild/cluster.properties b/nbbuild/cluster.properties
> > index 3523ff048..272f81016 100644
> > --- a/nbbuild/cluster.properties
> > +++ b/nbbuild/cluster.properties
> > @@ -40,6 +40,14 @@ clusters.config.basic.list=\
> >  nb.cluster.ergonomics
> >  # ergonomics must be last
> >
> > +clusters.config.igv.list=\
> > +${clusters.config.platform.list},\
> > +nb.cluster.ide,\
> > +nb.cluster.extide,\
> > +nb.cluster.java,\
> > +nb.cluster.nb,\
> > +nb.cluster.webcommon
> > +
> >  clusters.config.standard.list=\
> >  ${clusters.config.java.list},\
> >  nb.cluster.apisupport,\
> > ```
> >
> > so we seem to have enough information. It is just about the "right
> > presentation".
> >
>
> I think you are already looking at the right place. The work of creating
> the LICENSE file,
> which holds the summary of the licenses, and copies the individual license
> files with the
> full text to the licenses subdir in the build tree is done in the
> `createlicensesummary`
> task. That task is implemented by
> org.netbeans.nbbuild.extlibs.CreateLicenseSummary
> class in the nbbuild project.
>
> This task scans two sources for information:
> - the external files definitions
> - the licenseinfo.xml files
>
> In both files the license names are required to be names of files in the
> nbbuild/licenses
> directory. This should make it possible to create links to the files.
>
> Gettings this per cluster might be more work, as the system tries to
> minimise the information
> and summarise it if possible. This is required, so that the NOTICE file
> follows the
> requirement to be minimal.
>
> I think that the above mentioned class should be a good start for an
> individual task
> tailored to your needs. While that task is focused on text files, creating
> HTML should be
> doable.
>
> HTH
>
> Matthias
>
>
>
>
>
>
>
> -
> 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
>
>
>
>

-- 
http://timboudreau.com

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Laszlo Kishalmi]

It won't magically happen on Gradle. The support needs to be patched for 
that. Hopefully not a big deal and might catch the release train...


On 6/19/19 4:50 AM, Geertjan Wielenga wrote:

That is great.

Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there in
some way instead?

Can you check if Ant-based Java Web projects and Gradle-based Java Web
projects (new in 11.1) don't somehow magically inherit this new feature?
Probably not, but worth checking.

Gj


On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:


Hi Geertjan,

You are correct.  The drop-down you've mentioned should now include "Java
EE 8 Web" as an option.

Additionally, if you right-click on an existing Maven Web Project using
Java EE 7 or less, the Project Properties dialog "Run" panel now contains
"Java EE 8 Web" as a Java EE Version.

On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
wrote:


Great, thanks Josh. Just to understand what this consists of -- when I go
to the New Project dialog and I choose "Java with Maven" and then "Web
Application" and click Next, and Next again, there is a "Java EE Version"
drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE

5".

Does your PR add new content to that drop-down? That's my assumption,
please just confirm/deny that.

Thanks,

Gj


On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:


Thanks Neil, for the information.  I created the PR for Java EE 8
integration, and those enhancements are specifically geared towards

Maven

projects.  The PR includes the following functionality:

- Ability to create a new Maven Web Project using Java EE 8 (utilizes a
Java EE 8 maven archetype)
- Ability to change an existing Maven Web Project to use the Java EE 8
Platform
- Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
rather than gfv3ee6)
- IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
faces-config, CDI beans.xml 2.0, web.xml 4.0

+1 for merging the Payara server and micro tools integration as well.

On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
wrote:


Hi All,

This email follows some off-list discussion with various people
including Geertjan and the relevant contributors.  The release
schedule we agreed has an open question about allowing selective
feature freeze bypass based on mailing list agreement - hence ...

I propose we allow the pending Java EE and Payara PRs to be merged to
master for the NB 11.1 release -

* Incorporating new files and code modifications for adding Java EE 8
support. https://github.com/apache/netbeans/pull/1298
* NP-20 Payara Server tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1290
* NP-20 Payara Micro tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1297

One of the reasons we discussed having quarterly and non-LTS releases
was to get things testing in the wild earlier.  These partly missed
the feature freeze because of Travis issues, seem ready to merge, and
(hopefully!) have minimal impact on existing features.

This is a lazy consensus thread that will be open for 72hrs.  You do
not need to +1 (although you're welcome to), but do raise concerns or
-1 if need be.  Assuming this goes ahead, we can merge in time to

sync

up and include in beta2 next Wednesday.

My own lazy consent as release manager is also based on -

* All tests are passing before merging (appears now to be the case)
* Merging is done before second beta (possibly a good criteria for
feature freeze bypass in general?)
* The respective contributors can commit to timely fixes in case of
issues so that this doesn't cause delay in the NB 11.1 release
schedule.

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



--

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau



--
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau




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

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

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Jose Ch]

Hi all,

I vote +1.

Regards,
Jose.

El mié., 19 jun. 2019 a las 7:52, Gaurav Gupta ()
escribió:

> Hi all,
>
> Payara Server integration is based on Apache NetBeans GlassFish modules
> which supports Payara Server v4.1.144 to v5.192 with additional features
> like payara-web.xml DD editor, JDK 11, and connection pool properties, etc.
>
> And Payara Micro integration supports Payara Micro v 4.1.2.174  to v5.192
> and
> enables to create Payara Micro maven application from IDE itself from the
> archetype  payara-micro-maven-archetype
> <
> https://mvnrepository.com/artifact/fish.payara.maven.archetypes/payara-micro-maven-archetype
> >.
> And a developer may start, stop and debug, etc the Payara Micro application
> with Hot reload support.
>
> Both tools are already used by many developers since last 2 years :
> http://plugins.netbeans.org/plugin/72263/payara-server
>
> Although If any issue arises, I will make sure to fix those on priority.
> And *+1* for including both Java EE 8 and Payara tools integration into
> NetBeans IDE 11.1.
>
> Thanks and kind regards,
> Gaurav Gupta
>
> On Wed, Jun 19, 2019 at 5:38 PM Josh Juneau  wrote:
>
> > Hi Geertjan,
> >
> > I think for this release "Java EE 8" is the correct label.  We do not yet
> > have a release of "Jakarta EE 8".  However, I will put in a PR once that
> > has occurred.
> >
> > I will test the Ant and Gradle based Java web projects to see how things
> > work with the Java EE 8 integration.
> >
> > Thanks
> >
> > On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
> > wrote:
> >
> > > That is great.
> > >
> > > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there
> > in
> > > some way instead?
> > >
> > > Can you check if Ant-based Java Web projects and Gradle-based Java Web
> > > projects (new in 11.1) don't somehow magically inherit this new
> feature?
> > > Probably not, but worth checking.
> > >
> > > Gj
> > >
> > >
> > > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau 
> wrote:
> > >
> > > > Hi Geertjan,
> > > >
> > > > You are correct.  The drop-down you've mentioned should now include
> > "Java
> > > > EE 8 Web" as an option.
> > > >
> > > > Additionally, if you right-click on an existing Maven Web Project
> using
> > > > Java EE 7 or less, the Project Properties dialog "Run" panel now
> > contains
> > > > "Java EE 8 Web" as a Java EE Version.
> > > >
> > > > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga <
> geert...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Great, thanks Josh. Just to understand what this consists of --
> when
> > I
> > > go
> > > > > to the New Project dialog and I choose "Java with Maven" and then
> > "Web
> > > > > Application" and click Next, and Next again, there is a "Java EE
> > > Version"
> > > > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and
> "Java
> > EE
> > > > 5".
> > > > >
> > > > > Does your PR add new content to that drop-down? That's my
> assumption,
> > > > > please just confirm/deny that.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gj
> > > > >
> > > > >
> > > > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> > > wrote:
> > > > >
> > > > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > > > integration, and those enhancements are specifically geared
> towards
> > > > Maven
> > > > > > projects.  The PR includes the following functionality:
> > > > > >
> > > > > > - Ability to create a new Maven Web Project using Java EE 8
> > > (utilizes a
> > > > > > Java EE 8 maven archetype)
> > > > > > - Ability to change an existing Maven Web Project to use the Java
> > EE
> > > 8
> > > > > > Platform
> > > > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by
> adding
> > > > > > separate identifiers in the sources for GlassFish 5 branch -
> > gfv5ee8,
> > > > > > rather than gfv3ee6)
> > > > > > - IDE recognizes all Java EE 8 artifact versions, for example:
> JSF
> > > 2.3
> > > > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > > > >
> > > > > > +1 for merging the Payara server and micro tools integration as
> > well.
> > > > > >
> > > > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith <
> > neilcsm...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > This email follows some off-list discussion with various people
> > > > > > > including Geertjan and the relevant contributors.  The release
> > > > > > > schedule we agreed has an open question about allowing
> selective
> > > > > > > feature freeze bypass based on mailing list agreement - hence
> ...
> > > > > > >
> > > > > > > I propose we allow the pending Java EE and Payara PRs to be
> > merged
> > > to
> > > > > > > master for the NB 11.1 release -
> > > > > > >
> > > > > > > * Incorporating new files and code modifications for adding
> Java
> > > EE 8
> > > > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > > > 

RE: Profiler images in main toolbar

[Eirik Bakke]

See the previous thread, "NetBeans GUI icons, who drew them?"

I listed the various possible approaches at 
https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
 . Downsides to using an existing icon library include: (1) quite a few 
NetBeans icons will have no suitable replacement in an existing font library, 
(2) icon font libraries yield monochromatic icons only, sacrificing the color 
of the old icons for an improvement in resolution, and (3) the style of new 
icons would appear mismatched next to old ones. There's also the license issues.

The existing NetBeans icons are really quite good--most of them were drawn by a 
single professional designer (Leos Tronicek), who once did all the work to set 
a color theme, make a visual language for various objects etc. Thus I have 
proposed keeping new icons in the same style and shapes as the old ones, only 
making them more modern by omitting unnecessary shadows, bevels, and gradients. 
That makes them easier to vectorize in any case. This approach also makes new 
icons look reasonably consistent next to old ones that haven't been vectorized 
yet.

Some examples are shown at 
https://cwiki.apache.org/confluence/download/attachments/110692909/vectorized.png

-- Eirik

From: David Schulz 
Sent: Wednesday, June 19, 2019 1:56 PM
To: Eirik Bakke ; dev@netbeans.apache.org; Christian Lenz 

Subject: RE: Profiler images in main toolbar

Makes sense, we could also check some Icon libraries like Streamline or Icon8 
to use them as a base for our icon rework. Not sure how the apache license 
works with icon libraries like that, any opinions?

Best,
Dave

From: Eirik Bakke
Sent: Mittwoch, 19. Juni 2019 17:12
To: dev@netbeans.apache.org; David 
Schulz; Christian Lenz
Subject: RE: Profiler images in main toolbar

If it's not urgent for legal/trademark reasons, it would be natural to do this 
as part of https://issues.apache.org/jira/browse/NETBEANS-2617 ("Redraw common 
icons in SVG"). Added a comment about this.

See https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html 
for a list of other icons that we should eventually try to redraw in SVG 
versions. This task does require a fair bit of graphic design skills, though.
-- Eirik
-Original Message-
From: Geertjan Wielenga 
Sent: Wednesday, June 19, 2019 7:54 AM
To: David Schulz ; Christian Lenz ; 
dev 
Subject: Profiler images in main toolbar

Hi David and Chris,

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

That would be a great item to have resolved, i.e., remove the blue NetBeans 
icon and use the new one instead, together with similar or some different 
overlay on top to indicate the difference between them in functionality.

Hope this is doable and it makes sense.

Gj

Re: Profiler images in main toolbar

[Matthias Bläsing]

Hi,

Am Mittwoch, den 19.06.2019, 19:56 +0200 schrieb David Schulz:
> Makes sense, we could also check some Icon libraries like Streamline
> or Icon8 to use them as a base for our icon rework. Not sure how the
> apache license works with icon libraries like that, any opinions?

I think this is answered in the legal FAQ:

https://apache.org/legal/resolved.html#handling-public-domain-licensed-works

We should stay inside category A licenses. Everything else will lead to
discussions and might pose problems. The less license text/copyright/required
notice is present the better. We have to mark all files, that are not plain
ALv2/not licensed to the ASF, this might prove to be painful and should be
avoided if possible.

Maybe there are good base icons in the same spirit as the Tango Desktop
Project, which distributed the icons in the public domain. We went that
way to replace the npm icon, where the origin project was not willing to
release the graphics under an open enough license.

HTH

Matthias


-
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: Profiler images in main toolbar

[David Schulz]

Makes sense, we could also check some Icon libraries like Streamline or Icon8 
to use them as a base for our icon rework. Not sure how the apache license 
works with icon libraries like that, any opinions? 

Best, 
Dave

From: Eirik Bakke
Sent: Mittwoch, 19. Juni 2019 17:12
To: dev@netbeans.apache.org; David Schulz; Christian Lenz
Subject: RE: Profiler images in main toolbar

If it's not urgent for legal/trademark reasons, it would be natural to do this 
as part of https://issues.apache.org/jira/browse/NETBEANS-2617 ("Redraw common 
icons in SVG"). Added a comment about this.

See https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html 
for a list of other icons that we should eventually try to redraw in SVG 
versions. This task does require a fair bit of graphic design skills, though.
 
-- Eirik
-Original Message-
From: Geertjan Wielenga  
Sent: Wednesday, June 19, 2019 7:54 AM
To: David Schulz ; Christian Lenz ; 
dev 
Subject: Profiler images in main toolbar

Hi David and Chris,

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

That would be a great item to have resolved, i.e., remove the blue NetBeans 
icon and use the new one instead, together with similar or some different 
overlay on top to indicate the difference between them in functionality.

Hope this is doable and it makes sense.

Gj

Re: Files to License List

[Geertjan Wielenga]

It means those Oracle apps are built on top of NetBeans and the devs from
Oracle Labs are about to move to the latest Apache NetBeans release. In
short, “import”, in a way.

Gj


On Wed, 19 Jun 2019 at 19:26, Glenn Holmer 
wrote:

> On 6/19/19 11:43 AM, Jaroslav Tulach wrote:
> > [IGV](
> >
> https://www.graalvm.org/docs/graalvm-as-a-platform/implement-language/#igv
> )
> > stands for Ideal Graph Visualizer and it is a great way to get an insight
> > into what kind of optimizations the Graal compiler does when generating
> the
> > native code for your bytecodes.
>
> Well, what I meant was, what does it mean "We are about to import Apache
> NetBeans 11.x to OracleLabs projects"?
>
> > st 19. 6. 2019 v 16:30 odesílatel Glenn Holmer
> 
> > napsal:
> >
> >> On 6/19/19 8:34 AM, Jaroslav Tulach wrote:
> >>> We are about to import Apache NetBeans 11.x to OracleLabs projects like
> >>> VisualVM and IGV.
> >>
> >> I am curious: what does this mean?
>
> --
> Glenn Holmer (Linux registered user #16682)
> "After the vintage season came the aftermath -- and Cenbe."
>
>
> -
> 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: Files to License List

[Glenn Holmer]

On 6/19/19 11:43 AM, Jaroslav Tulach wrote:
> [IGV](
> https://www.graalvm.org/docs/graalvm-as-a-platform/implement-language/#igv)
> stands for Ideal Graph Visualizer and it is a great way to get an insight
> into what kind of optimizations the Graal compiler does when generating the
> native code for your bytecodes.

Well, what I meant was, what does it mean "We are about to import Apache
NetBeans 11.x to OracleLabs projects"?

> st 19. 6. 2019 v 16:30 odesílatel Glenn Holmer 
> napsal:
> 
>> On 6/19/19 8:34 AM, Jaroslav Tulach wrote:
>>> We are about to import Apache NetBeans 11.x to OracleLabs projects like
>>> VisualVM and IGV.
>>
>> I am curious: what does this mean?

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."


-
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: Files to License List

[Jaroslav Tulach]

[IGV](
https://www.graalvm.org/docs/graalvm-as-a-platform/implement-language/#igv)
stands for Ideal Graph Visualizer and it is a great way to get an insight
into what kind of optimizations the Graal compiler does when generating the
native code for your bytecodes.
-jt


st 19. 6. 2019 v 16:30 odesílatel Glenn Holmer 
napsal:

> On 6/19/19 8:34 AM, Jaroslav Tulach wrote:
> > We are about to import Apache NetBeans 11.x to OracleLabs projects like
> > VisualVM and IGV.
>
> I am curious: what does this mean?
>
> --
> Glenn Holmer (Linux registered user #16682)
> "After the vintage season came the aftermath -- and Cenbe."
>
>
> -
> 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: Profiler images in main toolbar

[Eirik Bakke]

And of course I would love to recruit David to help with the SVGification of 
NetBeans icons :-) But I know it's a big boring task...

(SVG icons will soon be supported, for improving NetBeans' appearance on HiDPI 
displays, once the PR at https://github.com/apache/netbeans/pull/1278 is 
finalized and merged.)

-- Eirik

-Original Message-
From: Eirik Bakke  
Sent: Wednesday, June 19, 2019 11:13 AM
To: dev@netbeans.apache.org; David Schulz ; Christian Lenz 

Subject: RE: Profiler images in main toolbar

If it's not urgent for legal/trademark reasons, it would be natural to do this 
as part of https://issues.apache.org/jira/browse/NETBEANS-2617 ("Redraw common 
icons in SVG"). Added a comment about this.

See https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html 
for a list of other icons that we should eventually try to redraw in SVG 
versions. This task does require a fair bit of graphic design skills, though.
 
-- Eirik
-Original Message-
From: Geertjan Wielenga  
Sent: Wednesday, June 19, 2019 7:54 AM
To: David Schulz ; Christian Lenz ; 
dev 
Subject: Profiler images in main toolbar

Hi David and Chris,

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

That would be a great item to have resolved, i.e., remove the blue NetBeans 
icon and use the new one instead, together with similar or some different 
overlay on top to indicate the difference between them in functionality.

Hope this is doable and it makes sense.

Gj

RE: Profiler images in main toolbar

[Eirik Bakke]

If it's not urgent for legal/trademark reasons, it would be natural to do this 
as part of https://issues.apache.org/jira/browse/NETBEANS-2617 ("Redraw common 
icons in SVG"). Added a comment about this.

See https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html 
for a list of other icons that we should eventually try to redraw in SVG 
versions. This task does require a fair bit of graphic design skills, though.
 
-- Eirik
-Original Message-
From: Geertjan Wielenga  
Sent: Wednesday, June 19, 2019 7:54 AM
To: David Schulz ; Christian Lenz ; 
dev 
Subject: Profiler images in main toolbar

Hi David and Chris,

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

That would be a great item to have resolved, i.e., remove the blue NetBeans 
icon and use the new one instead, together with similar or some different 
overlay on top to indicate the difference between them in functionality.

Hope this is doable and it makes sense.

Gj

Re: Code signing

[David Nalley]

On Wed, Jun 19, 2019 at 4:02 AM  wrote:
>
> Hi David,
>
> We use Code Signing service for signing NetBeans installers.
>
> Is there an action required to continue using this?
>

I hadn't seen any production signings, so didn't realize that you were
already using this.

At this stage, the thing that would be nice to have is an estimate of
the number of annual signing events.
With another project, this look like:

$project has two supported release lines that are released. $project
needs to sign both the uninstaller and installer. $project averages a
release per month. So that's 2 release lines that generate 2 signing
events 12 times per year - so ~48 signing events a year.

I don't know what the numbers are for Netbeans. I suspect you'll have
better sense of release cadence, number of signing events, etc. We'd
like to have those numbers for planning in the next 2-3 weeks if
possible.

Thanks,

--David

-
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: Installers for 11.1 release

[David Nalley]

On Mon, Jun 17, 2019 at 9:37 AM  wrote:
>
> Production signing of Windows installer is one that I haven't tried yet
> and it is not free.
>
> Other is limited testing of installers.
>

Please don't feel constrained by the 'not free' portion of production
signing. As long as you have validated with test signing, please feel
free to make sure production signing works. No one is going to
complain about a few extra signing events.

--David

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

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

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

[Neil C Smith]

On Wed, 19 Jun 2019 at 14:17, Sven Reimers  wrote:
>
> For the activation,
>
> - open plugins dialog
> - select installed tab.
> - check all checkboxes
> - press activate button.

Thanks, that triggers it for me too - so looks like it's installing
from the notification bubble?

Out of interest, does the Java with Maven / Java Frontend Application
work for you after those steps?  This wizard just hangs for me after
activation as above.

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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Gaurav Gupta]

Hi all,

Payara Server integration is based on Apache NetBeans GlassFish modules
which supports Payara Server v4.1.144 to v5.192 with additional features
like payara-web.xml DD editor, JDK 11, and connection pool properties, etc.

And Payara Micro integration supports Payara Micro v 4.1.2.174  to v5.192 and
enables to create Payara Micro maven application from IDE itself from the
archetype  payara-micro-maven-archetype
.
And a developer may start, stop and debug, etc the Payara Micro application
with Hot reload support.

Both tools are already used by many developers since last 2 years :
http://plugins.netbeans.org/plugin/72263/payara-server

Although If any issue arises, I will make sure to fix those on priority.
And *+1* for including both Java EE 8 and Payara tools integration into
NetBeans IDE 11.1.

Thanks and kind regards,
Gaurav Gupta

On Wed, Jun 19, 2019 at 5:38 PM Josh Juneau  wrote:

> Hi Geertjan,
>
> I think for this release "Java EE 8" is the correct label.  We do not yet
> have a release of "Jakarta EE 8".  However, I will put in a PR once that
> has occurred.
>
> I will test the Ant and Gradle based Java web projects to see how things
> work with the Java EE 8 integration.
>
> Thanks
>
> On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
> wrote:
>
> > That is great.
> >
> > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there
> in
> > some way instead?
> >
> > Can you check if Ant-based Java Web projects and Gradle-based Java Web
> > projects (new in 11.1) don't somehow magically inherit this new feature?
> > Probably not, but worth checking.
> >
> > Gj
> >
> >
> > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:
> >
> > > Hi Geertjan,
> > >
> > > You are correct.  The drop-down you've mentioned should now include
> "Java
> > > EE 8 Web" as an option.
> > >
> > > Additionally, if you right-click on an existing Maven Web Project using
> > > Java EE 7 or less, the Project Properties dialog "Run" panel now
> contains
> > > "Java EE 8 Web" as a Java EE Version.
> > >
> > > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga  >
> > > wrote:
> > >
> > > > Great, thanks Josh. Just to understand what this consists of -- when
> I
> > go
> > > > to the New Project dialog and I choose "Java with Maven" and then
> "Web
> > > > Application" and click Next, and Next again, there is a "Java EE
> > Version"
> > > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java
> EE
> > > 5".
> > > >
> > > > Does your PR add new content to that drop-down? That's my assumption,
> > > > please just confirm/deny that.
> > > >
> > > > Thanks,
> > > >
> > > > Gj
> > > >
> > > >
> > > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> > wrote:
> > > >
> > > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > > integration, and those enhancements are specifically geared towards
> > > Maven
> > > > > projects.  The PR includes the following functionality:
> > > > >
> > > > > - Ability to create a new Maven Web Project using Java EE 8
> > (utilizes a
> > > > > Java EE 8 maven archetype)
> > > > > - Ability to change an existing Maven Web Project to use the Java
> EE
> > 8
> > > > > Platform
> > > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > > > > separate identifiers in the sources for GlassFish 5 branch -
> gfv5ee8,
> > > > > rather than gfv3ee6)
> > > > > - IDE recognizes all Java EE 8 artifact versions, for example: JSF
> > 2.3
> > > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > > >
> > > > > +1 for merging the Payara server and micro tools integration as
> well.
> > > > >
> > > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith <
> neilcsm...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > This email follows some off-list discussion with various people
> > > > > > including Geertjan and the relevant contributors.  The release
> > > > > > schedule we agreed has an open question about allowing selective
> > > > > > feature freeze bypass based on mailing list agreement - hence ...
> > > > > >
> > > > > > I propose we allow the pending Java EE and Payara PRs to be
> merged
> > to
> > > > > > master for the NB 11.1 release -
> > > > > >
> > > > > > * Incorporating new files and code modifications for adding Java
> > EE 8
> > > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > > https://github.com/apache/netbeans/pull/1290
> > > > > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > > > > https://github.com/apache/netbeans/pull/1297
> > > > > >
> > > > > > One of the reasons we discussed having quarterly and non-LTS
> > releases
> > > > > > was to get things testing in the wild earlier.  These partly
> missed
> > > > > > the feature freeze because of Travis issues, seem ready to merge,
> > 

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Hi Geertjan,

I think for this release "Java EE 8" is the correct label.  We do not yet
have a release of "Jakarta EE 8".  However, I will put in a PR once that
has occurred.

I will test the Ant and Gradle based Java web projects to see how things
work with the Java EE 8 integration.

Thanks

On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
wrote:

> That is great.
>
> Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there in
> some way instead?
>
> Can you check if Ant-based Java Web projects and Gradle-based Java Web
> projects (new in 11.1) don't somehow magically inherit this new feature?
> Probably not, but worth checking.
>
> Gj
>
>
> On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:
>
> > Hi Geertjan,
> >
> > You are correct.  The drop-down you've mentioned should now include "Java
> > EE 8 Web" as an option.
> >
> > Additionally, if you right-click on an existing Maven Web Project using
> > Java EE 7 or less, the Project Properties dialog "Run" panel now contains
> > "Java EE 8 Web" as a Java EE Version.
> >
> > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
> > wrote:
> >
> > > Great, thanks Josh. Just to understand what this consists of -- when I
> go
> > > to the New Project dialog and I choose "Java with Maven" and then "Web
> > > Application" and click Next, and Next again, there is a "Java EE
> Version"
> > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE
> > 5".
> > >
> > > Does your PR add new content to that drop-down? That's my assumption,
> > > please just confirm/deny that.
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> > >
> > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> wrote:
> > >
> > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > integration, and those enhancements are specifically geared towards
> > Maven
> > > > projects.  The PR includes the following functionality:
> > > >
> > > > - Ability to create a new Maven Web Project using Java EE 8
> (utilizes a
> > > > Java EE 8 maven archetype)
> > > > - Ability to change an existing Maven Web Project to use the Java EE
> 8
> > > > Platform
> > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > > > separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> > > > rather than gfv3ee6)
> > > > - IDE recognizes all Java EE 8 artifact versions, for example: JSF
> 2.3
> > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > >
> > > > +1 for merging the Payara server and micro tools integration as well.
> > > >
> > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > This email follows some off-list discussion with various people
> > > > > including Geertjan and the relevant contributors.  The release
> > > > > schedule we agreed has an open question about allowing selective
> > > > > feature freeze bypass based on mailing list agreement - hence ...
> > > > >
> > > > > I propose we allow the pending Java EE and Payara PRs to be merged
> to
> > > > > master for the NB 11.1 release -
> > > > >
> > > > > * Incorporating new files and code modifications for adding Java
> EE 8
> > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > https://github.com/apache/netbeans/pull/1290
> > > > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > > > https://github.com/apache/netbeans/pull/1297
> > > > >
> > > > > One of the reasons we discussed having quarterly and non-LTS
> releases
> > > > > was to get things testing in the wild earlier.  These partly missed
> > > > > the feature freeze because of Travis issues, seem ready to merge,
> and
> > > > > (hopefully!) have minimal impact on existing features.
> > > > >
> > > > > This is a lazy consensus thread that will be open for 72hrs.  You
> do
> > > > > not need to +1 (although you're welcome to), but do raise concerns
> or
> > > > > -1 if need be.  Assuming this goes ahead, we can merge in time to
> > sync
> > > > > up and include in beta2 next Wednesday.
> > > > >
> > > > > My own lazy consent as release manager is also based on -
> > > > >
> > > > > * All tests are passing before merging (appears now to be the case)
> > > > > * Merging is done before second beta (possibly a good criteria for
> > > > > feature freeze bypass in general?)
> > > > > * The respective contributors can commit to timely fixes in case of
> > > > > issues so that this doesn't cause delay in the NB 11.1 release
> > > > > schedule.
> > > > >
> > > > > 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:
> > > > > 

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

[Geertjan Wielenga]

Some of what you describe, specifically the downloading of JavaFX, may be
related to this: https://github.com/apache/netbeans/pull/917

Gj

On Wed, Jun 19, 2019 at 1:43 PM Neil C Smith  wrote:

> Hi,
> On Tue, 18 Jun 2019 at 15:29, Sven Reimers  wrote:
> > Hi just ran NetBeans 11.1 beta 1 on OpenJDK Runtime Environment 12+33
> from
> > AdoptOpenJDK on Mac.
>
> OK, so I'm using AdoptOpenJDK 11 (OpenJ9) on Linux and can definitely
> replicate the error message.
>
> > I activated all plugins, got some follow  up install messages, once Java
> > plugins was active nb-javac installation was triggered...
>
> How exactly are you activating?
>
> > After all was over I saw this:
> >
> > java.lang.IllegalStateException: Host module
> > StandardModule:org.netbeans.libs.javacapi jarFile:
> >
> /Users/sven/tools/netbeans-11.1beta1/java/modules/org-netbeans-libs-javacapi.jar
> > was enabled before, will not accept fragment
>
> With a clean userdir and no import, if I go to create a new Maven
> Application the dialog offers buttons for download and activate, and
> just activate.
>
> The dialog has the same text repeated four times.
>
> If I click download and activate it wants to install JavaFX for Linux.
> Why?!  This is also unsigned.
>
> If I just activate (or cancel download install because I'm worried
> about an unsigned plugin!) I get the notification bubble to install
> nb-javac.  This triggers the above error.  It seems to actually work
> OK though.
>
> Anyone else replicate that?
>
> The exact same steps cause the exact same problems for me with NB 11.0
> though.  And it does appear to work OK afterwards.
>
> 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
>
>
>
>

Profiler images in main toolbar

[Geertjan Wielenga]

Hi David and Chris,

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

That would be a great item to have resolved, i.e., remove the blue NetBeans
icon and use the new one instead, together with similar or some different
overlay on top to indicate the difference between them in functionality.

Hope this is doable and it makes sense.

Gj

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Hi Geertjan,

You are correct.  The drop-down you've mentioned should now include "Java
EE 8 Web" as an option.

Additionally, if you right-click on an existing Maven Web Project using
Java EE 7 or less, the Project Properties dialog "Run" panel now contains
"Java EE 8 Web" as a Java EE Version.

On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
wrote:

> Great, thanks Josh. Just to understand what this consists of -- when I go
> to the New Project dialog and I choose "Java with Maven" and then "Web
> Application" and click Next, and Next again, there is a "Java EE Version"
> drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE 5".
>
> Does your PR add new content to that drop-down? That's my assumption,
> please just confirm/deny that.
>
> Thanks,
>
> Gj
>
>
> On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:
>
> > Thanks Neil, for the information.  I created the PR for Java EE 8
> > integration, and those enhancements are specifically geared towards Maven
> > projects.  The PR includes the following functionality:
> >
> > - Ability to create a new Maven Web Project using Java EE 8 (utilizes a
> > Java EE 8 maven archetype)
> > - Ability to change an existing Maven Web Project to use the Java EE 8
> > Platform
> > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> > rather than gfv3ee6)
> > - IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
> > faces-config, CDI beans.xml 2.0, web.xml 4.0
> >
> > +1 for merging the Payara server and micro tools integration as well.
> >
> > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> > wrote:
> >
> > > Hi All,
> > >
> > > This email follows some off-list discussion with various people
> > > including Geertjan and the relevant contributors.  The release
> > > schedule we agreed has an open question about allowing selective
> > > feature freeze bypass based on mailing list agreement - hence ...
> > >
> > > I propose we allow the pending Java EE and Payara PRs to be merged to
> > > master for the NB 11.1 release -
> > >
> > > * Incorporating new files and code modifications for adding Java EE 8
> > > support. https://github.com/apache/netbeans/pull/1298
> > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > https://github.com/apache/netbeans/pull/1290
> > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > https://github.com/apache/netbeans/pull/1297
> > >
> > > One of the reasons we discussed having quarterly and non-LTS releases
> > > was to get things testing in the wild earlier.  These partly missed
> > > the feature freeze because of Travis issues, seem ready to merge, and
> > > (hopefully!) have minimal impact on existing features.
> > >
> > > This is a lazy consensus thread that will be open for 72hrs.  You do
> > > not need to +1 (although you're welcome to), but do raise concerns or
> > > -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> > > up and include in beta2 next Wednesday.
> > >
> > > My own lazy consent as release manager is also based on -
> > >
> > > * All tests are passing before merging (appears now to be the case)
> > > * Merging is done before second beta (possibly a good criteria for
> > > feature freeze bypass in general?)
> > > * The respective contributors can commit to timely fixes in case of
> > > issues so that this doesn't cause delay in the NB 11.1 release
> > > schedule.
> > >
> > > 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
> > >
> > >
> > >
> > > --
> > Josh Juneau
> > juneau...@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/us/search?query=Juneau
> > 
> >
>
-- 
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

Great, thanks Josh. Just to understand what this consists of -- when I go
to the New Project dialog and I choose "Java with Maven" and then "Web
Application" and click Next, and Next again, there is a "Java EE Version"
drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE 5".

Does your PR add new content to that drop-down? That's my assumption,
please just confirm/deny that.

Thanks,

Gj


On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:

> Thanks Neil, for the information.  I created the PR for Java EE 8
> integration, and those enhancements are specifically geared towards Maven
> projects.  The PR includes the following functionality:
>
> - Ability to create a new Maven Web Project using Java EE 8 (utilizes a
> Java EE 8 maven archetype)
> - Ability to change an existing Maven Web Project to use the Java EE 8
> Platform
> - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> rather than gfv3ee6)
> - IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
> faces-config, CDI beans.xml 2.0, web.xml 4.0
>
> +1 for merging the Payara server and micro tools integration as well.
>
> On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> wrote:
>
> > Hi All,
> >
> > This email follows some off-list discussion with various people
> > including Geertjan and the relevant contributors.  The release
> > schedule we agreed has an open question about allowing selective
> > feature freeze bypass based on mailing list agreement - hence ...
> >
> > I propose we allow the pending Java EE and Payara PRs to be merged to
> > master for the NB 11.1 release -
> >
> > * Incorporating new files and code modifications for adding Java EE 8
> > support. https://github.com/apache/netbeans/pull/1298
> > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1290
> > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1297
> >
> > One of the reasons we discussed having quarterly and non-LTS releases
> > was to get things testing in the wild earlier.  These partly missed
> > the feature freeze because of Travis issues, seem ready to merge, and
> > (hopefully!) have minimal impact on existing features.
> >
> > This is a lazy consensus thread that will be open for 72hrs.  You do
> > not need to +1 (although you're welcome to), but do raise concerns or
> > -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> > up and include in beta2 next Wednesday.
> >
> > My own lazy consent as release manager is also based on -
> >
> > * All tests are passing before merging (appears now to be the case)
> > * Merging is done before second beta (possibly a good criteria for
> > feature freeze bypass in general?)
> > * The respective contributors can commit to timely fixes in case of
> > issues so that this doesn't cause delay in the NB 11.1 release
> > schedule.
> >
> > 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
> >
> >
> >
> > --
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> 
>

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Thanks Neil, for the information.  I created the PR for Java EE 8
integration, and those enhancements are specifically geared towards Maven
projects.  The PR includes the following functionality:

- Ability to create a new Maven Web Project using Java EE 8 (utilizes a
Java EE 8 maven archetype)
- Ability to change an existing Maven Web Project to use the Java EE 8
Platform
- Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
rather than gfv3ee6)
- IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
faces-config, CDI beans.xml 2.0, web.xml 4.0

+1 for merging the Payara server and micro tools integration as well.

On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith  wrote:

> Hi All,
>
> This email follows some off-list discussion with various people
> including Geertjan and the relevant contributors.  The release
> schedule we agreed has an open question about allowing selective
> feature freeze bypass based on mailing list agreement - hence ...
>
> I propose we allow the pending Java EE and Payara PRs to be merged to
> master for the NB 11.1 release -
>
> * Incorporating new files and code modifications for adding Java EE 8
> support. https://github.com/apache/netbeans/pull/1298
> * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> https://github.com/apache/netbeans/pull/1290
> * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> https://github.com/apache/netbeans/pull/1297
>
> One of the reasons we discussed having quarterly and non-LTS releases
> was to get things testing in the wild earlier.  These partly missed
> the feature freeze because of Travis issues, seem ready to merge, and
> (hopefully!) have minimal impact on existing features.
>
> This is a lazy consensus thread that will be open for 72hrs.  You do
> not need to +1 (although you're welcome to), but do raise concerns or
> -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> up and include in beta2 next Wednesday.
>
> My own lazy consent as release manager is also based on -
>
> * All tests are passing before merging (appears now to be the case)
> * Merging is done before second beta (possibly a good criteria for
> feature freeze bypass in general?)
> * The respective contributors can commit to timely fixes in case of
> issues so that this doesn't cause delay in the NB 11.1 release
> schedule.
>
> 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
>
>
>
> --
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

[Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

Hi All,

This email follows some off-list discussion with various people
including Geertjan and the relevant contributors.  The release
schedule we agreed has an open question about allowing selective
feature freeze bypass based on mailing list agreement - hence ...

I propose we allow the pending Java EE and Payara PRs to be merged to
master for the NB 11.1 release -

* Incorporating new files and code modifications for adding Java EE 8
support. https://github.com/apache/netbeans/pull/1298
* NP-20 Payara Server tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1290
* NP-20 Payara Micro tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1297

One of the reasons we discussed having quarterly and non-LTS releases
was to get things testing in the wild earlier.  These partly missed
the feature freeze because of Travis issues, seem ready to merge, and
(hopefully!) have minimal impact on existing features.

This is a lazy consensus thread that will be open for 72hrs.  You do
not need to +1 (although you're welcome to), but do raise concerns or
-1 if need be.  Assuming this goes ahead, we can merge in time to sync
up and include in beta2 next Wednesday.

My own lazy consent as release manager is also based on -

* All tests are passing before merging (appears now to be the case)
* Merging is done before second beta (possibly a good criteria for
feature freeze bypass in general?)
* The respective contributors can commit to timely fixes in case of
issues so that this doesn't cause delay in the NB 11.1 release
schedule.

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

Merging of PRs for 11.1 and 11.2

[Neil C Smith]

Hi All,

We're obviously still getting our heads around how the new release
process will work in practice, and one thing we still need to firm up
is how to handle tagging and merging PRs to master outside of the
merge windows.  I'd like to propose the following for NB 11.1, to be
reviewed after the release.

PRs to be included in next release (eg. NB 11.1)

* PRs should be made/reviewed in accordance with the Bug Priority Guidelines
* (almost) all PRs should have a related JIRA ticket with 11.1 as the
fix version - add the ticket reference in the PR title (and ideally a
full link to the issue in the description)
* Tag the PR with the release label (eg. NB 11.1)
* Add the release manager as a reviewer (in this case me) to help
tracking / scheduling

PRs ready to be merged in the following cycle (eg. NB 11.2)

* If the PR is ready for merging, add the following release label (eg. NB 11.2)
* A few days after the release (NB 11.1) necessary commits to master
such as spec increments will be made.
* Following that, the merge window reopening will be announced.
* Priority will be given to merging all pending PRs labelled as above.

Any thoughts, issues, comments?

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: Code signing

[reema . taneja]

Hi David,

   We use Code Signing service for signing NetBeans installers.

Is there an action required to continue using this?

Thanks,
Reema

On 19/06/19 9:29 AM, David Nalley wrote:

Hi folks,

Apologies for the interruption of your regularly scheduled project discussion.

Infra is in the procurement cycle for this years code signing service renewal.
I don't know if Netbeans cares about signing binary releases, but if
the PMC is interested - we have that option available. Feel free to
create a Jira ticket or start a conversation on us...@infra.apache.org

Thanks,

--David

-
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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists=DwIBaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=-5jPBe_OQdQRNVSCzec305l0FdBW9DIWpw6unap02KQ=ctK0WiVYB-AEHhAnM1PFosxP-Drwh-JNy1BHQJUsClw=






-
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