[
https://issues.apache.org/jira/browse/NETBEANS-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804023#comment-16804023
]
Dell Green commented on NETBEANS-2320:
--------------------------------------
A workaround for now could be to rename the gradle build file and then
explicitly specify the build file by name using -b option to gradle cli
> Opening project with both pom.xml and build.gradle defaults to gradle project
> -----------------------------------------------------------------------------
>
> Key: NETBEANS-2320
> URL: https://issues.apache.org/jira/browse/NETBEANS-2320
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Project
> Affects Versions: 11.0
> Reporter: Dell Green
> Priority: Minor
>
> When opening a project that has both a pom.xml and a build.gradle file, it
> defaults to gradle.
> This may not be correct as in my case as the gradle files are for other
> production related functionality and not IDE related.
> The expectation in this case would be that the user is offered the choice of
> which type of project to open as.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
