Popular Java Applications Repository

[thevpc]

I think it makes sense to have a special Popular Java Applications Repository that supports popular java applications that are not "installable" as simple jars and dependencies. One idea is to add a new extension project (next-pjar) that adds this repository upon installation.

This repository would support installation of multiple versions of:

• For developers
  • jedit
  • netbeans
  • eclipse
  • intellijidea (community)
  • maven
  • gradle
  • java decompiler (jd-gui)
• For developers / ops
  • wildfly
  • tomcat
  • jetty
  • derby
  • jmeter
  • jenkins
  • visualvm
• For education
  • bluej
• For productivity
  • jarnal
  • JDiskReport

What is our opinions on this? Are there any other "popular" java apps out there?

[bacali95]

Hello, I didn't get the purpose of the repository, can you please explain more?

[thevpc]

Now that we are fixing the latest issues in the 0.8.3, and I am hoping we can wrap this up in the very few days, I was thinking of the "suite" and the lead to the next versions.
And I was wondering how to make of nuts the supplier for every java application.

How to be able to do that:

nuts install netbeans

So, how to make every person think that any java application is available in nuts.

To take the example of netbeans installation, or any other popular java application, it is not mere jars with dependencies. It doesn't even have it's jars on maven central or equivalent. Installation passes through downloading from raw links as zip/tarball at best. And the links, most of the time, are not static.

Of course, we can ask netbeans team (and other apps) to re-package netbeans as a maven-central jar, however, you know, they wont be very attentive!

I have encountered the very same issue with maven (nmvn), tomcat (ntomcat) and derby (ndb). Basically I implemented a Repository for each of these application (as far as i can remember, at least, this was the way to do it). As an example you can take a look at ApacheTomcatRepositoryModel.java.

But, is it logical to create a Repository for each application. Should we (or should we not) create one Repository for all the leading apps. After all, there is not so much of them to support :)

I like to think of it like EPEL package of CentOS (Extra Packages for Enterprise Linux : EPEL) that should bundle extra popular apps.

To finish, I'm not saying we should do It, I'm just pointing out this question from the top of my head.

[bacali95]

Now I got it, I think it is a nice to have feature and quite useful. If we decide to have it it will be better if we have one repository for all the popular apps instead of having a repo for each one. what do you think?