| 1 |
Source: libjpf-java |
| 2 |
Section: java |
| 3 |
Priority: extra |
| 4 |
Maintainer: gregor herrmann <gregoa@debian.org> |
| 5 |
Uploaders: tony mancill <tmancill@debian.org> |
| 6 |
Build-Depends: debhelper (>= 5), ant, quilt (>= 0.40) |
| 7 |
Build-Depends-Indep: default-jdk-builddep, libcommons-logging-java, |
| 8 |
libjxp-java, libonemind-commons-java-java, libonemind-commons-invoke-java |
| 9 |
Homepage: http://jpf.sourceforge.net/ |
| 10 |
Standards-Version: 3.8.2 |
| 11 |
Vcs-Svn: http://svn.toastfreeware.priv.at/debian/libjpf-java/trunk/ |
| 12 |
Vcs-Browser: http://svn.toastfreeware.priv.at/wsvn/ToastfreewareDebian/libjpf-java/trunk |
| 13 |
|
| 14 |
Package: libjpf-java |
| 15 |
Architecture: all |
| 16 |
Depends: default-jre-headless | java-runtime-headless |
| 17 |
Description: Java Plugin Framework: plug-in infrastructure library for Java projects |
| 18 |
JPF provides a runtime engine that dynamically discovers and loads |
| 19 |
"plug-ins". A plug-in is a structured component that describes itself to JPF |
| 20 |
using a "manifest". JPF maintains a registry of available plug-ins and the |
| 21 |
functions they provide (via extension points and extensions). |
| 22 |
. |
| 23 |
One major goal of JPF is that the application (and its end-user) should not |
| 24 |
pay any memory or performance penalty for plug-ins that are installed, but |
| 25 |
not used. Plug-ins are added to the registry at application start-up or |
| 26 |
while the application is running but they are not loaded until they are |
| 27 |
called. |
Parent Directory
| 
Revision Log