Ebuilds Notes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* OSGi Manifests: if you have a header spanning several lines, it is *imperative* that you start newlines with a space!! Else this is considered to be another header. | * OSGi Manifests: if you have a header spanning several lines, it is *imperative* that you start newlines with a space!! Else this is considered to be another header. | ||
* Eclipse imperatively expects the Ant jar to be "exploded", eg in folder form. So we must keep a org.apache.ant folder with inside a manifest and a lib dir. We will symlink to the system jars in lib/. Keep the manifest bundle classpath up-to-date with the actual symlinks, else errors appear on the log (Eclipse tries to find jars that are not present). | |||
Revision as of 12:38, 16 October 2007
Eclipse 3.3
- The Ant script creates a .tar.gz file at the end. We need to unpack it to perform further modifications.
- To create this .tar.gz, stuff is copied from the build directory. We need to remove this copying in the main build.xml file, as we will later create the symlinks to our system jars.
- The Javadoc is ran by the build file buildDoc.xml in plugins/org.eclipse.platform.doc.isv. You could disable it here, or if you want to produce the javadoc, you need to add some classpath entries. Note that the warnings about multiple sources for comments is an upstream problem.
- OSGi Manifests: if you have a header spanning several lines, it is *imperative* that you start newlines with a space!! Else this is considered to be another header.
- Eclipse imperatively expects the Ant jar to be "exploded", eg in folder form. So we must keep a org.apache.ant folder with inside a manifest and a lib dir. We will symlink to the system jars in lib/. Keep the manifest bundle classpath up-to-date with the actual symlinks, else errors appear on the log (Eclipse tries to find jars that are not present).