[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-02-01 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758254#comment-16758254
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 2/1/19 12:21 PM:
---

Hey Jakub, thx for reporting. We moved the discussion over to the mailinglist: 
https://tinyurl.com/y8rbqsys


was (Author: chrizzly):
Hey Jakub, thx for reporting. We moved the discussion over to the mailinglist: 
https://lists.apache.org/thread.html/32d7950b2920abfeb57f5d29eead4adf9b80482a3018b60d75ccb2e0@

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-02-01 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758254#comment-16758254
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 2/1/19 12:22 PM:
---

Hey [~jherkel], thx for reporting. We moved the discussion over to the 
mailinglist: https://tinyurl.com/y8rbqsys


was (Author: chrizzly):
Hey Jakub, thx for reporting. We moved the discussion over to the mailinglist: 
https://tinyurl.com/y8rbqsys

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-01-08 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736975#comment-16736975
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 1/8/19 10:30 AM:
---

Sry, but it wasn't my attention for that. I only wanted to make my point clear, 
that there is a case, for a me a problem and I had a solution in my mind (Like 
the project type switcher). So it is not that I say: yeah well, make your own 
thoughts about it. And if it is not that important, I will leave it like this.

To add one thing, it would be good, to not restart the whole IDE, it would be 
good to reopen the project, if possible, that makes much more sense to me. And 
will not decrease my work. It will only affect this project, not everything 
else. See, another idea ;). Don't want to blame anyone or smth else. You know 
that.

Thx for your patience and your work, I really appreciates it.


was (Author: chrizzly):
Sry, but it wasn't my attention for that. I only wanted to make my point clear, 
that there is a case, for a me a problem and I had a solution in my mind (Like 
the project type switcher). So it is not that I say: yeah well, make your own 
thoughts about it. And if it is not that important, I will leave it like this.

To add one thing, it would be good, to not restart the whole IDE, it would be 
good to reopen the project, if possible, that makes much more sense to me. And 
will not decrease my work. It will only affect this project, not everything 
else. See, another idea ;). Don't want to blame anyone or smth else. You know 
that.

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-01-08 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736959#comment-16736959
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 1/8/19 10:15 AM:
---

When NetBeans is still open, nothing happens. When I remove the POM, the maven 
project is still there but unloadable, beacuse pom.xml is missing. So I have to 
restart NetBeans, now it is a html5 project. But I can make myself a tea or 
come back after getting water, until I can start to work because indexing, 
background scanning, opening projects, initializing project, etc.

Now I added the pom.xml again, nothing happens. I restarted NetBeans again and 
it is a maven project again.

Yes I tested it now, after you requested it, but now I can say, this is not 
even a workaround. Do you really want to work in this way?


was (Author: chrizzly):
When NetBeans is still open, nothing happens. When I remove the POM, the maven 
project is still there but unloadable, beacuse pom.xml is missing. So I have to 
restart NetBeans, now it is a html5 project. But I can make myself a tea or 
come back after getting water, until I can start to work because indexing, 
background scanning, opening projects, initializing project, etc.

Now I added the pom.xml again, nothing happens. I restarted NetBeans again and 
it is a maven project again.

Yes I tested it now, after you requested it, but now I can say, this is not 
even a workaround.

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-01-08 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736946#comment-16736946
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 1/8/19 10:00 AM:
---

With restarting NetBeans or without?


was (Author: chrizzly):
With restart NetBeans or without?

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-01-08 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736942#comment-16736942
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 1/8/19 9:55 AM:
--

TLDR;
{code}
Exactly. I would like to see both because when I choose them maybe 
accidentally, how can I switch it back? Or switching because of using this 
actions and then this actions. I mean it is similar to that what I mentioned 
before. It is like a feature that I activate/deactivate. I activate NodeJS 
support for a HTML5 Project and I can deactivate it. I can activate WordPress 
or Doctrine or Symfony for a PHP project, and I can deactivate it. So here it 
is a bit different but could be similar. If NetBeans see oh there is HTML5 and 
Maven, what would you like to activate? Hm this time, I would like to use 
HTML5. But inside of the properties, I can activate Maven too and it turns into 
a maven project, for example. Or switch it to a while different project.

