(Add javadoc section) |
No edit summary |
||
| Line 23: | Line 23: | ||
And additionally, Eclipse plug-in binary packages or their dependencies '''MUST''' have Requires (generated by RPM or manual) on: | And additionally, Eclipse plug-in binary packages or their dependencies '''MUST''' have Requires (generated by RPM or manual) on: | ||
* <code>eclipse-filesystem</code> | * <code>eclipse-filesystem</code> | ||
== Javadocs == | == Javadocs == | ||
Revision as of 14:07, 6 May 2016
Introduction
This page contains Fedora guidelines for packaging Eclipse plug-ins. Since Eclipse plug-ins are also Java packages, this page extends (and where necessary, overrides) the guidelines laid out in the Fedora Packaging Guidelines for Java. If you are not familiar with Java packaging in Fedora, please read the Java guidelines before continuing.
Package Naming
Packages MUST follow the standard Fedora package naming guidelines for add-on packages.
BuildRequires and Requires
Eclipse plug-ins in Fedora are always built with Maven/Tycho, so they MUST BuildRequire it:
BuildRequires: tycho
And optionally, for plug-ins that make advanced use of Tycho:
BuildRequires: tycho-extras
Since Eclipse plug-in packages are also Java packages, the binary packages or their dependencies MUST have Requires (generated by RPM or manual) on:
java-headlessorjava-headless >= 1:minimal_required_versionjavapackages-tools
And additionally, Eclipse plug-in binary packages or their dependencies MUST have Requires (generated by RPM or manual) on:
eclipse-filesystem
Javadocs
Since Eclipse plug-ins provide their documentation through the Eclipse help system they SHOULD NOT have a javadoc sub-package. The normal javadoc generation can be disabled by passing an extra parameter to the Maven build command:
%mvn_build -j