Issue with latest jdk 11 on Linux and work around solution

Hi I recently upgraded my java on ubuntu and on startup I get this error java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper at java.desktop/java.awt.Toolkit.newAWTError(Toolkit.java:472) at

RE: NB 9 Platform Maven arifacts

Ah--thank you! -- Eirik -Original Message- From: Geertjan Wielenga Sent: Thursday, August 23, 2018 7:43 AM To: dev Subject: Re: NB 9 Platform Maven arifacts This thread could help:

Re: [DISCUSS] NetBeans brand and domain transition to Apache

On Thu, Aug 23, 2018 at 5:10 AM, Bertrand Delacretaz wrote: > Yes - I think the only requirement at this point is that the > *ownership* of the domains is transferred to Apache, moving the > content is a separate concern. > Is it even possible for the Apache foundation to distribute older

Re: Failing builds

Yes, a few people have commented on this, not all tests -- probably not from all clusters are included yet -- are included right now. Something to look at, if someone knows how/where, this is something else to sort out. Gj On Thu, Aug 23, 2018 at 7:11 PM, Kai Uwe Pel wrote: > Christian is

Re: Failing builds

Christian is right, some are still missed... Kai On 8/23/2018 6:49 PM, Christian Bourque wrote: Yes I know that and that isn't what I meant! If you look at the module list under "All Tests", you'll see that some are missing! On Thu, Aug 23, 2018 at 11:53 AM, Geertjan Wielenga <

Re: Failing builds

Yes I know that and that isn't what I meant! If you look at the module list under "All Tests", you'll see that some are missing! On Thu, Aug 23, 2018 at 11:53 AM, Geertjan Wielenga < geertjan.wiele...@googlemail.com.invalid> wrote: > Yes, its yellow, meaning tests fail, however its not red,

Re: Failing builds

:) the second one also succeeded *Kind regards, * *Thilina Ranathunga.* On Thu, Aug 23, 2018 at 9:23 PM Geertjan Wielenga wrote: > Yes, its yellow, meaning tests fail, however its not red, which means > everything except the tests are passing: > >

Re: Failing builds

Yes, its yellow, meaning tests fail, however its not red, which means everything except the tests are passing: https://builds.apache.org/job/incubator-netbeans-linux/ Gj On Thu, Aug 23, 2018 at 5:47 PM, Christian Bourque < christian.bour...@gmail.com> wrote: > Great news! > > Though it seems

Re: Failing builds

Great news! Though it seems that not all tests are executed on Jenkins? Like I'm currently working on the NetBeans JGit module (libs.git) and some tests are failing when I run them locally so I would expect them to fail on Jenkins as well! C. On Thu, Aug 23, 2018 at 10:59 AM, Geertjan

Re: Failing builds

Perfect! On Thu, 23 Aug 2018 at 16:13, Thilina Ranathunga wrote: >  > > On Thu, Aug 23, 2018, 8:29 PM Geertjan Wielenga > wrote: > > > Hurray, the build succeeds, thanks all. > > > > Gj > > > > On Thursday, August 23, 2018, Geertjan Wielenga < > > geertjan.wiele...@googlemail.com> wrote: > >

Re: Failing builds

 On Thu, Aug 23, 2018, 8:29 PM Geertjan Wielenga wrote: > Hurray, the build succeeds, thanks all. > > Gj > > On Thursday, August 23, 2018, Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > > Great, thanks for doing this, really looking forward to the build > > succeeding

Re: NetBeans javadoc at Apache

One idea for whoever takes this on is we could link from our website to https://www.javadoc.io/ when we start creating maven artefacts, and we just have to deploy the javadocs to https://search.maven.org/ Regards John On Thu, 23 Aug 2018 at 13:30, Geertjan Wielenga wrote: > Does someone want

Re: org.netbeans name prefix for artifacts and Java packages (was: [DISCUSS] NetBeans brand and domain transition to Apache)

On Thu, Aug 23, 2018 at 3:41 PM Andreas Sewe wrote: > ...If you switch just the groupId from org.netbeans to > org.apache.netbeans (but leave artifactIds and package names intact), > then this is relatively painless, thanks to so-called relocation POMs [1] Yes, and that's something that

Re: org.netbeans name prefix for artifacts and Java packages (was: [DISCUSS] NetBeans brand and domain transition to Apache)

Hi, > We've discussed it before, will try to track it down -- I think there'd be > various problems if we switch the names of Maven artifacts to > org.apache.netbeans, though correct me if I'm wrong or add additional > points here related to this, anyone who has insights here. just a pointer: If

Re: org.netbeans name prefix for artifacts and Java packages (was: [DISCUSS] NetBeans brand and domain transition to Apache)