In IntelliJ there is the feature, where you can add frameworks and tools, to 
your project/module. So there is no specific projecttype at all, but you can 
add this, and that and that, etc. to use it in your module.
{code}

So long story short, yes it would be perfect to switch between projects or 
activate/deactivate features like maven, ant, gradle, whatever, doesn't matter 
what projecttype it is. Or more to talk about my case, when NetBeans see 
different project types. So both options are very needed in my case here.


was (Author: chrizzly):
TLDR;
Exactly. I would like to see both because when I choose them maybe 
accidentally, how can I switch it back? Or switching because of using this 
actions and then this actions. I mean it is similar to that what I mentioned 
before. It is like a feature that I activate/deactivate. I activate NodeJS 
support for a HTML5 Project and I can deactivate it. I can activate WordPress 
or Doctrine or Symfony for a PHP project, and I can deactivate it. So here it 
is a bit different but could be similar. If NetBeans see oh there is HTML5 and 
Maven, what would you like to activate? Hm this time, I would like to use 
HTML5. But inside of the properties, I can activate Maven too and it turns into 
a maven project, for example. Or switch it to a while different project.

In IntelliJ there is the feature, where you can add frameworks and tools, to 
your project/module. So there is no specific projecttype at all, but you can 
add this, and that and that, etc. to use it in your module.


So long story short, yes it would be perfect to switch between projects or 
activate/deactivate features like maven, ant, gradle, whatever, doesn't matter 
what projecttype it is. Or more to talk about my case, when NetBeans see 
different project types. So both options are very needed in my case here.

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the 

[jira] [Comment Edited] (NETBEANS-1802) Problem with loading a project which has 2 different project files

2019-01-07 Thread Christian Lenz (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735961#comment-16735961
 ] 

Christian Lenz edited comment on NETBEANS-1802 at 1/7/19 3:29 PM:
--

For the files, this is not a problem, but I can't use for example the sass 
process for this. It is not only that I can't see some files, I know how to 
treat it instead but some features are not working, like the sass compilation, 
running JS tests, adding node.js support etc.


was (Author: chrizzly):
For the files, this is not a problem, but I can't use for example the sass 
process for this. It nos not only that I can't see some files, I know how to 
treat it instead but some features are not working, like the sass compilation, 
running JS tests, adding node.js support etc.

> Problem with loading a project which has 2 different project files
> --
>
> Key: NETBEANS-1802
> URL: https://issues.apache.org/jira/browse/NETBEANS-1802
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure, projects - Generic 
> Projects UI
>Affects Versions: 8.2, 9.0, 10.0
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: dasaa.7z
>
>
> Most of the comments are inside of the external ticket, but I will summerize 
> it:
> When I have a project, with 2 different project related files like pom.xml 
> and package.json. One is always winning. In my case, pom is winning.
> I had a html5 project, where NetBeans found package.json and everything was 
> fine, because it is a HTML5 project. After some infrastucture changes in my 
> company, using nexus to put artifacts on the repo, we had to add pom.xml 
> files for nexus. Now, after opening NetBeans, the project turns into a maven 
> based project, which is not correct. Only this one file and some 
> infrastructure files, which are not project sourcecode related are needed for 
> nexus.
> Now, because NetBeans things this is a maven project, I can't set the sass 
> compilation anymore or the folder structure is wrong.
> This always happen, if the project loader finds a project specific file and 
> will change the project for that. This happens for pom.xml for example and 
> for this plugin here: https://github.com/tropyx/NetBeansPuppet
> It turns a project into a puppet project and this is even more worse. Here is 
> another discussion about the problem: 
> https://github.com/tropyx/NetBeansPuppet/issues/27
> I know, that NetBeans acts like it was designed but this isn't nice and 
> created problems. I only have one solution which could be ok. Give the user a 
> notification that a project type were found, like for node support and let 
> the user choose whether I want to change the project type or not.
> So for me, I have a HTML5 Project with a package.json file and it should be 
> as it is. If NetBeans found the pom file it should give me the hint whether I 
> want to change it or not.
> If you open NetBeans with a project with two files, I want to choose as what 
> I want to treat the project and it should be saved. Like a project switcher.
> I added a sample project to it to make it clear.
> We can set it back to Major, but I think this is a big problem for multiple 
> project files.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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