Re: [DISCUSS] Frontend distro of NetBeans

[Geertjan Wielenga]

I don't see that as a requirement. In the same way as the experimental
installer we have right now, we could create an installer for this which,
if no JRE is present, a message would appear that it needs to be obtained
from some specific place -- what that place is is the question.

Gj

On Sun, Apr 21, 2019 at 6:53 AM Laszlo Kishalmi 
wrote:

> Well,
>
> I do not know how dead JRE is, however this distro would have only
> meaningful if we can actually pack the JRE along the code and yes
> probably installable with a proper installer.
>
> I could probably make a Snap for such a distro for Linux without too
> much hustle, though I do not think I legally ship/distribute it as
> Apache NetBeans. Or maybe as it would be an unofficial convenience
> binary which would not be hosted on Apache infra...
>
> I do not really know.
>
> On 4/20/19 1:12 PM, Matthias Bläsing wrote:
> > Hi,
> >
> > at this point in time I don't see any benefit in producing a bunch of
> > different netbeans releases.
> >
> > Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:
> >> I think one of the coolest things we could do together is spin out a
> >> separate distro specifically for PHP/JS type developers.
> > what is the use case of that special distribution?
> >
> >> We had that before, it only requires JRE, not JDK, and would mean the
> >> potential for a small snappy editor-focused tool (that as a side effect
> >> could be interesting for users of a few comparable editors we can all
> think
> >> of).
> > The JRE is dead (for any Java version >= 9), at least that is what
> > every java vendor is telling. You can either get a JDK from Azul or Red
> > Hat and/or Amazon or stay in the past with JRE derived from JDK 8.
> >
> > If we could build a fully runnable NetBeans for people not interested
> > in Java, ok, but neigther the ASF, nor Oracle do anything visible to
> > resolve the big problem in the room:
> >
> > GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
> > this time (there is an open issue, that asks for moving GPLv2+CPE to
> > Category B, but the ASF side raised concers and noone stood up to calm
> > them.
> >
> > I don't think, that random comments will help here:
> >
> > https://issues.apache.org/jira/browse/LEGAL-336
> >
> > But comments from lawyers, preferable from oracle, could help to
> > resolve this. Mayber it would be possible to reword the CPE to make it
> > compatible with the ASFs requirements for dependencies.
> >
> > That would help _many_ apache projects, as many apache projects are
> > Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
> > there is _no_ other open source Java distribution out there, that is
> > even remotely as up-to-date and open as OpenJDK).
> >
> > Just my 2 cents.
> >
> > Greetings
> >
> > 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
> >
> >
> >
>
> -
> 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] Frontend distro of NetBeans

[Laszlo Kishalmi]

Well,

I do not know how dead JRE is, however this distro would have only 
meaningful if we can actually pack the JRE along the code and yes 
probably installable with a proper installer.


I could probably make a Snap for such a distro for Linux without too 
much hustle, though I do not think I legally ship/distribute it as 
Apache NetBeans. Or maybe as it would be an unofficial convenience 
binary which would not be hosted on Apache infra...


I do not really know.

On 4/20/19 1:12 PM, Matthias Bläsing wrote:

Hi,

at this point in time I don't see any benefit in producing a bunch of
different netbeans releases.

Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:

I think one of the coolest things we could do together is spin out a
separate distro specifically for PHP/JS type developers.

what is the use case of that special distribution?


We had that before, it only requires JRE, not JDK, and would mean the
potential for a small snappy editor-focused tool (that as a side effect
could be interesting for users of a few comparable editors we can all think
of).

The JRE is dead (for any Java version >= 9), at least that is what
every java vendor is telling. You can either get a JDK from Azul or Red
Hat and/or Amazon or stay in the past with JRE derived from JDK 8.

If we could build a fully runnable NetBeans for people not interested
in Java, ok, but neigther the ASF, nor Oracle do anything visible to
resolve the big problem in the room:

GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
this time (there is an open issue, that asks for moving GPLv2+CPE to
Category B, but the ASF side raised concers and noone stood up to calm
them.

I don't think, that random comments will help here:

https://issues.apache.org/jira/browse/LEGAL-336

But comments from lawyers, preferable from oracle, could help to
resolve this. Mayber it would be possible to reword the CPE to make it
compatible with the ASFs requirements for dependencies.

That would help _many_ apache projects, as many apache projects are
Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
there is _no_ other open source Java distribution out there, that is
even remotely as up-to-date and open as OpenJDK).

Just my 2 cents.

Greetings

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





-
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: DTDs and XSDs

[Jan Lahoda]

On Sat, Apr 20, 2019 at 8:40 PM Antonio  wrote:

