[
https://issues.apache.org/jira/browse/NETBEANS-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856431#comment-16856431
]
Rick edited comment on NETBEANS-2633 at 6/5/19 7:27 AM:
--------------------------------------------------------
We need this layout because we have multiple root projects that share a common
library.
Each root project corresponds to a customer project, and those root projects
all have a sub project that contains some customer specific code. For example:
{color:#8eb021}Customer project 1: (root)
- subproject: customerProject1Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
Customer project 2: (root)
- subproject: customerProject2Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
-- depends on: library:proj2
Customer project 3: (root)
- subproject: customerProject3Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
-- depends on: library:proj2
library
- proj1
- proj2 (depends on proj1)
{color}
As you can see, it would be impossible to put the library code inside project
1. The library itself is never built separately, so it also does not make sense
for it to have a settings.gradle. I understand that our layout may be a bit
strange, but do you have any suggestions on how this layout could be improved?
was (Author: nlrhendr):
We need this layout because we have multiple root projects that share a common
library.
Each root project corresponds to a customer project, and those root projects
all have a sub project that contains some customer specific code. For example:
Customer project 1: (root)
- subproject: customerProject1Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
Customer project 2: (root)
- subproject: customerProject2Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
-- depends on: library:proj2
Customer project 3: (root)
- subproject: customerProject3Specific (has the main class that basically
extends an abstract class from proj1)
-- depends on: library:proj1
-- depends on: library:proj2
library
- proj1
- proj2 (depends on proj1)
As you can see, it would be impossible to put the library code inside project
1. The library itself is never built separately, so it also does not make sense
for it to have a settings.gradle. I understand that our layout may be a bit
strange, but do you have any suggestions on how this layout could be improved?
> Netbeans 11 gradle cannot open projects with dependencies outside the root
> project
> ----------------------------------------------------------------------------------
>
> Key: NETBEANS-2633
> URL: https://issues.apache.org/jira/browse/NETBEANS-2633
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
> Affects Versions: 11.0
> Reporter: Rick
> Assignee: Laszlo Kishalmi
> Priority: Major
> Attachments: dependencyOutsideRoot.zip,
> image-2019-06-03-14-18-17-417.png, image-2019-06-03-14-18-57-811.png
>
>
> To reproduce, execute the following (after extracting the attached zip file):
> {{cd proj1}}
> {{gradle run}}
> That will output Hello world.
> When opened in netbeans 11, this shows:
> !image-2019-06-03-14-18-17-417.png!
> With the following error
> !image-2019-06-03-14-18-57-811.png!
> So it seems that netbeans thinks proj3 is a root project (which it isn't).
>
> I expect netbeans to open this project without errors. This worked fine in
> netbeans 8.2 with the old gradle plugin.
--
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
