[jira] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105164#comment-17105164 ] Christian Lenz commented on NETBEANS-1802: -- [~ebresie] yes that would be cool. I mean it is similar to the nodejs functionality and in IntelliJ you also can add support from other languages/frameworks to your projects. Doesn't matter how it is called but yeah adding facets to support multiple features (maybe only what makes sense), would be good :) > 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 >Assignee: Laszlo Kishalmi >Priority: Critical > Labels: pull-request-available > Attachments: dasaa.7z > > Time Spent: 1h 50m > Remaining Estimate: 0h > > 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 (v8.3.4#803005) - 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787884#comment-16787884 ] Christian Lenz commented on NETBEANS-1802: -- I will create a spec how it could work, hope for help of the others, that have a similar problem. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787888#comment-16787888 ] Christian Lenz commented on NETBEANS-1802: -- It gets more and more, that I have this problem. Now we have a lib in our company, which is in general a JS project/lib with a gulpfile. But in it, there is a pom.xml file, beacuse some other teams needs this file to add this lib as a dependency into there maven repo to use the stuff inside (It's a sass lib, we created). So we can't change here until we talk to each team whether we can change smth here or not. So this will be not an option only due to NetBeans can't handle it, FYI. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787906#comment-16787906 ] Geertjan Wielenga commented on NETBEANS-1802: - Write the spec, please. Thanks. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735951#comment-16735951 ] Christian Lenz commented on NETBEANS-1802: -- Atm, there is nothing I can do to make a workaround of this, except from changing the whole project structure and think about a new one. This is possible, when I'm the only one, but we are a company of some teams with different developers so a lot of other people use this approach, with the nexus thing for example. That means also time that I have to explain which is inaccaptable to say that I can't use my IDE of choice, due to this problem. Ok then take another IDE or whatever to fix this. So I don't know whether others have this problem but for me it is essential. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735952#comment-16735952 ] Geertjan Wielenga commented on NETBEANS-1802: - Well, at least you can open the folder into the Favorites window. It's not an ideal solution, but you should at least be able to edit the files. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735961#comment-16735961 ] Christian Lenz commented on NETBEANS-1802: -- 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
[jira] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735963#comment-16735963 ] Christian Lenz commented on NETBEANS-1802: -- Adding or updating npm or bower packages or mapping build tasks fo grunt or gulp tasks. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736899#comment-16736899 ] Christian Lenz commented on NETBEANS-1802: -- So my wish is, that it could be similar to a HTML5 project with NodeJS. When I open a HTML5 project, and NetBeans figure out, hey there is nodejs support, I can enable it and, that is also important, I can deactivate it later, because it is an option in the project properties. NetBeans doesn't force me to do that and it will not do it automatically. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736905#comment-16736905
]
Geertjan Wielenga commented on NETBEANS-1802:
-
Something else to think about is this part of your comments above:
{quote}I had this 3 times over the past 3 years.{quote}
You're so far the main person requesting this enhancement -- and you've had the
problem three times in three years. Is there a way to gauge to what extent this
is a problem throughout the community and in other words how useful this will
be to spend time on for someone?
> 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736911#comment-16736911 ] Christian Lenz commented on NETBEANS-1802: -- Yes and nowadays it is back again, as you can see it. I got a new project from an other team where they merged package.json and a pom.xml into one folder where one sub folder is the client project but NetBeans doesn't no it, because the package json is not in this folder. There is no freedom in that point, NetBeans forces the user the first project that it figures out. And, it still happens, if you have a maven project, with a puppet file and u use the puppet plugin. NetBeans now forces the puppet project type, where there are no maven actions anymore. I can't be the only one who has this problem and if this is so, this is a big reason for me, to change the IDE or editor, because I can't work with NetBeans in this case anymore. And why I added it back again to Jira is, that I still have the use case now. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736935#comment-16736935 ] Geertjan Wielenga commented on NETBEANS-1802: - I'm not sure what the solution would be, i.e., (1) when opening a folder and multiple project types could be applied, you want to be able to choose which project type to apply and (2) when a project type has already been selected, you want to be able to select a different project type? Do you want 1 only or also 2? > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736942#comment-16736942 ] Christian Lenz commented on NETBEANS-1802: -- 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 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736944#comment-16736944 ] Geertjan Wielenga commented on NETBEANS-1802: - Could you remove the POM from your project and then you'd have just a package.json file and then open the project and it will be an HTML5 project and then put the POM back into the project, or the other way around? Could you not complain, but just try this and say whether this works for you. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736946#comment-16736946 ] Christian Lenz commented on NETBEANS-1802: -- 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736945#comment-16736945 ] Christian Lenz commented on NETBEANS-1802: -- Here is another example, I think it was the nodejs plugin from tim: https://netbeans.org/bugzilla/show_bug.cgi?id=246939 It was long ago, where NetBeans couldn't handle NodeJS until now. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736949#comment-16736949 ] Geertjan Wielenga commented on NETBEANS-1802: - Whatever works. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736959#comment-16736959 ] Christian Lenz commented on NETBEANS-1802: -- 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736971#comment-16736971 ] Geertjan Wielenga commented on NETBEANS-1802: - Yes, it will at least need a restart. I'm looking at creating a project switcher right now, i.e., on the project context menu, you'll see a menu item 'Switch Project'. Not sure if it will work, but I'm investigating it. I am also concerned a lot about "squeaky wheel gets the grease", i.e., he who shouts loudest gets the most attention. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736975#comment-16736975 ] Christian Lenz commented on NETBEANS-1802: -- 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758234#comment-16758234 ] Jakub Herkel commented on NETBEANS-1802: I have a very similar problem. We have a web project that has a pom.xml. This pom contains only maven-frontend-plugin and maven-bundle-plugin that build a web project and pack it as an OSGI bundle. But because there is a pom.xml we cannot set HTML5 project, so now we have to use another IDE for web development. When I simple copy a whole directory somewhere else and delete pom.xml, everything works. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758254#comment-16758254 ] Christian Lenz commented on NETBEANS-1802: -- 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[
https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895705#comment-16895705
]
Jake Ochs commented on NETBEANS-1802:
-
I'll add my use-case to the list...
{noformat}
I am using gradle as the build system. There is a master gradle project with 3
subprojects. Each subproject results in a distributable rpm, which is how the
system is deployed. One of the rpm’s, in fact, also has a java component, but
it is mostly the copying of files to the proper directory structure, writing
the proper configs to disk and and configuring the rpm.
In NB8, I see thr project as I want it to be, a PHP project (with some gradle
and even some ant files. But in NB11, it’s a set of gradle projects and I can’t
even utilize the php features when accessing the project from the folder
explorer tab. (as opposed to the project tab, which has been rendered
useless.){noformat}
from thread:
http://mail-archives.apache.org/mod_mbox/netbeans-users/201907.mbox/browser
> 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
> Labels: pull-request-available
> Attachments: dasaa.7z
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.14#76016)
-
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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904515#comment-16904515 ] Eric Bresie commented on NETBEANS-1802: --- Was curious if an "Eclipse" feature comment would be relevant here... In Eclipses,a given project can have different "Facets" configured for a given project. So if for example, a project includes Gradle files, then the project is configured to have that Facet added/configured; if "EJB" related files/functionality are applicable, the given "EJB" equivalent Facet is configured for the project. As part of this, the decorations on the given project icon gives indication of type based on added icon indicators on the project. So assume if some "project" configuration meta data can either be automatically determined (based on the applicable build files) or could be manually added to some netbean project metadata file, could something like this be usable 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 >Assignee: Laszlo Kishalmi >Priority: Critical > Labels: pull-request-available > Attachments: dasaa.7z > > Time Spent: 40m > Remaining Estimate: 0h > > 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.14#76016) - 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725659#comment-16725659 ] Christian Lenz commented on NETBEANS-1802: -- Again a real world example. Another team put the backend (Java, Maven) together with the frontend (Different folder for the "client") but put the package.json and the pom.xml together in the same project folder. Now NetBeans shows me that this is a maven project.. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727272#comment-16727272 ] Laszlo Kishalmi commented on NETBEANS-1802: --- Well NetBeans evaluates projects upon the order of ProjectFactory registration id-s. Though it might be possible to offer the type of project to be opened with when multiple ProjectFactory is available for the same folder. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728709#comment-16728709 ] Christian Lenz commented on NETBEANS-1802: -- That would be good, yes. Or to enable/disable project features on demand, because sometimes, I need to do stuff with the other project type. Or with such project features. But choosing the project while opening is good. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728814#comment-16728814 ] Emilian Bold commented on NETBEANS-1802: This is an interesting improvement but I don't see how it could be something critical. Do people really have such hybrid projects? The project API is a bit sensitive code, but I believe this feature could be even implemented as a simple plugin. Just have a plugin that recognises both project types then delegate to one or the other depending on some configuration / GUI popup. > 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] [Commented] (NETBEANS-1802) Problem with loading a project which has 2 different project files
[ https://issues.apache.org/jira/browse/NETBEANS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728825#comment-16728825 ] Christian Lenz commented on NETBEANS-1802: -- For me it is critical, because I can't use the IDE for that project type, that I need to. We can move it to major, for sure, but this will always happen, if we have this hybrid projects. Accidentally or when someone worked with an other IDE. I had this 3 times over the past 3 years. First the Nexus thing, where the pom only was used for the Nexus repo to upload the artifact. Then the problem with the Puppet Plugin for NetBeans, where every project you have is treated as a Puppet Project, when the plugin find the matching folder/file. And now I have the problem again, with the team, that mixed a maven project with a client folder but added package.json and pom.xml into the same folder. > 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