> Hi there,
>
> I see, so you mean that http://netbeans.apache.org is redirecting to
> https://netbeans.apache.org (i.e. http to httpS protocol), right?
>
>
Mostly, yes, but just with netbeans.org currently. See, for example, the
systemID of the DTD used here:
https://github.com/apache/incubator-netbeans/blob/0f2e98d513deaedccef831ee9cfc08d09f3650b6/ide/languages.manifest/src/org/netbeans/modules/languages/manifest/DefaultPreferences.xml
it is:
http://www.netbeans.org/dtds/EditorPreferences-1_0.dtd

And doing wget http://www.netbeans.org/dtds/EditorPreferences-1_0.dtd
currently shows (for me) a redirect to:
http://netbeans.org/dtds/EditorPreferences-1_0.dtd
and then to:
https://netbeans.org/dtds/EditorPreferences-1_0.dtd

And IIRC java.net.URL won't follow the redirect from http to https, which
would explain why the online resolution fails.


> AFAIK all ASF servers will do that redirection, from plain http to
> https, so it's probably a good idea to have the DTDs in-place.
>
> Another option would be to add _all_ DTDs to a well-known directory in
> our build structure, and use the existing catalog.xml file there to
> resolve them for all modules.
>

Not sure I understand here. The DTDs are (hopefully all) in the repository.
For example:
https://github.com/apache/incubator-netbeans/blob/0f2e98d513deaedccef831ee9cfc08d09f3650b6/ide/editor.settings.lib/src/org/netbeans/modules/editor/settings/storage/preferences/EditorPreferences-1_0.dtd

They are even (hopefully) registered in the respective XML layers. The
reason why the system IDs are used instead of using the local copies is
that many tests run without module system, so they don't see the
registration. (Which, frankly, should be solveable as well, if one would
try hard enough.)

Jan


>
> BTW, DTDs uploaded to the website have already an APLv2 license.
>
> Cheers,
> Antonio
>
>
> El 20/04/2019 a las 19:07, Jan Lahoda escribió:
> > On Thu, Apr 18, 2019 at 9:26 AM Antonio  wrote:
> >
> >> https://github.com/apache/incubator-netbeans-website/pull/352
> >
> >
> > Thanks Antonio!
> >
> > Unfortunately, it seems this didn't help with the (java.completion)
> tests.
> > (Part of the issue might be that, AFAIK, java.net.URL does not redirect
> > across protocols.) I've sumitted a PR that is changing the
> java.completion
> > tests to use the local copies of the DTDs instead of trying to download
> > them:
> > https://github.com/apache/incubator-netbeans/pull/1206
> >
> > Comments are welcome, but I'd like to merge that soon.
> >
> > Jan
> >
> >
> >>
> >> El 18/04/2019 a las 6:47, Jaroslav Tulach escribió:
> >>> FYI: reported as https://issues.apache.org/jira/browse/NETBEANS-2429
> >>> -jt
> >>>
> >>>
> >>> st 17. 4. 2019 v 17:13 odesílatel Wade Chandler <
> wadechand...@apache.org
> >>>
> >>> napsal:
> >>>
>  This is here too for extra reference; a couple Jira issues were setup
> >> for
>  it too; in case anything in there helps:
> 
> 
> >>
> https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning#NewNetBeansWebSitePlanning-RelocateDTDsandNS(XMLSchemas)
>  <
> 
> >>
> https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning#NewNetBeansWebSitePlanning-RelocateDTDsandNS(XMLSchemas)
> >
> 
>  It would be helpful to understand what the process for publishing
> those
>  was before. Was there some build which did this automatically to the
> >> site
>  previously, or were these manual steps with infrequent changes? Either
> >> way
>  seems doable, but wondering if automated if the script or what ever is
>  still around which we could change up to use git pushes.
> 
>  Wade
> 
> 
> 
> > On Apr 16, 2019, at 10:35 PM, Wade Chandler  >
>  wrote:
> >
> > dtds here too
> >
> >
> 
> >>
> https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/dtds
>  <
> 
> >>
> https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/dtds
> >
> >
> > Wade
> >
> > On Tue, Apr 16, 2019, 22:28 Wade Chandler   > wrote:
> > These are probably in the original site copies I made; many files
> >> there;
> >
> >
> 
> >>
> https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/ns
>  <
> 
> >>
> https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/ns
> >
> >
> > It seems we should be able to publish then plus new updates.
> >
> > Wade
> >
> >
> > On Tue, Apr 16, 2019, 16:35 Antonio   anto...@vieiro.net>> wrote:
> > Hi,
> >
> > Yep, too bad we can't have that backup server.
> >
> > Meanwhile we're collecting those missing links here:
> >
> 
> >>
> https://cwiki.apache.org/confluence/display/NETBEANS/netbeans.org+migration
>  <
> 
> >>
> 

