Just a small bit of further feedback, in the project navigator pane (the one with the tree in). If you don't have a main project selected the set main project right click item doesn't appear. But if you have one selected the set main project does appear. I would say it should always appear.
On Sat, 26 Jan 2019, 20:07 Peter Steele <steeleh...@gmail.com wrote: > Hi > > Some good news on testing further with a brand new project and maybe some > suggestions for further enhancements > > 1) The exception I saw was caused by gradle running a too old version on > root project (the default gradle installation on linux was too low for jdk > 11 (actually 9 10 and 11). I fixed it by running this "gradle wrapper > --gradle-version 5.1". > 2) The issue of not loading the sub projects was only because I didn't > open the project from the project dialog, it opened because it was the last > project I opened. My suggestion here would be to default to open all > subprojects in this scenario. > 3) The issue of the sub projects changing name was caused because I had a > settings.gradle in root project and all the sub projects from the previous > gradle pluggin. In the new netbeans it is not done this way. My suggestion > here is to better handle the behavior if settings.gradle is present and has > rootProject.nane=XXXXX set to a value different to the directory name of > the project (the previous plugin allowed you to set th emodule name and > project name). > 4) The other reason for the compiling not working is because the root > project settings.gradle did not have all the includes set for the sub > project. > > For 3 and 4 I think this was caused by a old version of the current gradle > plugin as it doesn't happen now. and produces similar file to the new > version of netbeans > > So overall a positive experice (once I fixed issues with my project). > > Regards > > Peter > > On Sat, Jan 26, 2019 at 3:21 PM Peter Steele <steeleh...@gmail.com> wrote: > >> H >> >> I downloaded the new version and ran it side by side with the current >> setup. After installing javafx (which was new), I got an error initially >> >> java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 >> at >> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) >> at >> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) >> at >> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) >> at java.base/java.util.Objects.checkIndex(Objects.java:372) >> at java.base/java.util.ArrayList.get(ArrayList.java:458) >> at >> org.netbeans.modules.gradle.options.GradleDistributionManager.evaluateGradleWrapperDistribution(GradleDistributionManager.java:209) >> at >> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:159) >> at >> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:83) >> [catch] at >> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:337) >> at >> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:311) >> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) >> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) >> at >> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) >> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) >> at >> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) >> >> It then installed nc-javac and requested a restart. After the restart I >> got the same error again. My root project + subprojects project was >> attempted to be opened but it didn't recognise the fact the that the root >> project was a root project and didn't load all the sub projects. When I >> closed all the projects and reopened the root project it seemed to >> recognise the root project and that it had sub projects just fine but the >> error above still came up. >> >> When I right click on the sub projects and say open project (would be >> much nicer if they were opened by default), the project name in the sub >> projects tree and the name in the new open project tree node are renamed to >> the settings.gradle -> rootProject.name value from the directory name value >> (which is the name of the project it was given when created). >> >> When I try and run the main sub project, which depends on the other sub >> projects I get lots of compile errors because it can't find the classes in >> the other sub projects. This is because the compile dependencies are >> currently set in the build.gradle of the root project. In the current >> gradle plugin it runs everything from the root projects perspective and >> allows you to choose a sub project to be the main sub project where as this >> new version of netbeans runs things from the perspective of the subproject >> in isolation. >> >> Sorry if the above doesn't make sense, I will try later on today to get >> an example project together which highlights as many of the issues as I >> can. I'll create the project in the new version of netbeans to test the >> creation process too. >> >> Regards >> >> Peter >> >> >> On Sat, Jan 26, 2019 at 2:06 PM marccollin7...@gmail.com < >> marccollin7...@gmail.com> wrote: >> >>> like i said work fine.... but it use a lot more memory... >>> >>> gc monitor with netbeans 10 turn around 500mb... now with this release i >>> go to 2000mb.... and cpu is high >>> >>> On 2019/01/26 13:07:14, Geertjan Wielenga >>> <geertjan.wiele...@googlemail.com.INVALID> wrote: >>> > Hi all, >>> > >>> > If you're using Gradle in any way at all -- and especially if you have >>> some >>> > Gradle projects of whatever kind lying around -- we need you! >>> > >>> > Thanks to Laszlo, we have integration with Gradle for the first time >>> in the >>> > upcoming release scheduled to be released in March. We need as many as >>> > possible to try out the Gradle features, i.e., simply open your >>> existing >>> > projects into the latest NetBeans builds and see if there are any >>> problems >>> > so they can be fixed in time. >>> > >>> > Interested? Please respond to this e-mail indicating your intention to >>> try >>> > out your existing Gradle projects in the upcoming release of Apache >>> > NetBeans and we'll work on this together from there initially via this >>> mail >>> > thread. >>> > >>> > For example, without any problems at all, I was able to open and work >>> with >>> > this random project I found on GitHub: >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org >>> For additional commands, e-mail: users-h...@netbeans.apache.org >>> >>> For further information about the NetBeans mailing lists, visit: >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >>> >>>
