I written a Java free software (closed source) product which I deploy on the hosting company and distribute via JNLP, inclusive Linux clients.
I intend to suggest the product for inclusion into several Linux distro, if at all possible "out of the box" (JNLP-based).
Can One already contact distros, or I have to reconfigure something (deploy on another host, convert JNLP to something, etc.)? What's your experience?
Generally Linux distros aren't very thinking about things they cannot integrate to their release agendas. Since JNLP enables you to definitely deploy a brand new version anytime, they cannot perform a version freeze before release. This can exclude you against most distros - Debian even removed Adobe's expensive wordpress plugin with this very reason, and when they'll remove Expensive, pricier these to make exceptions for any less well-known application.
If you are prepared to distribute it as being only a plain .jar, you may have the ability to have it in - for debian, you will want to browse the Debian New Maintainer's Guide and Debian Policy regarding how to package things, submit an ITP (intent to package), upload a package, then seek sponsorship around the debian-mentors subscriber list. More information are available in the Debian mentors FAQ. Packages posted to Debian will even make their distance to Ubuntu in the end.
Other distributions may have different guidelines, obviously if uncertain, check their frequently asked questions, or request with an appropriate subscriber list for that distro under consideration.
I'd state that a free software JNLP application is virtually the alternative of the items Linux distributions would often include.
First of all, JNLP won't use the native package management solution. Should you desired to have an application incorporated inside a distribution it will have to be package within the native format and up-to-date within the standard way.
Next, most distributions will favour free packages and several won't include non free packages within their default databases. Some distributions might have specical non-free databases. Up to OpenJDK you might not even Java itself could be during these databases.
For me you'd be better attempting to develop a users list by yourself while you then have total treatments for releases etc.
Discover a method to package it correctly on each one of the platforms you need to incorporate your software on, and get ready for rigid software management (freezing, multiple versions etc if you would like the code incorporated within the standard installation.
Or else you may have the ability to produce a simple package just that contains the hyperlink towards the JNLP page which might be incorporated within the non-core parts. It's worth an attempt.
What applcation shall we be speaking about?
Java programs are usually tough to package and keep. Therefore recommendations change from distro to distro. Which means you should take a look in the specific recommendations for many popular distros first.
Additionally to that particular: Exactly what updates itself individually in the package manager could be real discomfort for that user and maintainer from the package so you should look at another distribution model for inclusion in linux distros.