Re: [DISCUSS] Frontend distro of NetBeans

[Matthias Bläsing]

Hi,

at this point in time I don't see any benefit in producing a bunch of
different netbeans releases.

Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:
> 
> I think one of the coolest things we could do together is spin out a
> separate distro specifically for PHP/JS type developers.

what is the use case of that special distribution? 

> We had that before, it only requires JRE, not JDK, and would mean the
> potential for a small snappy editor-focused tool (that as a side effect
> could be interesting for users of a few comparable editors we can all think
> of).

The JRE is dead (for any Java version >= 9), at least that is what
every java vendor is telling. You can either get a JDK from Azul or Red
Hat and/or Amazon or stay in the past with JRE derived from JDK 8.

If we could build a fully runnable NetBeans for people not interested
in Java, ok, but neigther the ASF, nor Oracle do anything visible to
resolve the big problem in the room:

GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
this time (there is an open issue, that asks for moving GPLv2+CPE to
Category B, but the ASF side raised concers and noone stood up to calm
them.

I don't think, that random comments will help here:

https://issues.apache.org/jira/browse/LEGAL-336

But comments from lawyers, preferable from oracle, could help to
resolve this. Mayber it would be possible to reword the CPE to make it
compatible with the ASFs requirements for dependencies.

That would help _many_ apache projects, as many apache projects are
Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
there is _no_ other open source Java distribution out there, that is
even remotely as up-to-date and open as OpenJDK).

Just my 2 cents.

Greetings

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: DTDs and XSDs

[Antonio]

Hi there,

I see, so you mean that http://netbeans.apache.org is redirecting to 
https://netbeans.apache.org (i.e. http to httpS protocol), right?


AFAIK all ASF servers will do that redirection, from plain http to 
https, so it's probably a good idea to have the DTDs in-place.


Another option would be to add _all_ DTDs to a well-known directory in 
our build structure, and use the existing catalog.xml file there to 
resolve them for all modules.


BTW, DTDs uploaded to the website have already an APLv2 license.

Cheers,
Antonio


El 20/04/2019 a las 19:07, Jan Lahoda escribió:

On Thu, Apr 18, 2019 at 9:26 AM Antonio  wrote:


https://github.com/apache/incubator-netbeans-website/pull/352



Thanks Antonio!

Unfortunately, it seems this didn't help with the (java.completion) tests.
(Part of the issue might be that, AFAIK, java.net.URL does not redirect
across protocols.) I've sumitted a PR that is changing the java.completion
tests to use the local copies of the DTDs instead of trying to download
them:
https://github.com/apache/incubator-netbeans/pull/1206

Comments are welcome, but I'd like to merge that soon.

Jan




El 18/04/2019 a las 6:47, Jaroslav Tulach escribió:

FYI: reported as https://issues.apache.org/jira/browse/NETBEANS-2429
-jt


st 17. 4. 2019 v 17:13 odesílatel Wade Chandler 
This is here too for extra reference; a couple Jira issues were setup

for

it too; in case anything in there helps:



https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning#NewNetBeansWebSitePlanning-RelocateDTDsandNS(XMLSchemas)

<


https://cwiki.apache.org/confluence/display/NETBEANS/New+NetBeans+Web+Site+Planning#NewNetBeansWebSitePlanning-RelocateDTDsandNS(XMLSchemas)




It would be helpful to understand what the process for publishing those
was before. Was there some build which did this automatically to the

site

previously, or were these manual steps with infrequent changes? Either

way

seems doable, but wondering if automated if the script or what ever is
still around which we could change up to use git pushes.

Wade




On Apr 16, 2019, at 10:35 PM, Wade Chandler 

wrote:


dtds here too





https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/dtds

<


https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/dtds



Wade

On Tue, Apr 16, 2019, 22:28 Wade Chandler 
> wrote:

These are probably in the original site copies I made; many files

there;






https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/ns

<


https://github.com/wadechandler/netbeans-static-site/tree/master/src/content/ns



It seems we should be able to publish then plus new updates.

Wade


On Tue, Apr 16, 2019, 16:35 Antonio 
anto...@vieiro.net>> wrote:

Hi,

Yep, too bad we can't have that backup server.

Meanwhile we're collecting those missing links here:




https://cwiki.apache.org/confluence/display/NETBEANS/netbeans.org+migration

<


https://cwiki.apache.org/confluence/display/NETBEANS/netbeans.org+migration



Jan, can you please add your findings to that page?

Thanks,
Antonio

El 16/04/2019 a las 21:37, Geertjan Wielenga escribió:

Yes, none of this is news at all. We tried rerouting, didn’t work as
expected, side effects, so it’s being rolled back now, may take a day

