Skip to content

Labsus insider

Ubbo Veentjer requested to merge labsus-insider into master

this branch mainly includes the labsus repo which is our old nexus repo which had the dependencies required to build tglab or tglab extensions. hopefully the new nexues repo will include this artifacts soon, but for the tiome given its labsus.

further this branch removes some stuff which is not needed given the labsus repo is available.

one thing i am unsure of is the teiparser.core/META-INF/MANIFEST.MFfile. there are two possible ways to solve the osgi dependency hell, one is to use Import-Package which seems to be the better way to do this. This may cause trouble however, so here is how the MANIFEST.MF can also be written:

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: teiparser Core Plugin
Bundle-SymbolicName: teiparser.core;singleton:=true
Bundle-Version: 0.0.1.qualifier
Bundle-Activator: org.classicmayan.tglab.teiparser.core.Activator
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Automatic-Module-Name: teiparser.core
Require-Bundle: info.textgrid.lab.ui.core,
 org.eclipse.ui.workbench,
 info.textgrid.lab.core.model,
 org.eclipse.core.jobs,
 org.eclipse.core.commands,
 org.eclipse.osgi,
 org.eclipse.core.runtime,
 org.eclipse.jface,
 org.apache.cxf.bundle,
 org.apache.servicemix.specs.jsr311-api-1.1.1,
 org.codehaus.jettison.jettison

just in case of strange osgi problems regarding to split package or wtf. i think actually most of the lab uses Require-Bundle statements, so don't hesitate to also use this in case of trouble ;-)

Edited by Ubbo Veentjer

Merge request reports

Loading