KIELER Project


Get me back to the home page!

Page tree

Versions Compared

Old Version 10

changes.mady.by.user Malte Kruse

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Stange

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Tab Overview
    • ID: start with de.cau.cs.kieler as prefix, except for plugins that contain third-party code
    • Version: 0.1.0.qualifier, increase with each release according to changes in the plugin
    • Name: start with KIELER, e.g. KIELER Core UI
    • Provider: Christian-Albrechts-Universität zu Kiel Kiel University
    • Check Activate this plug-in when one of its classes is loaded and This plug-in is a singleton, except if you know what you're doing
    • Execution Environment: JavaSE-1.8.0
    • Activator: Set the name of your Activator class (this represents the entry point of you plug-in). By default it is named "Activator.java". Rename this class to <Name>Plugin.java (e.g. CorePlugin.java).
  • Tab Dependencies
    • For Eclipse plugins: set your current version with 0 as third digit for Minimum Version, e.g. org.eclipse.core.runtime (3.5.0)
    • For our own plugins: if you know that you really need a specific version of the plugin, do the same as for Eclipse plugins, else leave the minimum version empty
    • Don't reexport dependencies, except in one case: UI plug-ins may reexport their dependencies on plug-ins that are part of the same project. (de.cau.cs.kieler.kiml.ui could reexport a dependency on de.cau.cs.kieler.kiml)
    • Collect all KIELER internal dependencies on the bottom of the list to increase readability.
  • Tab Runtime
    • Add all Java packages that must be visible for other plugins, e.g. if they contain classes or interfaces that must be referenced elsewhere
  • Tab Extensions
    • Add extensions to other extension points as needed
  • Tab Build
    • Binary Build
      • Include epl-v10.html (copy into plugin from one of the other plugins)
      • Include META-INF folder, plugin.xml and plugin.properties if present
      • Do not include src or bin folder
      • Include all icons, models etc. that are in your plugin
    • Source Build
      • Include epl-v10.html (copy into plugin from one of the other plugins)
      • Do not include src or bin folder
      • Include files that you explicitly want to be present in the source project

...