or so

and it will be OK again.

Then, now that we know of several problematic areas such as this one,

we

can investigate each case and see how to solve it.

Gj


On Tue, 16 Apr 2019 at 15:22, Jan Lahoda 
lah...@gmail.com>> wrote:



Hi,

(As noted by a friend of mine.) Many modules in NetBeans use DTDs or

XSDs

to validate XMLs. The appropriate DTDs and XSDs are available not

only

inside the IDE, but also published on the web. Presumably with the

recent

change to use netbeans.apache.org 

instead of www.netbeans.org , (some of)

these became unavailable. This can cause  problems when doing online
validation of XMLs. That may happen e.g. in tests.

As far as I can tell, these were under the "dtd" and "ns" directories

under

(www.)netbeans.org .

One thing to note is that "netbeans.org "

still appears to use the old

server. So:
https://netbeans.org/dtds/EditorFontsColors-1_0.dtd <

https://netbeans.org/dtds/EditorFontsColors-1_0.dtd>


still appears to work OK, while:
https://www.netbeans.org/dtds/EditorFontsColors-1_0.dtd <

https://www.netbeans.org/dtds/EditorFontsColors-1_0.dtd>


does not.

I think we need to publish the DTDs and XSDs again on our pages, but

it

would be awesome if we could use the old server until that is done.

Would a

redirect from:
https://www.netbeans.org/dtds/ 
to:
https://netbeans.org/dtds/ 

work for now? (And the same for "https://www.netbeans.org/ns/ <

https://www.netbeans.org/ns/>".) After we

(re-)publish the DTDs and 

Re: [DISCUSS] import Bugzilla to Jira or Plan to Drop Bugzilla

[Craig Russell]

I have no dog in this hunt, but I think a copy of the Oracle bugzilla 
repository hosted at Apache might be very useful.

However, it might be misleading if it is read-only. I'd think that it might be 
useful for a small number of admins to be able to update issues: annotate the 
issue with a link to the current JIRA; close the issue with a reference to a 
Netbeans release; annotate the issue as being rejected, user error, etc.

Craig

> On Apr 20, 2019, at 6:18 AM, Geertjan Wielenga  wrote:
> 
> Sounds like we need an INFRA ticket as a starting point for that.
> 
> Gj
> 
> On Sat, 20 Apr 2019 at 08:55, László Kishalmi 
> wrote:
> 
>> +1 for import bugzilla into apache bugzilla and keep it read only. Apache
>> supports bugzilla, so that should be feasible.
>> 
>> On Sat, Apr 20, 2019, 02:16 Neil C Smith  wrote:
>> 
>>> On Sat, 20 Apr 2019, 02:37 Geertjan Wielenga, 
>> wrote:
>>> 
 My understanding is Oracle NetBeans bugzilla is being kept in readonly
 state. That’s how e.g., Reema, is using and needing it.
 
>>> 
>>> IIRC we were told a while back that hosting a read-only (or even
>>> read-write) bugzilla on Apache infrastructure was a possibility?!
>>> 
>>> Best wishes,
>>> 
>>> Neil
>>> 
 
>>> 
>> 

Craig L Russell
c...@apache.org


-
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] Frontend distro of NetBeans

[Kenneth Fogel]

This may have been brought up before but is there any talk about a python 
enabled NetBeans. My program at Dawson is planning to drop PHP because the job 
market demand here has dropped while requests for Python have increased. I know 
there is a plug-in but could it be more? I agree with continuing targeted 
NetBeans and having a PHP version. Then there is Go, Rust and for April Fools 
we will need a GW-Basic version. Extra points if you know what GW stands for.

Ken Fogel
Co-Chairperson and Co-Program Coordinater
Computer Science Technology
Dawson College
3040 Sherbrooke St. W
Westmount, Quebec
H3Z 1A4, Canada
Tel: 514-931-8731 x 4799
Twitter: @omniprof

From: Josh Juneau 
Sent: Saturday, April 20, 2019 10:11 AM
To: dev@netbeans.apache.org
Cc: wadechand...@apache.org
Subject: Re: [DISCUSS] Frontend distro of NetBeans

I agree that a separate "lite" distribution would be useful for those who do 
not wish to deal with Java. I also agree with Wade that such a release should 
provide the option to automatically download and install a JRE distribution if 
one wishes to do so.

Around naming, it seems to make sense to continue to build off the Apache 
NetBeans brand, but perhaps create new "editions". I like something like 
"Apache NetBeans: PHP Edition", or something of the like.


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

