[SCM] eclipse - Powerful IDE written in java - Debian package. branch, master, updated. ad73e2d691f1fdb8b9b1be68ee04f7a285f28814
Benjamin Drung
bdrung-guest at alioth.debian.org
Tue Oct 6 20:51:10 UTC 2009
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "eclipse - Powerful IDE written in java - Debian package.".
The branch, master has been updated
via ad73e2d691f1fdb8b9b1be68ee04f7a285f28814 (commit)
from 098826457f2573533fc137790233fdab5dd47e20 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit ad73e2d691f1fdb8b9b1be68ee04f7a285f28814
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Tue Oct 6 22:50:51 2009 +0200
Remove unused efj script
-----------------------------------------------------------------------
Summary of changes:
debian/extra/efj.1 | 35 -------------
debian/extra/efj.sh | 141 ---------------------------------------------------
2 files changed, 0 insertions(+), 176 deletions(-)
diff --git a/debian/extra/efj.1 b/debian/extra/efj.1
deleted file mode 100644
index 640ad1d..0000000
--- a/debian/extra/efj.1
+++ /dev/null
@@ -1,35 +0,0 @@
-.TH EFJ "1" "June 2006"
-.SH NAME
-efj \- manual page for Eclipse Formatter for Java
-.SH SYNOPSIS
-.B efj <options> <source files>\fR
-.SH DESCRIPTION
-EFJ is the commanline version of the Eclipse source code formatter.
-The main motivation for EFJ comes from a request to use Eclipse's Java formatter without
-having to install the entire Eclipse Platform, JDT or a GUI toolkit. It is possible to run
-a nightly cron job which checks out the code, formats it and checks it back in. EFJ could also
-be used in a server side commit hook.
-
-.SH OPTIONS
-.TP
-\fB\-config\fR <file> Use the formatting style from the specified config file. This file must be an xml file that has been exported by Eclipse.
-.TP
-\fB\-help\fR Display this message.
-.TP
-\fB\-quiet\fR Only print error messages.
-.TP
-\fB\-verbose\fR Be verbose about the formatting job.
-.PP
-.SH SEE ALSO
-eclipse(1)
-.SH ISSUES
-You may also notice that an empty workspace directory is created in the directory that efj
-is called from. This is because EFJ is just a GUI-less version of eclipse. Affords exists
-to disable this behaviour.
-.SH "REPORTING BUGS"
-Report bugs to Ben Konrath <ben at bagu.org>.
-.SH AUTHOR
-ecj was written by Ben Konrath <ben at bagu.org>. See the web site
-http://www.bagu.org/eclipse/efj/ for more information.
-
-This manual page was written by Stephan Michels <stephan at apache.org>.
diff --git a/debian/extra/efj.sh b/debian/extra/efj.sh
deleted file mode 100644
index 8efb732..0000000
--- a/debian/extra/efj.sh
+++ /dev/null
@@ -1,141 +0,0 @@
-#!/bin/bash
-
-# Having any sort of classpath causes massive breakage, with Kaffe at least.
-unset CLASSPATH; export CLASSPATH
-
-# Allow the user to specify their own Java home, we check for it later.
-#unset JAVA_HOME; export JAVA_HOME
-
-CMDLINEARGS=""
-VMARGS=""
-INSTALL="/usr/lib/eclipse"
-STARTUP="/usr/lib/eclipse/startup.jar"
-
-if [ -x /usr/bin/zenity ]; then
- DIALOG=/usr/bin/zenity
-elif [ -x /usr/bin/kdialog ]; then
- DIALOG=/usr/bin/kdialog
-elif [ -x /usr/bin/xdialog ]; then
- DIALOG=/usr/bin/xdialog
-else
- DIALOG=echo
-fi
-
-# Make sure this directory exists.
-if [ ! -d ~/.eclipse ]; then
- mkdir ~/.eclipse > /dev/null 2>&1
- if [ $? -ne 0 ]; then
- $DIALOG \
- --error \
- --title="Could not launch Eclipse Platform" \
- --text="Could not create settings directory at ~/.eclipse."
- fi
-fi
-
-# Just in case Eclipse tries to put something in the home directory.
-cd ~
-
-# Load default settings from the user's configuration file.
-if [ -f ~/.eclipse/eclipserc ]; then
- . ~/.eclipse/eclipserc
-fi
-
-# Process the command line options. These override the eclipserc file, so we do
-# them after parsing that file.
-while [ "$1" ]; do
- if [ "$1" = "-h" -o "$1" = "--help" ]; then
- echo "Eclipse Starter Script"
- echo "Usage:"
- echo "eclipse [options [value]]"
- echo "See eclipse(1) for more information."
- echo ""
- echo "Also see ~/.eclipse/eclipserc, which provides some default values"
- exit 0
- elif [ "$1" = "-vm" ]; then
- shift
- unset JAVA_HOME
- JAVACMD="$1"
- shift
- elif [ "$1" = "-install" ]; then
- shift
- INSTALL="$1"
- shift
- elif [ "$1" = "-startup" ]; then
- shift
- STARTUP="$1"
- shift
- elif [ "$1" = "-vmargs" ]; then
- shift
- while [ "$1" ]; do
- VMARGS="${VMARGS} $1"
- shift
- done
- else
- CMDLINEARGS="${CMDLINEARGS} $1"
- shift
- fi
-done
-
-# If the user has specified a custom JAVA, we check it for validity.
-# JAVA defines the virtual machine that Eclipse will use to launch itself.
-if [ -n "${JAVA_HOME}" ]; then
- echo "using specified vm: ${JAVA_HOME}"
- if [ ! -x "${JAVA_HOME}/bin/java" ]; then
- $DIALOG \
- --error \
- --title="Could not launch Eclipse Platform" \
- --text="The custom VM you have chosen is not a valid executable."
- exit 1
- fi
-fi
-
-# If the user has not set JAVA_HOME, cycle through our list of compatible VM's
-# and pick the first one that exists.
-if [ -z "${JAVA_HOME}" -a ! -n "${JAVACMD}" ]; then
- echo "searching for compatible vm..."
- javahomelist=`cat /etc/eclipse/java_home | grep -v '^#' | grep -v '^$' | while read line ; do echo -n $line ; echo -n ":" ; done`
- OFS="$IFS"
- IFS=":"
- for JAVA_HOME in $javahomelist ; do
- echo -n " testing ${JAVA_HOME}..."
- if [ -x "${JAVA_HOME}/bin/java" ]; then
- export JAVA_HOME
- echo "found"
- break
- else
- echo "not found"
- fi
- done
- IFS="$OFS"
-fi
-
-# If we don't have a JAVA_HOME yet, we're doomed.
-if [ -z "${JAVA_HOME}" -a ! -n "${JAVACMD}" ]; then
- $DIALOG \
- --error \
- --title="Could not launch Eclipse Platform" \
- --text="A suitable Java Virtual Machine for running the Eclipse Platform could not be located."
- exit 1
-fi
-
-# Set JAVACMD from JAVA_HOME
-if [ -n "${JAVA_HOME}" -a -z "${JAVACMD}" ]; then
- JAVACMD="$JAVA_HOME/bin/java"
-fi
-
-case $CLASSPATH in
- */usr/lib/eclipse/startup.jar*) ;;
- *) CLASSPATH=$CLASSPATH:/usr/lib/eclipse/startup.jar
-esac
-
-export CLASSPATH
-
-# Do the actual launch of the Eclipse Code Formatter with the selected VM.
-exec $JAVA_HOME/bin/java \
- org.eclipse.core.launcher.Main \
- -application org.eclipse.jdt.core.JavaCodeFormatter \
- ${1+"$@"} \
- -vmargs -Djava.library.path=/usr/lib/jni \
- -Dgnu.gcj.precompiled.db.path=/var/lib/gcj-4.2/classmap.db \
- -Dgnu.gcj.runtime.VMClassLoader.library_control=never \
- -Dosgi.locking=none ${VMARGS}
hooks/post-receive
--
eclipse - Powerful IDE written in java - Debian package.
More information about the pkg-java-commits
mailing list