KnowledgeBase
|
Size: 762
Comment:
|
← Revision 12 as of 2011-11-09 16:07:46 ⇥
Size: 1482
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(JavaTeam/Header)]] | <<Include(JavaTeam/Header)>> |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 7: | Line 7: |
| Check out the [http://www.debian.org/doc/packaging-manuals/java-policy/ Debian Java Policy]. | Check out the [[http://www.debian.org/doc/packaging-manuals/java-policy/|Debian Java Policy]]. Follow the [[JavaTeam/KnowledgeBase/Packaging|packaging for Java developers guide]] == What exactly is already packaged somewhere ? == With Java it's sometimes difficult to know if some classes are not already shipped somewhere as part of a given package. JavaTeam/JavaContents addresses that by providing java-Contents.gz files containing a map of packages / jar / classes shipped in a given release. == Building == Many Java packages require that the build^dependencies are installed in order to build a source package. If you work with many different Java packages with different or conflicting build-dependencies, you may want to build your source packages in a snapshot chroot. The buildds have a debconf setting to automatically accept the Sun Java licenses, to allow autobuilding of packages. The following command will replicate this configuration for your build chroots: {{{ echo "buildd shared/accepted-sun-dlj-v1-1 boolean true" | debconf-set-selections }}} |
| Line 10: | Line 27: |
| Check out the [:PackagingGuide/Lists/ReferencePackages#Java:Java Reference Packages]. = Plans = == What are your plans for the release? == Refer to our [:JavaTeam/Roadmap:Roadmap] and find out more. == What have you been working on up until now? == Check out our [:JavaTeam/Roadmap:Roadmap] and our [:JavaTeam/TeamReport:team report]. |
Check out the [[PackagingGuide/Lists/ReferencePackages#Java|Java Reference Packages]]. |
Next Meeting: Thu July 16th 9:00 UTC |
Packaging
How is Java Packaging different?
Check out the Debian Java Policy.
Follow the packaging for Java developers guide
What exactly is already packaged somewhere ?
With Java it's sometimes difficult to know if some classes are not already shipped somewhere as part of a given package. JavaTeam/JavaContents addresses that by providing java-Contents.gz files containing a map of packages / jar / classes shipped in a given release.
Building
Many Java packages require that the build^dependencies are installed in order to build a source package. If you work with many different Java packages with different or conflicting build-dependencies, you may want to build your source packages in a snapshot chroot.
The buildds have a debconf setting to automatically accept the Sun Java licenses, to allow autobuilding of packages. The following command will replicate this configuration for your build chroots:
echo "buildd shared/accepted-sun-dlj-v1-1 boolean true" | debconf-set-selections
Are there any packaging examples?
Check out the Java Reference Packages.
JavaTeam/KnowledgeBase (last edited 2011-11-09 16:07:46 by james-page)