> On Apr 20, 2019, at 7:03 AM, Eric Barboni  wrote:
>
> Hi
> I would keep Apache NetBeans in the name, Apache PhpBeans looks like a TLP of 
> Apache not something from Apache NetBeans.
> And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans.
>
> But making several branding sounds a good idea.
>
> Jenkins release build should be make more complex but this will not change 
> the vote and release except more file to sign and to review. It will be in 
> the convenience libraries part of the voting thread.
> For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans" at the 
> same time.
>
> The above link all the branding to official Apache NetBeans release to limit 
> effort.
>
> Best Regards
> Eric
>
> -Message d'origine-
> De : Wade Chandler 
> Envoyé : samedi 20 avril 2019 13:08
> À : dev@netbeans.apache.org
> Objet : Re: [DISCUSS] Frontend distro of NetBeans
>
>> On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:
>>
>> Hi all,
>>
>> I think one of the coolest things we could do together is spin out a
>> separate distro specifically for PHP/JS type developers.
>>
>> We had that before, it only requires JRE, not JDK, and would mean the
>> potential for a small snappy editor-focused tool (that as a side
>> effect could be interesting for users of a few comparable editors we
>> can all think of).
>>
>> And that would bring in new contributions too since we’d be targeting
>> a different type of developer.
>>
>> What would need for this to be done and where? Probably something
>> would need to be tweaked on Jenkins?
>>
>
> This seems like a release build step.
>
> One thing though, would we want to do any special branding like a different 
> splash screen, icon, and name? Something like "WebBeans" (sounds like
> webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
> and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or 
> "CyBeans" for C, C++, and Python or given all the Machine Learning bits at 
> Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new wizards 
> for Spark and TensorFlow related items. Later with some of the new mobile and 
> native techs we could even have "MoBeans" (please).
>
> It would be handy if the installer offered to download and install a JDK for 
> the user as well from some where like AdoptOpenJDK. Those devs often don't 
> know about Java tools. And if we setup a JDK, and if they ever install any 
> Java, Groovy, or Gradle tools, then they'd be ready to work with them.
>
> I like the base idea plus all the play I think we can do like mentioned 
> above. I think for me personally I would rather focus on hardening, adding 
> features, and making more robust first, and then circle back, but laying some 
> foundation for it at the same time I think would be great; 
> names/branding/config steps etc/requirements from which to build features or 
> harden.
>
> Thanks
>
> Wade
>
>
> -
> 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] Frontend distro of NetBeans

[Josh Juneau]

I agree that a separate "lite" distribution would be useful for those who do 
not wish to deal with Java.  I also agree with Wade that such a release should 
provide the option to automatically download and install a JRE distribution if 
one wishes to do so.

Around naming, it seems to make sense to continue to build off the Apache 
NetBeans brand, but perhaps create new "editions".  I like something like 
"Apache NetBeans: PHP Edition", or something of the like.


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

> On Apr 20, 2019, at 7:03 AM, Eric Barboni  wrote:
> 
> Hi
> I would keep Apache NetBeans in the name,  Apache PhpBeans looks like a TLP 
> of Apache not something from Apache NetBeans.
> And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans. 
> 
> But making several branding sounds a good idea. 
> 
> Jenkins release build should be make more complex but this will not change 
> the vote and release except more file to sign and to review. It will be in 
> the convenience libraries part of the voting thread. 
> For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans"  at 
> the same time. 
> 
> The above link all the branding to official Apache NetBeans release to limit 
> effort.
> 
> Best Regards
> Eric
> 
> -Message d'origine-
> De : Wade Chandler  
> Envoyé : samedi 20 avril 2019 13:08
> À : dev@netbeans.apache.org
> Objet : Re: [DISCUSS] Frontend distro of NetBeans
> 
>> On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:
>> 
>> Hi all,
>> 
>> I think one of the coolest things we could do together is spin out a 
>> separate distro specifically for PHP/JS type developers.
>> 
>> We had that before, it only requires JRE, not JDK, and would mean the 
>> potential for a small snappy editor-focused tool (that as a side 
>> effect could be interesting for users of a few comparable editors we 
>> can all think of).
>> 
>> And that would bring in new contributions too since we’d be targeting 
>> a different type of developer.
>> 
>> What would need for this to be done and where? Probably something 
>> would need to be tweaked on Jenkins?
>> 
> 
> This seems like a release build step.
> 
> One thing though, would we want to do any special branding like a different 
> splash screen, icon, and name? Something like "WebBeans" (sounds like
> webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
> and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or 
> "CyBeans" for C, C++, and Python or given all the Machine Learning bits at 
> Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new wizards 
> for Spark and TensorFlow related items. Later with some of the new mobile and 
> native techs we could even have "MoBeans" (please).
> 
> It would be handy if the installer offered to download and install a JDK for 
> the user as well from some where like AdoptOpenJDK. Those devs often don't 
> know about Java tools. And if we setup a JDK, and if they ever install any 
> Java, Groovy, or Gradle tools, then they'd be ready to work with them.
> 
> I like the base idea plus all the play I think we can do like mentioned 
> above. I think for me personally I would rather focus on hardening, adding 
> features, and making more robust first, and then circle back, but laying some 
> foundation for it at the same time I think would be great; 
> names/branding/config steps etc/requirements from which to build features or 
> harden.
> 
> Thanks
> 
> Wade
> 
> 
> -
> 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] import Bugzilla to Jira or Plan to Drop Bugzilla

