[
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
