Re: Builds: Always Show Output (default values)
I would prefer to always show the output, it’s a way to see how the build is progressing. In the case of maven and gradle I always like to have a look at the dependency download stage for example. Alternatively a “always show when build fails” behavior is also acceptable. Regards Alex Il giorno dom 10 feb 2019 alle 02:31 Laszlo Kishalmi < laszlo.kisha...@gmail.com> ha scritto: > Dear all, > > The Always Show Output setting default values are not consistent among > Build Systems: > > - Ant: false > - Maven: true > - Gradle: false > > I can make them consistent, but the question is what should that be? > > (FYI: This setting controls whether the output window should be shown on > all builds, or just in the case when your builds fails.) > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Writing plugins for NetBeans 11.0
Hi Lazslo, Yes I started developing that plugin in May 2016 with a first public release in June for NetBeans 8.1 and Java 7 (wow, time flies). It’s already Apache 2.0 licensed thus could be merged in the future should I decide to donate it. Had a look at PR 1114 diffs, very interesting, that should allow to run and debug SpringBoot gradle projects right? Thank you for your swift reaction to my wishes! Looking forward to its merge into master. Regards, Alex Il giorno ven 1 feb 2019 alle 20:41 Laszlo Kishalmi < laszlo.kisha...@gmail.com> ha scritto: > Just checked the github link, it seems we have a well established plugin > here, please ignore my previous message, I've even copied the wrong link > for the PR... > > https://github.com/apache/incubator-netbeans/pull/1114 > > On 2/1/19 10:44 AM, Laszlo Kishalmi wrote: > > Just a question to consider. Wouldn't it be better to add the the code > > to NetBeans itself? > > > > Like: https://github.com/apache/incubator-netbeans/pull/ > > > > On 2/1/19 4:18 AM, Alessandro wrote: > >> Thanks for the info, Eric. > >> > >> Will try to populate the local repository following the procedure you > >> indicated. > >> > >> Regards, > >> Alex > >> > >> Il giorno ven 1 feb 2019 alle ore 12:33 Eric Barboni > >> ha > >> scritto: > >> > >>> Hi, > >>> Publication of maven artefacts are currently on hold to be sure > >>> how it > >>> should be done the apache way. > >>> > >>> You can populate your own repository using the following procedure > >>> see > >>> this comment from Rami Swailem [1]. > >>> > >>> We will later have snapshot version of master branch > >>> > >>> Best Regards > >>> Eric > >>> > >>> > >>> > https://issues.apache.org/jira/browse/NETBEANS-467?focusedCommentId=16684815=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16684815 > >>> > >>> > >>> > >>> -Message d'origine- > >>> De : Alessandro > >>> Envoyé : vendredi 1 février 2019 11:16 > >>> À : dev@netbeans.incubator.apache.org > >>> Objet : Writing plugins for NetBeans 11.0 > >>> > >>> Hi all, > >>>I would like to start playing with the new Gradle support in my NB > >>> Spring Boot plugin (https://github.com/AlexFalappa/nb-springboot) > which > >>> is written using maven and uses the RELEASE82 artifacts from the > >>> repository > >>> at http://bits.netbeans.org/nexus/content/groups/netbeans. > >>> > >>> I know that the publication of maven artifacts for the platform > >>> modules is > >>> ongoing. > >>> > >>> What should I do ? Is there a way to work on the platform in > >>> development > >>> (say a RELEASE11-SNAPSHOT in maven parlance) or is it better to wait > >>> for > >>> official publication of maven artifacts? Is there any documentation on > >>> working with the bleeding edge platform using maven? > >>> > >>> Regards, > >>> Alex > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > >>> For additional commands, e-mail: > dev-h...@netbeans.incubator.apache.org > >>> > >>> For further information about the NetBeans mailing lists, visit: > >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >>> > >>> > >>> > >>> > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Writing plugins for NetBeans 11.0
Thanks for the info, Eric. Will try to populate the local repository following the procedure you indicated. Regards, Alex Il giorno ven 1 feb 2019 alle ore 12:33 Eric Barboni ha scritto: > Hi, > Publication of maven artefacts are currently on hold to be sure how it > should be done the apache way. > > You can populate your own repository using the following procedure see > this comment from Rami Swailem [1]. > > We will later have snapshot version of master branch > > Best Regards > Eric > > > https://issues.apache.org/jira/browse/NETBEANS-467?focusedCommentId=16684815=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16684815 > > > -Message d'origine- > De : Alessandro > Envoyé : vendredi 1 février 2019 11:16 > À : dev@netbeans.incubator.apache.org > Objet : Writing plugins for NetBeans 11.0 > > Hi all, > I would like to start playing with the new Gradle support in my NB > Spring Boot plugin (https://github.com/AlexFalappa/nb-springboot) which > is written using maven and uses the RELEASE82 artifacts from the repository > at http://bits.netbeans.org/nexus/content/groups/netbeans. > > I know that the publication of maven artifacts for the platform modules is > ongoing. > > What should I do ? Is there a way to work on the platform in development > (say a RELEASE11-SNAPSHOT in maven parlance) or is it better to wait for > official publication of maven artifacts? Is there any documentation on > working with the bleeding edge platform using maven? > > Regards, > Alex > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Writing plugins for NetBeans 11.0
Hi all, I would like to start playing with the new Gradle support in my NB Spring Boot plugin (https://github.com/AlexFalappa/nb-springboot) which is written using maven and uses the RELEASE82 artifacts from the repository at http://bits.netbeans.org/nexus/content/groups/netbeans. I know that the publication of maven artifacts for the platform modules is ongoing. What should I do ? Is there a way to work on the platform in development (say a RELEASE11-SNAPSHOT in maven parlance) or is it better to wait for official publication of maven artifacts? Is there any documentation on working with the bleeding edge platform using maven? Regards, Alex
Re: Calling all Gradle users!
Hi all, with today's build the exception are fixed and Gradle projects generated by Spring Initializr can be opened, built and tested. I found some minor annoyances for which I opened NETBEANS-2035, 2036, 2037 and 2038. The next step would be to be able to run and debug the project as Martin pointed out (the buttons and context menu items are currently grayed out). Keep up the good work Laszlo! Regards, Alex Il giorno mer 30 gen 2019 alle ore 23:18 Martin Weißhaupt ha scritto: > Hi Alex, > > you are right, the workaround worked for me too so I marked my ticket as > a duplicate of yours. > > That is what I get for not reading the comments on the tickets :D > > BTW: > Does anyone know if there is a way to overwrite or select the run and > debug tasks yet? With my projects they are not enabled but maby this is > expected at the current stage of development. > > Regards, > Martin >
Re: Calling all Gradle users!
Hi Martin, I noticed that the exception stacktrace you reported is very similar to the one I faced, the root cause might be the same. Anyway it seems Laszlo is aware of the problems and willing to solve them. Regards, Alex Il giorno mer 30 gen 2019 alle 22:40 Martin Weißhaupt ha scritto: > Hi, > > I have had some time to investigate further and I noticed that I just > need to create a project with the inofficial gradle Plugin and Netbeans > 8.2 to reproduce the issue. > > Therefore I created a repository with a project to reproduce it: > https://github.com/mweisshaupt1988/Netbeans11GradleTest > > As well as a Jira Issue since I believe that Alex propably has a > different issue: > https://issues.apache.org/jira/browse/NETBEANS-2030 > > If not please flag my bug as a duplicate. > > Let me know if there is anything else I can do to help. The stuff that > works does look very good for me :) > > Regards, > Martin >
Re: JIRA component for new gradle support
Hi John, Thanks for your swift reaction and for retargeting my issue. Cheers, Alex Il giorno mer 30 gen 2019 alle 20:14 John McDonnell < mcdonnell.j...@gmail.com> ha scritto: > Should be there now :) > > Regards > > John >
Re: Calling all Gradle users!
Hi,
I stumbled upon the same issue reported by Martin while trying to open a
project generated by the Spring Initializr service (http://start.spring.io).
I have opened NETBEANS-2024 to track the issue with instructions to
reproduce and an exceptions raised.
The resulting project is unloadable and unbuildable thus a showstopper for
Spring Boot + Gradle users.
Regards,
Alex
Il giorno mer 30 gen 2019 alle ore 14:52 Martin Weißhaupt
ha scritto:
> Hello,
>
> I use Gradle mostly for private projects and I have a few to try out.
> My biggest one is a toy project for a web framework which uses Hibernate
> Pojos to render a ui.
>
> This is the first one I have tried and it failed with the following
> exception:
> java.lang.NullPointerException: The file parameter cannot be null
> at org.openide.util.Parameters.notNull(Parameters.java:64)
> at org.openide.filesystems.FileUtil.toFileObject(FileUtil.java:853)
> at
>
> org.netbeans.modules.gradle.queries.GradleSourceForBinary.findSourceRoots2(GradleSourceForBinary.java:59)
> at
>
> org.netbeans.api.java.queries.SourceForBinaryQuery.findSourceRoots2(SourceForBinaryQuery.java:101)
> at
>
> org.netbeans.modules.parsing.impl.indexing.PathRegistry.createResources(PathRegistry.java:728)
> at
>
> org.netbeans.modules.parsing.impl.indexing.PathRegistry.getSources(PathRegistry.java:275)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RootsWork.getDone(RepositoryUpdater.java:4888)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$InitialRootsWork.getDone(RepositoryUpdater.java:5821)
> [catch] at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doTheWork(RepositoryUpdater.java:3420)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task._run(RepositoryUpdater.java:6183)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.access$4300(RepositoryUpdater.java:5834)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2$1.run(RepositoryUpdater.java:6099)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
> at
>
> org.netbeans.modules.parsing.impl.RunWhenScanFinishedSupport.performScan(RunWhenScanFinishedSupport.java:83)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6095)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6091)
> at
>
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
>
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
>
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
>
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
>
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.run(RepositoryUpdater.java:6091)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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)
>
> Well failed is not really true.
> It opens, it builds, it runs the targets I have tried but it shows this
> exception in a dialog whenever I open the project or a file in the project.
>
> Since this seems to be related to repository updates here are my configured
> repositories for this project:
> repositories
> {
> flatDir { dirs "lib" }
> mavenCentral()
> maven { url "http://mavensync.zkoss.org/maven2; }
> maven { url "http://mavensync.zkoss.org/eval; }
> }
>
> The project uses a gradle wrapper with gradle version 4.10.2 currently.
>
> I can provide more information if needed.
> I'll try to try out other existing projects as soon as possible.
>
> Regards,
> Martin
>
> Am Sa., 26. Jan. 2019 um 14:07 Uhr schrieb Geertjan Wielenga
> :
>
> > 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
Re: Calling all Gradle users!
Correction: I opened NETBEANS-2029 'Unloadable Spring Initializr gradle project' Il giorno mer 30 gen 2019 alle ore 20:00 Alessandro ha scritto: > Hi, > I stumbled upon the same issue reported by Martin while trying to open a > project generated by the Spring Initializr service (http://start.spring.io > ). > > I have opened NETBEANS-2024 to track the issue with instructions to > reproduce and an exceptions raised. > > The resulting project is unloadable and unbuildable thus a showstopper for > Spring Boot + Gradle users. > > Regards, > Alex >
JIRA component for new gradle support
Hi, a component should be created in JIRA for categorizing bugs related to the new gradle support. There is currently 'projects - Ant project' and 'projects - Maven' but no 'projects - Gradle' or similar. Some bugs have been filed with a 'gradle' label. Greetings, Alex
Re: Re: What to do with features for EARs and EJBs?
Hi Ondro, Il giorno mer 30 gen 2019 alle ore 10:08 Ondro Mihályi < ondrej.miha...@gmail.com> ha scritto: > ... Although the project creation dialog refers to Java EE in one select box, it allows choosing Tomcat and only adds dependencies present in Tomcat. In > addition, if there was a plugin for generating Ant-based Spring Boot apps, > it could also be in this category, as it would be a Java Web project, > although a separate SpringBoot type packaged as JAR. > ... > - Ondro > While creating an Ant project using Spring Boot is entirely possible it is not recommended as Spring Boot heavily relies on a build tool with dependency management capabilities (see https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-build-systems.html ). The NB Spring Boot plugin I created intentionally adds items to the Maven category for this reason. Now that Gradle support is in master it could be worth having a look at supporting Spring Boot Gradle projects too. Greets, Alessandro