[Geertjan Wielenga]

Sounds like we need an INFRA ticket as a starting point for that.

Gj

On Sat, 20 Apr 2019 at 08:55, László Kishalmi 
wrote:

> +1 for import bugzilla into apache bugzilla and keep it read only. Apache
> supports bugzilla, so that should be feasible.
>
> On Sat, Apr 20, 2019, 02:16 Neil C Smith  wrote:
>
> > On Sat, 20 Apr 2019, 02:37 Geertjan Wielenga, 
> wrote:
> >
> > > My understanding is Oracle NetBeans bugzilla is being kept in readonly
> > > state. That’s how e.g., Reema, is using and needing it.
> > >
> >
> > IIRC we were told a while back that hosting a read-only (or even
> > read-write) bugzilla on Apache infrastructure was a possibility?!
> >
> > Best wishes,
> >
> > Neil
> >
> > >
> >
>

Re: Re: bugzilla

[Geertjan Wielenga]

Those that are relevant and reproducible, sure.

Gj

On Sat, 20 Apr 2019 at 09:04, Eric Bresie  wrote:

> Silly question and maybe bigger task but should the Bugzilla items be
> migrated to Jira tickets to avoid multiple bug systems?
>
> Eric Bresie
> ebre...@gmail.com
> > On April 19, 2019 at 7:58:26 PM CDT, reema.tan...@oracle.com <
> reema.tan...@oracle.com> wrote:
> > Thanks, Able to access old bugzilla links now, eg
> >
> > https://netbeans.org/bugzilla/show_bug.cgi?id=236107
> >
> > Regards,
> >
> > Reema
> >
> >
> > On 19/04/19 10:24 PM, Antonio wrote:
> > > Hi all,
> > >
> > > John is asking if bugzilla.netbeans.org is to be redirected to
> > > netbeans.org/buzilla.
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D17245=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=u8ssj6xGkQ38f6081vnQ_p5IvAmCiaqHfOei2DoayI4=
> > >
> > >
> > > Don't know what to say. Would you please clarify @INFRA-17245?
> > >
> > > Thanks,
> > > Antonio
> > >
> > >
> > > El 19/04/2019 a las 17:14, Geertjan Wielenga escribió:
> > > > But the below seems to be fine, so which specific links are not
> working?
> > > >
> > > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__netbeans.org_bugzilla_show-5Fbug.cgi-3Fid-3D245227=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=Fc2fDsOSZwj1czeST-ucaBLX9WvbsCydKUo7kLpIs5I=
> > > >
> > > >
> > > > Gj
> > > >
> > > > On Fri, Apr 19, 2019 at 11:13 AM Geertjan Wielenga <
> geert...@apache.org>
> > > > wrote:
> > > >
> > > > >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D18243=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=JZDN47uUjk6EKTBFiuh1RJkwjuFNz74gt_S672SKBgc=
> > > > >
> > > > >
> > > > > Thanks for the above Antonio.
> > > > >
> > > > > Gj
> > > > >
> > > > > On Fri, Apr 19, 2019 at 12:46 AM  wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Bugzilla links are getting redirected, is this also planned to be
> > > > > > migrated?
> > > > > >
> > > > > > Thanks,
> > > > > > Reema
> > > > > >
> > > > > >
> > > > > >
> -
> > > > > > 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=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=xVZCqEdngzdhhOvVPKcZ5sE4ntaOfAOkjI_0Cue-iu4=
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > >
> > > -
> > > 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=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=xVZCqEdngzdhhOvVPKcZ5sE4ntaOfAOkjI_0Cue-iu4=
> > >
> > >
> > >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>

Re: Re: bugzilla

[Eric Bresie]

Silly question and maybe bigger task but should the Bugzilla items be migrated 
to Jira tickets to avoid multiple bug systems?

