jh_installeclipse(1) [debian man page]

JH_INSTALLECLIPSE(1)						    Javahelper						      JH_INSTALLECLIPSE(1)

NAME

       jh_installeclipse - Installs eclipse features built by pde-build into package build directories

SYNOPSIS

       jh_installeclipse [debhelperoptions] [--install-name=name] [--pde-build-dir=dir] [feature[...]]

DESCRIPTION

       jh_installeclipse is a javahelper program that handles installing eclipse features built by pde-build into package build directories. These
       features can be specified either in the package's eh-install file or via command-line.

       jh_installeclipse uses debhelper behind the scenes and are therefore subject to the compat level (e.g. when parsing eh-install files).

       jh_installeclipse will replace all the embedded orbit depends imported by jh_generateorbitdeps with symlinks post install. The symlinked
       jar files will also be used to populate ${orbit:Depends} variable.

FILES

       debian/package.eh-install
	   List the eclipse features to install into each package and optionally under which name. The format is a set of lines, where each line
	   lists a file or files to install, and at the end of the line tells the name it should be installed under. You may use wildcards in the
	   names of the files to install.

	   If name is not present, eh_install will either use the install name given on the command line or attempt to guess it from the package
	   name. It is perfectly legal for two or more features to be installed under the same name.

OPTIONS

       --install-name=name
	   Specifies the name to install under if it is not given in the file. It is perfectly legal to install more than one feature under the
	   same name.

       --pde-build-dir=dir
	   Specifies the directory from where pde-build was run. Defauls to "debian/.eclipse_build".

EXAMPLE

       Suppose your package builds org.eclipse.emf and org.eclipse.xsd and you want to put org.eclipse.emf into eclipse-emf and org.eclipse.xsd
       into eclipse-xsd.  Then make debian/eclipse-emf.eh-install contain:

	 org.eclipse.emf

       and debian/eclipse-xsd.eh-install contain:

	 org.eclipse.xsd

       jh_installeclipse will then install org.eclipse.emf into usr/share/eclipse/dropins/emf/ and xsd into usr/share/eclipse/dropins/xsd/.

       In case your package is not called eclipse-name, or you want to install two different features into the same package, you will have to
       provide a name. Suppose you wanted to install both eclipse above into a single package called foo, then debian/foo.eh-install should
       contain:

	 org.eclipse.emf emf
	 org.eclipse.xsf xsd

SEE ALSO

       debhelper(7)

       This program is a part of javahelper and uses debhelper as backend. There are also tutorials in /usr/share/doc/javahelper.

AUTHOR

       Niels Thykier <niels@thykier.net>

COPYRIGHT AND LICENSE

       Copyright 2010 by Niels Thykier

       This tool is free software; you may redistribute it and/or modify it under the terms of GNU GPL 2.

0.43								    2011-03-24						      JH_INSTALLECLIPSE(1)

JH_COMPILEFEATURES(1)						    Javahelper						     JH_COMPILEFEATURES(1)

NAME

       jh_compilefeatures - Compiles eclipse features using pde-build.

SYNOPSIS

       jh_compilefeatures [debhelperoptions] [options] [--pde-build-dir=dir] [feature[...]]

DESCRIPTION

       jh_compilefeatures is a javahelper program that handles compiling features using pde-build. These features can be specified either in
       debian/eclipse.features or via command-line.

       jh_compilefeatures uses debhelper behind the scenes and are therefore subject to the compat level (e.g. when parsing the eclipse.features
       file).

       When specifying the dependencies for a feature, jh_compilefeatures will see if this feature has just been compiled and will use the
       dependency if it is among the results. This can be used together with debian/eclipse.features.

       Dependencies are always resolved by first checking if it is a recently built feature and if not, then the system installed eclipse's
       dropins folders will be checked.

       Currently jh_compilefeatures do not clean up between builds, which means the dependencies for previous builds are present for the current
       build.  Nevertheless, do not rely on this, as this behavior is subject to change.

       Note: jh_compilefeatures will not rearrange the build order for you in order to do this.

       Note: that jh_compilefeatures will not error out if it cannot find a missing dependency. This is due to the underlying builder being unable
       to detect this.

FILES

       debian/eclipse.features
	   List the eclipse features to compile and their dependencies. The first item on the line is the feature to compile and the following
	   items are considered dependencies.

	   A dependency can either be a dropins folder or a previous built feature.  jh_compilefeatures will find it as long as it is installed in
	   the system eclipse's dropins folder or it has just been compiled.

OPTIONS

       --pde-build-dir=dir
	   Specifies the directory from where pde-build is to be run. Defauls to "debian/.eclipse_build".

       --feature-deps=deps
	   A space separated list of dependencies. These dependencies will be used to compile all features passed by command-line. Features read
	   from debian/eclipse.features are unaffected by this.

       --build-opts=args
	   Pass args to the underlying builder. These options are passed to all features built.

	   This defaults to "-DjavacTarget=1.5 -DjavacSource=1.5" if not set.  This can be disabled by passing the empty string.

       --jvm-args=args
	   Pass args to the JVM. These options are passed to all features built.

       --orbit-dir=dir
	   Specifies where the Orbit dependencies can be found. This is only needed if the orbit dir is in an unusual location.

       --pde-build=cmd
	   Use a non-standard pde-build command to compile the features.

       --pde-args=args
	   Passes args directly to pde-build. Note, jh_compilefeatures have specialised options for some of pde-build options and these should be
	   used whenever possible.

	   These options are passed to all features built.

       --ignore-java-home
	   Skip the check of JAVA_HOME. Since the underlying builder uses ant (and therefore java), the build should ensure it always uses the
	   expected java implementation.

	   Use this if you (for whatever reason) need to declare the specific java implementation without being able to use JAVA_HOME.

	   Note: You still have to tell the underlying builder which java to use.

EXAMPLE

       A sample debian/eclipse.features

	 org.eclipse.tm.terminal emf
	 org.eclipse.rse.sdk

       org.eclipse.tm.terminal depends on "emf", which is expected to be found in eclipse's dropins folder. org.eclipse.rse.sdk on the other hand
       has no dependencies beyond the eclipse platform.

       If needed you can also specify a previously built feature as a dependency:

	 org.eclipse.some.feature
	 org.eclipse.another.feature org.eclipse.some.feature rse

       Here org.eclipse.another.feature depends org.eclipse.some.feature, which was just built and also rse, which is expected to be in system
       installed eclipse's dropins.

SEE ALSO

       debhelper(7)

       This program is a part of javahelper and uses debhelper as backend. There are also tutorials in /usr/share/doc/javahelper.

AUTHOR

       Niels Thykier <niels@thykier.net>

COPYRIGHT AND LICENSE

       Copyright 2010 by Niels Thykier

       This tool is free software; you may redistribute it and/or modify it under the terms of GNU GPL 2.

0.43								    2011-03-24						     JH_COMPILEFEATURES(1)