Common Java Packaging
Goals
Implementing a common set of policies and helper tools to ease the task of packaging java application and making it as fail-safe as our users would expect it. Provide the user with one easy and well structured way to handle java related configurations and issues.
Tools
This open wiki and a mailing list at https://www.zarb.org/mailman/listinfo/cojapas
Solutions
So, to finally get something done here, we will add a page, where we list the requirements and if someone has already a working solution for it. In the end we hopefully have something to base a descision on.
- A tool for every runtime problem.
- Where do the config files go, where the Jars and how they are named.
- What information is needed to manipulate classpaths automatically.
- Shuns all the others. Wants to be useful at build and design time and on other Operating Systems and platforms.
Discussion
Please describe your current way, how you handle such things as
- dealing with CLASSPATH issues choosing different JVM, including Sun derived and free ones building java packages
Distributions
[[What_is_required_from_upstream]]
Upstream developpers have little or no idea of what must be done to make their project easy to package. They need clear guidelines or they will continue to produce software that is very difficult to package.
Problems and discussed Solutions
The idea is to figure out some problems with current packaging. The page should also hold the discussion about what needs to be done to find a common solution, which is acceptable for each group. I've also included a page about requirements from each group.
- What some groups absolutely can't change or must have
- This topic is discussed in two pages. It seems to me that a solution is only possible when both are combined into one and one script is used to figure out both the classpath based on a chosen JVM. I will try to add one page for a solution, based on my understanding of the situation and the needs of Gentoo, the [JPackage Project] and Debian. Please comment on it and change parts you want changed. --jasc
CombinedClasspathAndRuntimeSolution
- Page to list a solution for both topics. Below are the pages where the main discussion has taken place.
- Building the classpath for each application.
- Find out what runtime a package can use and how to manage that.
- How to build java packages from source.
- What's available in the different package managers and whatnot.
- Some notes regarding a common naming scheme.
- Standardizing the uids used by java daemon users.
http://people.redhat.com/dgregor/rollin.html
- Some thoughts on the Java packaging/runtime problems from the Red Hat CCM folks.
- Tools, thoughts and tweaks for testing and QA.
Archives of previous communication attempts
JPackage_Project and JanSchulz, november 2003 :
http://lists.zarb.org/pipermail/jpackage-discuss/2003-November/003345.html http://lists.zarb.org/pipermail/jpackage-discuss/2003-November/003414.html
- plus probably other threads at about the same time on this list
Debian, august/september 2003
- Discussion about a new Debian Java policy
Start: http://lists.debian.org/debian-java/2003/debian-java-200308/msg00158.html Main part and result in september: http://lists.debian.org/debian-java/2003/debian-java-200309/threads.html