Eric Bresie
ebre...@gmail.com
> On April 19, 2019 at 7:58:26 PM CDT, reema.tan...@oracle.com 
>  wrote:
> Thanks, Able to access old bugzilla links now, eg
>
> https://netbeans.org/bugzilla/show_bug.cgi?id=236107
>
> Regards,
>
> Reema
>
>
> On 19/04/19 10:24 PM, Antonio wrote:
> > Hi all,
> >
> > John is asking if bugzilla.netbeans.org is to be redirected to
> > netbeans.org/buzilla.
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D17245=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=u8ssj6xGkQ38f6081vnQ_p5IvAmCiaqHfOei2DoayI4=
> >
> >
> > Don't know what to say. Would you please clarify @INFRA-17245?
> >
> > Thanks,
> > Antonio
> >
> >
> > El 19/04/2019 a las 17:14, Geertjan Wielenga escribió:
> > > But the below seems to be fine, so which specific links are not working?
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__netbeans.org_bugzilla_show-5Fbug.cgi-3Fid-3D245227=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=Fc2fDsOSZwj1czeST-ucaBLX9WvbsCydKUo7kLpIs5I=
> > >
> > >
> > > Gj
> > >
> > > On Fri, Apr 19, 2019 at 11:13 AM Geertjan Wielenga 
> > > wrote:
> > >
> > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D18243=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=JZDN47uUjk6EKTBFiuh1RJkwjuFNz74gt_S672SKBgc=
> > > >
> > > >
> > > > Thanks for the above Antonio.
> > > >
> > > > Gj
> > > >
> > > > On Fri, Apr 19, 2019 at 12:46 AM  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Bugzilla links are getting redirected, is this also planned to be
> > > > > migrated?
> > > > >
> > > > > Thanks,
> > > > > Reema
> > > > >
> > > > >
> > > > > -
> > > > > 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=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=xVZCqEdngzdhhOvVPKcZ5sE4ntaOfAOkjI_0Cue-iu4=
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> >
> > -
> > 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=DwIDaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0=wrrws_5LcJr_q0GGPtc2LPx_RpiNb2ide8nNmDpx_7g=xVZCqEdngzdhhOvVPKcZ5sE4ntaOfAOkjI_0Cue-iu4=
> >
> >
> >
> >
>
>
> -
> 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] import Bugzilla to Jira or Plan to Drop Bugzilla

[László Kishalmi]

+1 for import bugzilla into apache bugzilla and keep it read only. Apache
supports bugzilla, so that should be feasible.

On Sat, Apr 20, 2019, 02:16 Neil C Smith  wrote:

> On Sat, 20 Apr 2019, 02:37 Geertjan Wielenga,  wrote:
>
> > My understanding is Oracle NetBeans bugzilla is being kept in readonly
> > state. That’s how e.g., Reema, is using and needing it.
> >
>
> IIRC we were told a while back that hosting a read-only (or even
> read-write) bugzilla on Apache infrastructure was a possibility?!
>
> Best wishes,
>
> Neil
>
> >
>

[VOTE] Apache NetBeans (incubating) maven artefacts for version 9, 10 and 11

[Eric Barboni]

Dear member of the Apache NetBeans community. 

The Maven artefacts for Apache NetBeans (incubating) 9,10 and 11 are ready
to be published based on the respective state of source at their time of
release.

 

Apache NetBeans (incubating) 9.0

https://github.com/apache/incubator-netbeans/commit/97904961e496383d6150aef9
b78fa8dff8f3e1ce

staged at
https://repository.apache.org/content/repositories/orgapachenetbeans-1021 

with buildnumber incubator-netbeans-release-334-on-20180708 

 

Apache NetBeans (incubating) 10

https://github.com/apache/incubator-netbeans/commit/910bd74bf46d079e49925f70
2432c74d54ec705c

staged at
https://repository.apache.org/content/repositories/orgapachenetbeans-1022 

with buildnumber incubator-netbeans-release-380-on-20181217

 

Apache NetBeans (incubating) 11.0

https://github.com/apache/incubator-netbeans/commit/275dea5557510c107cf9d193
fe61555aacd544b1

staged at
https://repository.apache.org/content/repositories/orgapachenetbeans-1023 

with buildnumber incubator-netbeans-release-404-on-20190319

 

Artefacts are signed using my key (Eric Barboni) and verified by the
repository.apache.org closing phase.

Artefacts are composed jars,nbm,sources,javadocs,pom.

 

https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS

 

 

This vote is going to be open at least 72  hours, vote with +1, 0, and -1 as
usual

 

Best Regards

Eric

RE: [DISCUSS] Frontend distro of NetBeans

[Eric Barboni]

Hi
 I would keep Apache NetBeans in the name,  Apache PhpBeans looks like a TLP of 
Apache not something from Apache NetBeans.
 And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans. 

 But making several branding sounds a good idea. 

 Jenkins release build should be make more complex but this will not change the 