23. srpna 2018 13:37:23 SELČ, Bertrand Delacretaz napsal: >Hi, > >On Thu, Aug 23, 2018 at 1:01 PM Geertjan Wielenga > wrote: >> ...A related knock-on effect is that org.netbeans will be available >for Apache >> NetBeans Maven archetypes, since the netbeans.org domain will belong >to >>

Re: [DISCUSS] NetBeans brand and domain transition to Apache

On Thu, Aug 23, 2018 at 1:46 PM Neil C Smith wrote: > ...The DNS settings > could still point back to Oracle hosting for all, then select, > subdomains Yes - I think the only requirement at this point is that the *ownership* of the domains is transferred to Apache, moving the content is a

Re: org.netbeans name prefix for artifacts and Java packages (was: [DISCUSS] NetBeans brand and domain transition to Apache)

Yes, thanks for flagging this topic. We've discussed it before, will try to track it down -- I think there'd be various problems if we switch the names of Maven artifacts to org.apache.netbeans, though correct me if I'm wrong or add additional points here related to this, anyone who has insights

Re: Failing builds

Great, thanks for doing this, really looking forward to the build succeeding again. :-) Gj On Thu, Aug 23, 2018 at 1:32 PM, Svata Dedic wrote: > Hi, > > I am trying already to fix path issues from the recent cluster moves. PR > will be filed soon. > > @Thilina: thanks, will include that one. >

Re: [DISCUSS] NetBeans brand and domain transition to Apache

> On Thu, Aug 23, 2018 at 1:01 PM, Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > To add to the fun, we're getting really close now to actually > > transitioning the NetBeans brand and domains to Apache. For everyone else, there was a very brief off-list discussion on this

Re: NB 9 Platform Maven arifacts

This thread could help: https://lists.apache.org/thread.html/3b4ef9f4e14f614e65b4144e02ef228fcda693ace1de2752a338885d@%3Cdev.netbeans.apache.org%3E Gj On Thu, Aug 23, 2018 at 9:24 AM, Luff,Chris wrote: > You can use the nb-repository-plugin to build the maven artifacts for your > local repo

org.netbeans name prefix for artifacts and Java packages (was: [DISCUSS] NetBeans brand and domain transition to Apache)

Hi, On Thu, Aug 23, 2018 at 1:01 PM Geertjan Wielenga wrote: > ...A related knock-on effect is that org.netbeans will be available for Apache > NetBeans Maven archetypes, since the netbeans.org domain will belong to > Apache... I suppose you mean Maven *artifacts*. Note that AFAIK NetBeans

Re: Failing builds

By searching for any occurrences of all 92 modules in platform cluster one by one in rat-exclusions.txt noticed in line 78 openide.nodes/test/unit/src/org/openide/nodes/data/** the module openide.nodes is a part of platform cluster and has been moved to the platform/ folder. so the path should

[DISCUSS] NetBeans brand and domain transition to Apache

Hi all, To add to the fun, we're getting really close now to actually transitioning the NetBeans brand and domains to Apache. I.e., netbeans.org and several other domains are in process of being donated to Apache. We have the go ahead from Apache VP to open an INFRA ticket for the transfer of

Re: Failing builds

If this is the problem in the Linux build, then I believe the problem comes from here: https://github.com/apache/incubator-netbeans/pull/732 BUILD FAILED > /home/jenkins/jenkins-slave/workspace/incubator-netbeans- > linux/nbbuild/build.xml:203: > The following error occurred while executing this

Re: License for .form files

Thanks, great question, keep them coming, when in doubt send questions just like these. The .form files that are currently not licensed to Apache are not many, they have escaped the automation tools we’ve created for this purpose. They need to be relicensed manually, same for the .mf files, I

License for .form files

Hi Everyone, I have noticed that there are multiple ".form" and "manifest.mf" files across multiple modules and all of these files are without licenses. Also, it is mentioned here that these files come under

Re: Failing builds

Great, thanks for these investigations. I will also take a look -- any further details welcome. Gj On Thu, Aug 23, 2018 at 8:56 AM, John McDonnell wrote: > Morning, > > So the windows build is still red, but it seems it goes all the way to the > RAT step and then fails. > > At the moment the

Re: NB 9 Platform Maven arifacts

You can use the nb-repository-plugin to build the maven artifacts for your local repo at the correct version from a netbeans source. Associate Principal Software Engineer | IP Development - Care Insight and Delivery Dev | chris.l...@cerner.com | Cerner

Re: Failing builds

Morning, So the windows build is still red, but it seems it goes all the way to the RAT step and then fails. At the moment the windows build runs the following ant targets: 'build', 'test-platform', 'rat', while the Linux build runs: 'build', 'test-platform', 'rat', 'verify-libs-and-licenses',