debian::javahelper::eclipse(3) [debian man page]
Debian::Javahelper::Eclipse(3) Javahelper Debian::Javahelper::Eclipse(3) NAME
Debian::Javahelper::Eclipse - Eclipse Helper Library. SYNOPSIS
use Debian::Javahelper::Eclipse; my @orbitdeps = (); push(@orbitdeps, { EOB_SYM_NAME => 'org.apache.commons.net', EOB_SYS_JAR => '/usr/share/java/commons-net2.jar'}); #... # Install the feature to "$dropins/$name" install_zipped_feature($zip, "$dropins/$name"); # and symlink the following orbitdeps. install_zipped_feature($zip, "$dropins/$name", @orbitdeps); DESCRIPTION
This module is used by the eclipse related javahelpers to share common code. Please note this API is not stable and backwards compatibility is not guaranteed at the current time. Please contact the maintainers if you are interested in a stable API. Definitions A bundle refers to a jar file. An orbit dependency (a.k.a orbitdep) is a bundle, which is used by eclipse or one of its features without being a part of eclipse or said feature. This module keeps track of bundles via hashes; see the EOB_* constants for relevant keys (and their expected values). Constants EOB_SYM_NAME Key for hashes to fetch the symbolic name of a bundle. EOB_BUNDLE_VERSION Key for hashes to fetch the version of a bundle. EOB_SYS_JAR Key for hashes to fetch the path to the system installed jar file. Only valid for an orbit dependency and cannot be used with manifests. Methods install_zipped_feature($fzip, $loc[, $orbitdeps[, $package, $needs]]) Unpacks the zipped feature $fzip into $loc, which should be a subfolder of a dropins folder (e.g. /usr/share/eclipse/dropins/emf). This can also be used to install the feature into a "build environment". In this case it should be installed into the same folder as the SDK is (this folder is usually called "SDK"). If $orbitdeps is present, it should be an ARRAY ref containing orbit dependencies, which will be symlinked after unpacking. This sub only needs the EOB_SYM_NAME and EOB_SYS_JAR to be set and valid. Orbit dependencies not present in the installed folder will be ignored, so it is safe to have unrelated orbit dependencies in the ARRAY ref. If $package and $needs are present, the former should be the name of a debian package and the latter a hashref. The sub will populate the $needs hashref with which orbit dependencies are used by the package. The $needs hashref can be re-used in multiple calls to this sub. Keys in $needs will be the path to the orbit jar's real location (EOB_SYS_JAR) and the value a new hashref. This hashref has as keys the names of packages and as values 1. The $needs is used by jh_installeclipse to populate the ${orbit:Depends} variables for packages. AUTHOR
Niels Thykier <niels@thykier.net> COPYRIGHT AND LICENSE
Copyright 2010 by Niels Thykier This module is free software; you may redistribute it and/or modify it under the terms of GNU GPL 2. 0.43 2011-02-17 Debian::Javahelper::Eclipse(3)
Check Out this Related Man Page
MAVEN(1) User Commands MAVEN(1) NAME
Maven - Installs a jar into /usr/share/maven-repo. SYNOPSIS
mh_installjar [option]... [pom] [jar] [link]... DESCRIPTION
Installs the jar file in /usr/share/maven-repo, at the correct location for Maven. The jar is copied into the build directory. It can also create additional links to the jar, usually located in /usr/share/java. Where [pom] is the location of the POM associated with the jar to install. GroupId, artifactId and version will be extracted from this file. [jar] is the path to the jar to install, usually located in the build folder. [link] is an additional link to the jar to install, usually there should be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that there is no need to specify those particular links if the --java-lib option is used. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this jar file -e<version>, --set-version=<version>: set the version for the jar, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the groupId, artifactId and version from the POM file. -l --java-lib: Optional, if given it will install the jar into /usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo -n<name> --usj-name=<name>: Optional, the name to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM. -j<version> --usj-version=<version>: Optional, the version to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM. -s --no-usj-versionless: Optional, don't install the versionless link in /usr/share/java. This flag is used only when the -l or --java-lib option is given. -d<path> --dest-jar=<path>: Optional, the destination for the real jar. The other places where the jar appears, in the repository or in the list of links, will be symlinks to this jar. Defaults to /usr/share/java/$name-$version.jar if --java-lib is used, otherwise the jar is installed in the versioned path in the Maven reposi- tory. -c<classifier> --classifier=<classifier>: Optional, the classifier for the jar. Empty by default. -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results --skip-clean-pom: don't clean the pom, assume that a previous action ran mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar See also: mh_installpom(1), mh_installsite(1) Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)