vote and release except more file to sign and to review. It will be in the 
convenience libraries part of the voting thread. 
 For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans"  at the 
same time. 

 The above link all the branding to official Apache NetBeans release to limit 
effort.
 
Best Regards
Eric

-Message d'origine-
De : Wade Chandler  
Envoyé : samedi 20 avril 2019 13:08
À : dev@netbeans.apache.org
Objet : Re: [DISCUSS] Frontend distro of NetBeans

On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:

> Hi all,
>
> I think one of the coolest things we could do together is spin out a 
> separate distro specifically for PHP/JS type developers.
>
> We had that before, it only requires JRE, not JDK, and would mean the 
> potential for a small snappy editor-focused tool (that as a side 
> effect could be interesting for users of a few comparable editors we 
> can all think of).
>
> And that would bring in new contributions too since we’d be targeting 
> a different type of developer.
>
> What would need for this to be done and where? Probably something 
> would need to be tweaked on Jenkins?
>

This seems like a release build step.

One thing though, would we want to do any special branding like a different 
splash screen, icon, and name? Something like "WebBeans" (sounds like
webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or "CyBeans" 
for C, C++, and Python or given all the Machine Learning bits at Apache 
"MLBeans" with C, C++, Python, Java, and Groovy with some new wizards for Spark 
and TensorFlow related items. Later with some of the new mobile and native 
techs we could even have "MoBeans" (please).

It would be handy if the installer offered to download and install a JDK for 
the user as well from some where like AdoptOpenJDK. Those devs often don't know 
about Java tools. And if we setup a JDK, and if they ever install any Java, 
Groovy, or Gradle tools, then they'd be ready to work with them.

I like the base idea plus all the play I think we can do like mentioned above. 
I think for me personally I would rather focus on hardening, adding features, 
and making more robust first, and then circle back, but laying some foundation 
for it at the same time I think would be great; names/branding/config steps 
etc/requirements from which to build features or harden.

Thanks

Wade


-
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] Frontend distro of NetBeans

[Wade Chandler]

On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:

> Hi all,
>
> I think one of the coolest things we could do together is spin out a
> separate distro specifically for PHP/JS type developers.
>
> We had that before, it only requires JRE, not JDK, and would mean the
> potential for a small snappy editor-focused tool (that as a side effect
> could be interesting for users of a few comparable editors we can all think
> of).
>
> And that would bring in new contributions too since we’d be targeting a
> different type of developer.
>
> What would need for this to be done and where? Probably something would
> need to be tweaked on Jenkins?
>

This seems like a release build step.

One thing though, would we want to do any special branding like a different
splash screen, icon, and name? Something like "WebBeans" (sounds like
webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or
"CyBeans" for C, C++, and Python or given all the Machine Learning bits at
Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new
wizards for Spark and TensorFlow related items. Later with some of the new
mobile and native techs we could even have "MoBeans" (please).

It would be handy if the installer offered to download and install a JDK
for the user as well from some where like AdoptOpenJDK. Those devs often
don't know about Java tools. And if we setup a JDK, and if they ever
install any Java, Groovy, or Gradle tools, then they'd be ready to work
with them.

I like the base idea plus all the play I think we can do like mentioned
above. I think for me personally I would rather focus on hardening, adding
features, and making more robust first, and then circle back, but laying
some foundation for it at the same time I think would be great;
names/branding/config steps etc/requirements from which to build features
or harden.

Thanks

Wade

Re: [DISCUSS] import Bugzilla to Jira or Plan to Drop Bugzilla

[Neil C Smith]

On Sat, 20 Apr 2019, 02:37 Geertjan Wielenga,  wrote:

> My understanding is Oracle NetBeans bugzilla is being kept in readonly
> state. That’s how e.g., Reema, is using and needing it.
>

IIRC we were told a while back that hosting a read-only (or even
read-write) bugzilla on Apache infrastructure was a possibility?!

Best wishes,

Neil

>

Re: [DISCUSS] import Bugzilla to Jira or Plan to Drop Bugzilla

[Matthias Bläsing]

Hi,

Am Freitag, den 19.04.2019, 21:37 -0400 schrieb Geertjan Wielenga:
> My understanding is Oracle NetBeans bugzilla is being kept in readonly
> state. That’s how e.g., Reema, is using and needing it.
> 
> Gj
> 
> On Fri, 19 Apr 2019 at 21:22, Wade Chandler  wrote:
> 
>> [Import Bugzilla Issues]

I think keeping bugzilla in read-only mode around is a good idea as a
reference point where details from the past can be retrieved. I would
not import the issues, as they suffer the same problem as many of the
newer reports in the jira:

- unresponsive users
- automated reports without context
- issues for obsolete states of netbeans

Greetings

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