This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Some projects keep different types of build scripts to enable various styles of development but it is not possible at the moment to force NetBeans to open a directory as a project of some type if there is another project type with a higher priority recognizing it first. It is becoming common in Android world where people migrate from Ant-based projects to Gradle (for example Facebook SDK has samples and libraries like this). Similar example of Maven/Gradle conflict is mentioned in http://stackoverflow.com/questions/23021784/how-to-force-netbeans-load-gradle-project-instead-of-maven-pom I have seen project with Ant build.xml and Maven pom.xml too. This is often result of migration but it may have sense to use it as Ant or as Maven under different scenarios.
Hi,I am working to a Project that supports both Gradle and Maven developers and I think many are in similar situations. However IMHO it is pointless to go through a wizard of a certain type of project and see your project change to a Maven type next time you start Netbeans just because you added a POM file. Eclipse has a project nature that helps managing this kind of situations. This is a possible solution, or at least give the choice to keep a certain project layout/build system or to switch between them.
Any progress on this? I've developed a ProjectType which can open any directory. This was necessary to handle Ansilbe projects which very often do not have a clear structure. Is it at least possible to have my project type checked after all other more specific projects haven been tried? Can I define e.g. a priority somewhere?