Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #302929 +++ Document the new buckminster.convert.source property that is used for adding the Manifest header that Eclipse needs to connect the source bundle to the binary bundle.
Added the following to the headless buckminster command reference: <term> <literal>org.eclipse.buckminster.convert.source</literal> </term><listitem> <para>When this boolean is set to true, the materializer will enforce that a downloaded source bundle is an <acronym>OSGi</acronym> bundle and that it has '<literal>Eclipse-SourceBundle</literal>' set in its manifest. Non compliant source jars are converted. This opion is false by default as the result is that doqnloaded source jars are modified. Setting this flag to true is useful with (the typical) source jars found at Maven.</para> </listitem> <term> <literal>org.eclipse.buckminster.download.source</literal> </term><listitem> <para>A boolean indicating if acompanying source bundles should be downloaded when downloading binary bundles. Default <literal>true</literal>. Also see <literal>org.eclipse.buckminster.convert.source</literal></para> </listitem> (list on p.211 in rev 0.8) And the following added to the "p2 materializer" on p.102 <title>Materializing from non p2 repositories</title><para>If the p2 materializer is given a <acronym>URI</acronym> that is not a reference to a p2 repository, the <acronym>URI</acronym> is handed to the given reader type — see <link linkend="rmap.sect.readerType"/> for more information about reader types. This allows the p2 materializer functionality to be combined with readers such as the maven reader. Also see <link linkend="command-buckminster-preferences"/> for information about preferences that controls download of source bundles.</para>
