Page MenuHomeSolus

Netbeans IDE
Open, LowPublic


Software Name : Netbeans IDE

Product Homepage :

Why you should include this into the repository : Netbeans IDE is a very popular IDE for both academic and professional Java programming.

Open Source : Yes

Open Source Link :

Related Objects

SamTemp created this task.Sep 25 2017, 4:02 PM

I am waiting for this to be added!

I would be really happy to see this package in the repo.

Wompo added a subscriber: Wompo.Apr 27 2018, 1:05 PM

Would also like to see this in the repo.

Is this even still developed? 8.2 is looking crusty

@DataDrake it was moved to Apache Incubator and it seems version 9.0 should be coming soon:
Git repo:

For the UI it only partially integrates with system theme so yeah it's not a beauty.

With it being moved to the Apache Incubator, this actually gives me far more confidence in its continued development. Unless @DataDrake disagrees, I think it'd be reason to move to Awaiting Package Upgrades pending the release of 9.0.

DataDrake triaged this task as Low priority.

I concur.

mati865 added a comment.EditedJul 29 2018, 7:54 PM

FYI Netbeans 9.0 has been released just today:

What is the current status of NetBeans for Solus OS, any prediction?

livingsilver94 added a subscriber: livingsilver94.

Let's give it a try.

@livingsilver94 I think you have to add ant to the repo too. Link:

@maverick1 already there under the name apache-ant.

@livingsilver94 Sorry my bad. I am glad that you step up as a maintainer.

Technically, I didn't. I'm just trying at the moment :)

Ok, we need to decide what/if to split netbeans in multiple packages. These are the bundles:
What do we want? Only the default (release) cluster? Only Java? Maybe we should build everything and immediately split it via ypkg?

I think i'd just build everything unless there's other packaging using only some parts of it. Otherwise I really don't see a reason to split it up.

size and/or runtime dependencies might be reasons for splitting this.

That's a good point but I don't think it makes sense to split packages which are, and will, only be needed by one single application.
If it's being used by multiple other packages, sure, it makes sense. Otherwise I don't really see a reason to.

I have this packaged but I would really like a regular user of netbeans to test and a long-time maintainer or tester to step foward. Additionally, there is some small annoyances with the packaging including windows, mac, arm jni libs which I have to filter out and remove.

There is some small annoyances with the packaging including windows, mac, arm jni libs which I have to filter out and remove.

Have a look at Fedora's patches for that.

Have a look at Fedora's patches for that.

Unless i'm blind they seem to be still shipping netbeans 7.0, I rebased a couple of their patches but I didn't seem to make a difference to what libs were copied.

I know they ship an old version, and I was actually counting on rebasing the patches. Nevermind then.

livingsilver94 removed livingsilver94 as the assignee of this task.Nov 18 2018, 11:12 AM

It's too demanding to package it. I'm quite busy in this period of time.

I have a working package for this, however, it requires JDK 9 or later without downloading their bundled Java. Several system packages still require openjdk 8 as we have packaged but we have no way to provide multiple java versions currently, see T6658.