Greetings, Well, yes, I've had gradle issues in the past due to work projects. It is rather important that the people trying to fix issue X have a way to ensure that they are using code that invokes issue X to see if they are actually fixing issue X.
_*Nobody*_ expects you to publish your non-opensource project. Anybody else who might consider working upon your issue expects you to provide an example that shows your failure mode if you cannot expose the project with which you have a problem. The interesting bit is that you /may/ (not will, but *MAY*) find the source of your issue while creating the simulated project that reflects the very issue you have. Get a throw-away email account and create a GitHub account for your simulated project. Or provide a link to git repo that shows your issue. Or create a local file tree of your simulated gradle projects tree, tar it up, and attach it to your JIRA ticket. There is not a single person on this mailing list who will get money for fixing your problem. (assuming you haven't set a bounty to do so). You should make it simple to other humans to replicate your problem so that they may help. -- Mark A. Flacy mfl...@verizon.net On Monday, June 26, 2023 7:18:53 AM CDT Thomas Kellerer wrote: > Well, I can't show the real project (customer project with NDA). And I can't > just create a project of that size (35 projects, 550K lines of code). AndNob > besides I don't have a Github account. > > The problem is, that basically every problem I have with NetBeans and Gradle > only happens on bigger projects (and not with some tiny example projects. > It would be a lot more helpful if NetBeans offered some diagnostic data > that would allow investigating such a problem. It's pretty unrealistic to > as every user that has a problem to publish their projects. > > I thought Gradle uses the term "module" for projects that consist of > multiple sub-projects, but apparently I was wrong. > > The layout is: > > main_project > sub-project1 > sub-sub-project1 > sub-sub-project2 > sub-project2 > sub-project3 > sub-sub-project1 > sub-sub-project2 > sub-sub-project3 > sub-sub-project4 > sub-sub-project5 > sub-sub-project6 > sub-sub-project7 > sub-sub-project8 > sub-sub-project9 > sub-sub-project10 > sub-sub-project11 > sub-sub-project12 > sub-sub-project13 > sub-sub-project14 > sub-sub-project15 > sub-project4 > sub-project5 > sub-project6 > sub-project7 > sub-sub-project1 > sub-sub-project2 > sub-sub-project3 > sub-sub-project4 > sub-sub-project5 > sub-sub-project6 > sub-sub-project7 > sub-sub-project8 > sub-sub-project8 > sub-project8 > sub-sub-project1 > sub-sub-project2 > sub-sub-project3 > sub-sub-project4 > sub-sub-project5 > sub-project9 > sub-project10 > sub-project11 > sub-project12 > sub-sub-project1 > sub-sub-project2 > > sub-project13 > > For those sub-projects that aren't recognized I can see the following > entries in the NetBeans logfile: > > INFO [org.netbeans.modules.gradle.loaders.GradleProjectLoaderImpl]: Load > aiming EVALUATED for Unloaded Gradle Project: > GradleFiles[projectDir=C:\Projects\******\main\commons, > rootDir=C:\Projects\*******\main] > > Thomas > > Mark A. Flacy schrieb am 26.06.2023 um 13:47: > > Create a simple example in GitHub or GitLab so that people have something > > to test against. > > > > I'm not sure how your project is set up, since I normally don't use the > > term "module" in gradle projects. > > > > > > > > Sent from my Galaxy > > > > > > -------- Original message --------
