Forcing download of binaries
Hi, today I have cloned a fresh new copy of NetBeans repository and I got this error. Is there any way to force the download ? Enrico BUILD FAILED /home/diennea.lan/enrico.olivelli/dev/incubator-netbeans/nbbuild/build.xml:128: Could not download D6330851B59C33A3A8D98C86FF438F23DD3B4267-ant-misc-1.10.4.zip from http://netbeans.osuosl.org/binaries/: java.io.IOException: Could not download D6330851B59C33A3A8D98C86FF438F23DD3B4267-ant-misc-1.10.4.zip to /home/diennea.lan/enrico.olivelli/.hgexternalcache/D6330851B59C33A3A8D98C86FF438F23DD3B4267-ant-misc-1.10.4.zip: java.io.IOException: Skipping download from http://netbeans.osuosl.org/binaries/D6330851B59C33A3A8D98C86FF438F23DD3B4267-ant-misc-1.10.4.zip due to response code 503 at org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:249) at org.netbeans.nbbuild.extlibs.DownloadBinaries.fillInFile(DownloadBinaries.java:190) at org.netbeans.nbbuild.extlibs.DownloadBinaries.execute(DownloadBinaries.java:156) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) at org.apache.tools.ant.Project.executeTarget(Project.java:1376) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1260) at org.apache.tools.ant.Main.runBuild(Main.java:854) at org.apache.tools.ant.Main.startAnt(Main.java:236) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:285) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:112) Caused by: java.io.IOException: Skipping download from http://netbeans.osuosl.org/binaries/D6330851B59C33A3A8D98C86FF438F23DD3B4267-ant-misc-1.10.4.zip due to response code 503 at org.netbeans.nbbuild.extlibs.DownloadBinaries.downloadFromServer(DownloadBinaries.java:275) at org.netbeans.nbbuild.extlibs.DownloadBinaries.legacyDownload(DownloadBinaries.java:262) at org.netbeans.nbbuild.extlibs.DownloadBinaries.lambda$execute$1(DownloadBinaries.java:156) at org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:226) ... 18 more - 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: Calling all Gradle users!
Il giorno dom 27 gen 2019, 23:20 Laszlo Kishalmi
ha scritto:
> Dear Enrico,
>
> You are facing with: https://issues.apache.org/jira/browse/NETBEANS-2009,
>
> I've something on my mind already to fix this.
>
I will be happy to try your fix
Thanks
Enrico
>
> On 1/26/19 2:21 PM, Enrico Olivelli wrote:
> > Hi,
> > I am trying latest nightly build on linux + jdk8 (and with jdk8 the
> > result is the same) on the project linked below, itis quite complex
> > but I was able to work on it with the 'other' plugin.
> > https://github.com/pravega/pravega
> >
> > The project has a lot of subprojects but I can see only the first one
> > ("pravega common") displayed in the project tree.
> > I can't see any particular error in logs apart from this, but it seems
> unrelated
> >
> > INFO [org.openide.loaders.FolderInstance.Toolbars]: Cannot create
> > org.openide.loaders.FolderInstance$HoldInstance@259ead78[Toolbars/Build]
> > java.io.IOException: Cyclic reference. Somebody is trying to get value
> > from FolderInstance (org.openide.awt.Toolbar$Folder) from the same
> > thread that is processing the instance
> > at
> org.openide.loaders.FolderInstance.instanceCreate(FolderInstance.java:274)
> > at
> org.openide.loaders.FolderInstance.instanceForCookie(FolderInstance.java:555)
> > at
> org.openide.loaders.FolderInstance$HoldInstance.instanceCreate(FolderInstance.java:1132)
> > [catch] at
> org.openide.loaders.FolderInstance$1R.instances(FolderInstance.java:675)
> > at
> org.openide.loaders.FolderInstance$1R.run(FolderInstance.java:696)
> > 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)
> >
> > To reproduce:
> > - download nightly build
> > - unzip
> > - git clone https://github.com/pravega/pravega
> > - open with netbeans
> > - install nbjavac (this pops up)
> > - you will see only a subproject "common", but if you look at
> > build.gradle or you run "clean and build" you will see that there are
> > plenty of modules
> >
> >
> > Any hint/help is appreciated.
> > I am available to any debug, I have never debugged NB before, so any
> > pointer will help
> >
> > Cheers
> > Enrico
> >
> > Il giorno sab 26 gen 2019 alle ore 22:42 Scott Palmer
> > ha scritto:
> >> I exclusively use Gradle, so I will be testing extensively. The new
> plugin (or maybe it is partly the NB build) does have some issues with my
> projects. I will attempt to isolate a test case. I already emailed Laszlo,
> but he needs to be able to reproduce the issue.
> >>
> >> Scott
> >>
> >>> On Jan 26, 2019, at 8:07 AM, Geertjan Wielenga
> wrote:
> >>>
> >>> https://github.com/gradle/gradle-build-scan-quickstart
> >>>
> >>> ...and we need more like that to play with to see whether the new
> Gradle support works! :-)
> >>>
> >>> Gj
> >>>
> >>>
> >>>
> >>>> On Sat, Jan 26, 2019 at 2:07 PM Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> 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: 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: Calling all Gradle users!
Hi,
I am trying latest nightly build on linux + jdk8 (and with jdk8 the
result is the same) on the project linked below, itis quite complex
but I was able to work on it with the 'other' plugin.
https://github.com/pravega/pravega
The project has a lot of subprojects but I can see only the first one
("pravega common") displayed in the project tree.
I can't see any particular error in logs apart from this, but it seems unrelated
INFO [org.openide.loaders.FolderInstance.Toolbars]: Cannot create
org.openide.loaders.FolderInstance$HoldInstance@259ead78[Toolbars/Build]
java.io.IOException: Cyclic reference. Somebody is trying to get value
from FolderInstance (org.openide.awt.Toolbar$Folder) from the same
thread that is processing the instance
at
org.openide.loaders.FolderInstance.instanceCreate(FolderInstance.java:274)
at
org.openide.loaders.FolderInstance.instanceForCookie(FolderInstance.java:555)
at
org.openide.loaders.FolderInstance$HoldInstance.instanceCreate(FolderInstance.java:1132)
[catch] at
org.openide.loaders.FolderInstance$1R.instances(FolderInstance.java:675)
at org.openide.loaders.FolderInstance$1R.run(FolderInstance.java:696)
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)
To reproduce:
- download nightly build
- unzip
- git clone https://github.com/pravega/pravega
- open with netbeans
- install nbjavac (this pops up)
- you will see only a subproject "common", but if you look at
build.gradle or you run "clean and build" you will see that there are
plenty of modules
Any hint/help is appreciated.
I am available to any debug, I have never debugged NB before, so any
pointer will help
Cheers
Enrico
Il giorno sab 26 gen 2019 alle ore 22:42 Scott Palmer
ha scritto:
>
> I exclusively use Gradle, so I will be testing extensively. The new plugin
> (or maybe it is partly the NB build) does have some issues with my projects.
> I will attempt to isolate a test case. I already emailed Laszlo, but he
> needs to be able to reproduce the issue.
>
> Scott
>
> > On Jan 26, 2019, at 8:07 AM, Geertjan Wielenga
> > wrote:
> >
> > https://github.com/gradle/gradle-build-scan-quickstart
> >
> > ...and we need more like that to play with to see whether the new Gradle
> > support works! :-)
> >
> > Gj
> >
> >
> >
> >> On Sat, Jan 26, 2019 at 2:07 PM Geertjan Wielenga
> >> 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: 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: [VOTE] Apache NetBeans Version Number: 11.0
+1(non binding) Enrico Il giorno sab 26 gen 2019, 08:19 Tomas Poledny ha scritto: > +1 > > On Sat, Jan 26, 2019, 05:54 Vano Beridze > > +1 > > > > On Sat, Jan 26, 2019, 7:51 AM Laszlo Kishalmi > wrote: > > > > > Dear all, > > > > > > Well, it is time to finalize out version scheme for a while. There will > > > be three voting threads created on this topic with subjects: > > > > > > * [VOTE] Apache NetBeans Version Number: 11 > > > * [VOTE] Apache NetBeans Version Number: 11.0 > > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > > > Everyone from the community can cast his/her own vote on each thread > as: > > > > > > +1 I like it, let's do this way > > > 0I'm Ok with it, does not particularly like it, but won't mind it > > > -1 I do not like it at all. > > > > > > Each thread is going to be open for 72+ hours and going to be closed at > > > the same time. Regardless from the number of votes, that version number > > > would win which has the greatest sum of the vote values. > > > > > > Voting is a community event! Be a proud community member and cast your > > > vote! > > > > > > Thank you! > > > > > > Laszlo Kishalmi > > > > > > Volunteer Release Manager of Apache NetBeans 11.0 > > > > > > P.S.: Please keep this thread for voting only! > > > > > > > > >
Re: Porting 8.2 plugin to 10 problem
Hi, Can't you just add that dependency explicitly? It has been removed from jdk, but it is still available on Maven central. Enrico Il mer 2 gen 2019, 17:38 Peter Cheung ha scritto: > Hi Peter > May I know which part is module dev supports for jdk >8? I mean where > is the code for this thing?. I want to know anything i can help > > > Thanks > From Peter > > From: Peter Nabbefeld > Sent: Tuesday, January 1, 2019 11:23 PM > To: dev@netbeans.incubator.apache.org > Subject: Re: Porting 8.2 plugin to 10 problem > > Hi Peter, > > the Generated annotation has moved somewhere, IIRC, so the annotation > processor creates Java code with non-working imports. For the bundles, > it will probably be better to use property files. Or better wait, until > JDK > 8 is supported for module development, as modules targeted to NB > 8.x should still work in most cases. > > Kind regards > > Peter > > > > Am 01.01.19 um 15:54 schrieb Peter Cheung: > > Hi > > I am porting my plugins to Netbeans 10, but all of them have this > error. It auto generated a java file called Bundle.java and it is unable to > compile since it can't find @javax.annotahition.Generated > > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile > (default-compile) on project netbeans-antlr: Compilation failure: > Compilation failure: > > [ERROR] > /Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/syntax/antlr3/realtimecompile/Bundle.java:[3,17] > error: cannot find symbol > > [ERROR] symbol: class Generated > > [ERROR] location: package javax.annotation > > [ERROR] > /Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/Bundle.java:[3,17] > error: cannot find symbol > > [ERROR] symbol: class Generated > > [ERROR] location: package javax.annotation > > [ERROR] > /Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/syntax/antlr4/realtimecompile/Bundle.java:[3,17] > error: cannot find symbol > > [ERROR] -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > > > > > > Thanks > > From Peter > > > > > - > 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 > > > > -- -- Enrico Olivelli
Re: Surefire plugin issue
Can you post the link to the PR ? Enrico Il mer 28 nov 2018, 17:36 Enrico Olivelli ha scritto: > Thank you. > > To be honest I found the same problem inin the project I am working on. > After re-looking the same output every day I failed to see the problem. > Cheers > Enrico > > > Il mer 28 nov 2018, 16:07 Jean-Marc Borer ha scritto: > >> OK, so I found the issue in the code (it is actually broken) and fixed it. >> Going to publish a PR soon. >> >> On Mon, Nov 26, 2018 at 4:52 PM Jean-Marc Borer >> wrote: >> >> > If you can't get the zip from the list, you can grab it from >> > https://issues.apache.org/jira/browse/NETBEANS-635 >> > >> > On Mon, Nov 26, 2018 at 4:50 PM Jean-Marc Borer >> wrote: >> > >> >> Ok I could reproduce it with very small sample project. Just clean and >> >> build and you will see that there will be no stacktrace parsing... >> >> >> >> On Mon, Nov 26, 2018 at 4:43 PM Jean-Marc Borer >> >> wrote: >> >> >> >>> Can you see the screenshot I attached my last message (the one with >> the >> >>> XML)? >> >>> >> >>> On Mon, Nov 26, 2018 at 4:30 PM Enrico Olivelli >> >>> wrote: >> >>> >> >>>> Jan-Marc, >> >>>> I am sorry, I can't reproduce your problem. Maybe it is something >> >>>> releated >> >>>> to the stacktrace. >> >>>> I am not aware of how NetBeans deals with surefire. I hope others on >> >>>> this >> >>>> list will provide help. >> >>>> Maybe adding a sample stacktrace may help >> >>>> >> >>>> Enrico >> >>>> -- >> >>>> >> >>>> >> >>>> -- Enrico Olivelli >> >>>> >> >>> >> > -- > > > -- Enrico Olivelli > -- -- Enrico Olivelli
Re: Surefire plugin issue
Thank you. To be honest I found the same problem inin the project I am working on. After re-looking the same output every day I failed to see the problem. Cheers Enrico Il mer 28 nov 2018, 16:07 Jean-Marc Borer ha scritto: > OK, so I found the issue in the code (it is actually broken) and fixed it. > Going to publish a PR soon. > > On Mon, Nov 26, 2018 at 4:52 PM Jean-Marc Borer wrote: > > > If you can't get the zip from the list, you can grab it from > > https://issues.apache.org/jira/browse/NETBEANS-635 > > > > On Mon, Nov 26, 2018 at 4:50 PM Jean-Marc Borer > wrote: > > > >> Ok I could reproduce it with very small sample project. Just clean and > >> build and you will see that there will be no stacktrace parsing... > >> > >> On Mon, Nov 26, 2018 at 4:43 PM Jean-Marc Borer > >> wrote: > >> > >>> Can you see the screenshot I attached my last message (the one with the > >>> XML)? > >>> > >>> On Mon, Nov 26, 2018 at 4:30 PM Enrico Olivelli > >>> wrote: > >>> > >>>> Jan-Marc, > >>>> I am sorry, I can't reproduce your problem. Maybe it is something > >>>> releated > >>>> to the stacktrace. > >>>> I am not aware of how NetBeans deals with surefire. I hope others on > >>>> this > >>>> list will provide help. > >>>> Maybe adding a sample stacktrace may help > >>>> > >>>> Enrico > >>>> -- > >>>> > >>>> > >>>> -- Enrico Olivelli > >>>> > >>> > -- -- Enrico Olivelli
Re: Surefire plugin issue
Jan-Marc, I am sorry, I can't reproduce your problem. Maybe it is something releated to the stacktrace. I am not aware of how NetBeans deals with surefire. I hope others on this list will provide help. Maybe adding a sample stacktrace may help Enrico -- -- Enrico Olivelli
Re: Surefire plugin issue
Jean-Marc Did you try latest surefire ? I have no problem with NB 9 + surefire Enrico Il lun 26 nov 2018, 13:42 Jean-Marc Borer ha scritto: > Hi all, > > Guys, we are planning to move away from Ant in favor of Maven. This will > only be possible if the Maven echosystem is properly supported. Currently, > surefire error logs are still broken since 2.19 as I described in > https://issues.apache.org/jira/browse/NETBEANS-635 > > For example with surefire 2.19.1: > > [image: image.png] > You can see that when I click on the link, an error message is displayed > in the status bar in the lower left corner. > > This was broken in NB 8.2 and still is in NB 9.0 > > Am I missing something here? > > Cheers, > > JMB > > -- -- Enrico Olivelli
Re: NetBeans - the UI for Maven
Martin, Il sab 24 nov 2018, 11:29 Martin Desruisseaux < martin.desruisse...@geomatys.com> ha scritto: > I think differently. In Apache SIS for example, we maintain both a Maven > and Ant project. The root source code directory is a classical Maven > project with pom.xml file [1], but we also maintain a sub-directory with > NetBeans Ant project configuration [2]. The official project > configuration is the Maven one, but the Ant project configuration is > keep in sync and takes its dependencies directly from the > ~/.m2/repository directory. This means that the project needs to be > built with Maven once before we can use the Ant project. We do that for > the following reasons: > > * NetBeans Ant project builds faster. > * Application and debugging sessions start faster in NetBeans Ant > project. This is very convenient when we do a lot of "modify - test" > cycles. > * Allow to commit configurations that can not be done in Maven (header > license, hints, additional words for check speller). > * NetBeans Ant Jigsaw project configuration offers better > compatibility with Jigsaw (more on it below). > > A major issue is that since Jigsaw, Maven standard directory layout is > incompatible with java, javac and javadoc "--module-path" option, which > is making me look for alternatives (Gradle?). I describe the issue at > [3]. I would like to try changes in maven-compiler, maven-javadoc, > maven-jar and maven-deploy plugins for supporting Jigsaw, but did not > had the time to start yet. As far as I can see, I can not modularize my > projects the way I want with Maven at it stands today. > > I also feel more concerned about Maven standard directory layout not > only because of its incompatibility with Jigsaw module paths, but also > because it does not seem well suited to project mixing two or more > languages. For example in the given directory layout: > > * src/main/java > * src/main/cpp > * src/main/resources > Have you already shared your thoughts and needs with Apache Maven group ? Cheers Enrico > Does the resources applies to Java, to C++ or both? > > So Maven is a great tool, but its speed is not yet the same than the > NetBeans Ant project configuration (admittedly it may be improved with > time) and - more importantly - I think that the Maven standard directory > layout needs to be modified at least for Jigsaw compatibility, maybe for > better multi-language support. > > Regards, > > Martin > > [1] https://github.com/apache/sis > [2] > https://github.com/apache/sis/tree/master/ide-project/NetBeans/nbproject > [3] https://github.com/Geomatys/maven-plugins/wiki > > -- -- Enrico Olivelli
Re: [VOTE] Release Apache NetBeans 9.0 RC1 (incubating) rc1
Hi, I have tested 9.0 rc1 with my a bunch of Java Maven projects, and minimally tested 'var' support with JKD10. +1 (non binding) I have filed this "annoying" issue which happens sporadically while working on a simple java file. I do not have a strict reproducer. https://issues.apache.org/jira/browse/NETBEANS-814 I don't know if it could be a blocker. I will follow up the issue on JIRA. Thank you very much for shipping this new greatest release of NetBeans ! Cheers Enrico Il giorno ven 18 mag 2018 alle ore 13:29 Geertjan Wielenga < geertjan.wiele...@googlemail.com> ha scritto: > Downloaded, unzipped, and ran the convenience binary. > > Everything works, installed nb-javac, tried out some of the new 'var' hint > refactorings. > > Only thing I've seen we need to do is change the splash screen but that > shouldn't block the rc1 release AFAIK. > > As with the other releases we've done so far, the main point of our > releases is to ensure that we pass the Apache requirements, i.e., the IPMC > vote will be interesting -- to see if there are still license problems, > binary problems, or whatever, everything identified so far has been fixed > and the main thing is to see whether the IPMC agrees. > > Many thanks Emilian for putting this release together, great to spread the > release management knowledge. > > +1 for releasing rc1. > > Thanks, > > Gj > > > On Thu, May 17, 2018 at 4:35 PM, Emilian Bold > wrote: > > > Hi all, > > > > Please vote on releasing Apache NetBeans 9.0 RC1 (incubating) rc1! > > > > If this voting passes, another similar voting will be started on > > gene...@incubator.apache.org, and if that passes too, then we can > release > > this version. > > > > Apache NetBeans 9.0 RC1 (incubating) constitutes all the modules in the > > Apache NetBeans Git repo, which together provide the NetBeans Platform > > (i.e., the underlying application framework), as well as all the modules > > that provide the Java SE-related features of Apache NetBeans. > > > > In short, Apache NetBeans 9.0 RC1 (incubating) is a full IDE for Java SE > > development. > > > > Build artifacts available here: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > incubating-netbeans-java/incubating-9.0-rc1-rc1 > > > > The specific artifact to be voted on: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > incubating-netbeans-java/incubating-9.0-rc1-rc1/ > > incubating-netbeans-java-9.0-rc1-source.zip > > > > Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and > > NOTICE files, as well as a README file with build instructions, which are > > the same as these: > > > > https://github.com/apache/incubator-netbeans/blob/master/README.md > > > > MD5: 75ac72983e074f159638a8da4cec6c8b > > SHA1: a1a265455c8246f849b14982fa3c36b351b21876 > > > > KEYS file: > > > > https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS > > > > Apache NetBeans Git Repo tag: 9.0-rc1-rc1: > > > > https://github.com/apache/incubator-netbeans/tree/9.0-rc1-rc1 > > > > Note: NetBeans license violation checks are managed via the > > rat-exclusions.txt file: > > > > https://github.com/apache/incubator-netbeans/blob/ > > master/nbbuild/rat-exclusions.txt > > > > Rat report shows no unknown licenses, except for license files: > > > > https://builds.apache.org/job/incubator-netbeans-release/ > > 302/artifact/rat-java-temp/nbbuild/build/rat-report.txt > > > > The license files listed in the Rat report are known and an issue exists > > for solving this: > > > > https://issues.apache.org/jira/browse/NETBEANS-305 > > > > Included as a convenience binary, not relevant for the voting purposes > > (unzip it, run it and you'll see Apache NetBeans): > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > incubating-netbeans-java/incubating-9.0-rc1-rc1/ > > incubating-netbeans-java-9.0-rc1-bin.zip > > > > Also included as a convenience binary the NBMs: > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/ > > incubating-netbeans-java/incubating-9.0-rc1-rc1/nbms > > > > New & Noteworthy features of the 9.0 Release: > > > > https://cwiki.apache.org/confluence/display/NETBEANS/ > > Apache+NetBeans+9.0+New+and+Noteworthy > > > > Release specific wiki page: > > > > https://cwiki.apache.org/confluence/display/NETBEANS/ > > Apache+NetBeans+9.0+RC1 > > > > How (and what) to try out the release: > > > > 1. Download the artifact to be voted on and unzip it. > > 2. Build it using the README provided by the artifact. > > 3. Look in nbbuild/netbeans for the NetBeans installation created by the > > build process. > > 4. Run the NetBeans executable and (if you're running on JDK 8) you'll be > > prompted to install nb-javac, after agreeing to its licensing terms, and > > (if you're running on JDK 9), you'll be able to use javac directly from > JDK > > 9 and, optionally, you'll be prompted to install nb-javac, after agreeing > > to its licensing terms. > > > > If the above succeeds, i.e., Apache Ne
Re: How/where exactly to host the NBMs for the 9.0 release
Do releases of NBM files follow usual Apache release flow? If they are artifacts 'released' by this Apache Project they could go to dist.apache.org and to Apache mirrors. Just my two cents Enrico Il gio 5 apr 2018, 14:50 Jiří Kovalský ha scritto: > I am afraid that VM hosting Synergy won't survive such a load > (~3TB/month) once we release 9.0 to public. > > -Jirka > > Dne 5.4.2018 v 14:38 Geertjan Wielenga napsal(a): > > > Hi all, > > > > We need to nail down this one and I think the key blocker is that there > are > > different ideas about what this is about: > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_NETBEANS-2D330&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=HkiKbmb7GeafxH447aOYZCa-BLZDc-ny5MEKc3uwowA&s=S5RtUWcQM-rPz2Hrjg-3o2iB9HQEuOdT1E2IZNSouVA&e= > > > > The above is not about the Plugin Portal. > > > > If I understand it correctly, this is about where the NBMs (which ones? > how > > many? do we know?) and the related XML file (a.k.a. update center) will > be > > hosted. > > > > AFAIK, the XML file and the NBMs could be put onto our Apache NetBeans VM > > just like Synergy: > > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__netbeans-2Dvm.apache.org_synergy&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=HkiKbmb7GeafxH447aOYZCa-BLZDc-ny5MEKc3uwowA&s=8qd68zoMwDb5S72suJJWvkF5QMPr7gbwqNpb-Na1VMI&e= > > > > The key question remains, which NBMs are we talking about here, > applicable > > to the 9.0 release, I think. > > > > Thanks, > > > > Gj > > > > - > 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 > > > > -- -- Enrico Olivelli
Re: [Gentoo Packaging] 9 9 9 :)
Very interesting work! One question...the splash screen displays the old license of NetBeans, is it still a packaging issue? Enrico Il sab 2 dic 2017, 10:03 Antonio ha scritto: > Congratulations! Good work! > > El 01/12/17 a las 03:42, William L. Thomson Jr. escribió: > > Netbeans 9, built under java 9, running on java 9 :) > > > > http://www.enlightenment.org/ss/e-5a20b8eb0b3e91.03603173.jpg > > http://www.enlightenment.org/ss/e-5a20b833eb1999.79359468.jpg > > http://www.enlightenment.org/ss/e-5a20b8017cd974.90970763.jpg > > http://www.enlightenment.org/ss/e-5a20bf75cc4179.53467093.jpg > > > > Still much more to do, no working editor yet, mime and some other > > issues, more to package. That NbBundleProcessor issue was a major light > > switch moment. All menus are fully populated now :) > > > > Darcula works when copied from my 8.2 user install. Trying to get the > > nbm to install. No public plugins are showing. I assume that is due to > > 9 not being released yet and/or transition to Apache. Not a huge deal. > > > > Off to the races now for the most part! > > > -- -- Enrico Olivelli
Re: How do we want to do merges?
Hi, in BookKeeper we have a script which deals with GitHub pull requests https://github.com/apache/bookkeeper/blob/master/dev/bk-merge-pr.py it creates tmp git branches, does squash merges and eventually pushes to apache, handle commit messages, handles github bug tracker + ASF JIRA bugtracker + does automatic QA checks we originally take the idea from other Apache Projects feel free to use and example Cheers Enrico 2017-09-27 15:07 GMT+02:00 Eric Barboni : > Hi, > Idea from other Apache project > > https://cwiki.apache.org/confluence/display/ROLLER/How+ > to+accept+a+GitHub+Pull+Request > > If contribution is not important a icla is not required. > > Only commiter can merge pr > > Regards > > Eric > -Message d'origine- > De : Geertjan Wielenga [mailto:geertjan.wiele...@googlemail.com] > Envoyé : mercredi 27 septembre 2017 10:26 > À : dev@netbeans.incubator.apache.org > Objet : How do we want to do merges? > > Hi all, > > Bear in mind that Apache GitHub is a readonly mirror of Apache Git. > > So, the question is, how do we want to do merges of PRs and also what > should the workflow be. These are decisions we can make as a community. > > For example, this PR by Eric Barboni, seems a logical one to want to > merge, i.e., its an addition to our Rat setup that we logically would want > to have, i.e., there's no reason not to have it and everyone in the PR > agrees with it: > > https://github.com/apache/incubator-netbeans/pull/12 > > If the person providing a PR is a committer, after there is agreement on > the PR, the committer could then push that PR to the Apache Git repo > themselves, for example. > > Thoughts welcome. > > Gj > >
Re: AW: Github issue tracker or Jira?
Hi, I have been an enthusiast NetBeans use since version 3, if possible I would like to help, expecially now that NB is under Apache I expect that it will be easier to contribute. I am a committer in another Apache Project, BookKeeper. We recently did an important switch to GitBox, that is a great integration between ASF infra and Github. The main point is that in this mode the github repo becomes the master repo, source of truth. Each committer links his own apache id with the github personal id and this gives full write access to committers to the github repo. We are switching from ASF jira to github issue tracker as well. This is going very well and it is easier for users to have a github account than having an ASF Jira account Hope that helps Enrico Olivelli eolive...@apache.org On mer 13 set 2017, 17:54 Daniel Gruno wrote: > On 09/13/2017 05:46 PM, Christian Lenz wrote: > > I think so too, but maybe there is a jira or github plugin, where it > will get or post the new ticket, only description and title and with > githubuser-bla or smth like that. > > > > Gesendet von Mail für Windows 10 > > > > Von: Bertrand Delacretaz > > Gesendet: Mittwoch, 13. September 2017 16:56 > > An: dev@netbeans.incubator.apache.org > > Betreff: Re: Github issue tracker or Jira? > > > > On Wed, Sep 13, 2017 at 6:06 AM, Daniel Gruno > wrote: > >> ...Most, if not all Apache projects with both JIRA and GitHub have > >> mirroring enabled. Trivial to activate :)... > > > > Mirroring of issue tracker tickets you mean? > > > > Can you provide examples? I'm curious, as there are many differences > > between the underlying ticket models. > > > > -Bertrand > > > > > > Normally you would make a JIRA ticket first, let's say the ticket is > NETBEANS-1234, and on GitHub you call your tickets something like > "NETBEANS-1234: Some problem here", which in turn means that everything > that happens in that ticket on github gets reflected in JIRA. > -- -- Enrico Olivelli
