This plugin for Maven 2 is based on the BND tool from Peter Kriens. The way BND works is by treating your project as a big collection of classes (e.g., project code, dependencies, and the class path). The way you create a bundle with BND is to tell it the content of the bundle's JAR file as a subset of the available classes. This plugin wraps BND to make it work specifically with the Maven 2 project structure and to provide it with reasonable default behavior for Maven 2 projects.
Since the 1.4.0 release, this plugin also aims to automate OBR (OSGi Bundle Repository) management. It helps manage a local OBR for your local Maven repository, and also supports remote OBRs for bundle distribution. The plug-in automatically computes bundle capabilities and requirements, using a combination of Bindex and Maven metadata.
bnd is the Swiss army knife of OSGi, it is used for creating and working with OSGi bundles. Its primary goal is take the pain out of developing bundles. With OSGi you are forced to provide additional metadata in the JAR's manifest to verify the consistency of your "class path". This metadata must be closely aligned with the class files in the bundle and the policies that a company has about versioning. Maintaining this metdata is an error prone chore because many aspects are redundant.
Autojar dient dazu, jar-Archive minimaler Größe aus unterschiedlichen Qellen (eigenen Klassen, Verzeichnissen, Archiven) zu erzeugen. Ausgehend von einer oder mehreren Klassen wird der Bytecode rekursiv nach weiteren benutzten Klassen durchsucht; diese werden ggf. aus ihrem Archiv extrahiert und in die Ausgabedatei übernommen. Das resultierende Archiv enthält alle tatsächlich benutzten Klassen, und nur diese. Somit lassen sich z.B. Größe und Ladezeit von Applets klein halten oder Applikationen unabhängig von installierten Bibliotheken machen.
The Fat Jar Eclipse Plug-In is a Deployment-Tool which deploys an Eclipse java-project into one executable jar.It adds the Entry "Build Fat-JAR" to the Export-Wizard.In addition to the eclipse standard jar-exporter referenced classes and jars are included to the "Fat-Jar", so the resulting jar contains all needed classes and can be executed directly with "java -jar", no classpath has to be set, no additional jars have to be deployed.
The Fat Jar Eclipse Plug-In is a Deployment-Tool which deploys an Eclipse java-project into one executable jar.
It adds the Entry "Build Fat-JAR" to the Export-Wizard.
In addition to the eclipse standard jar-exporter referenced classes and jars are included to the "Fat-Jar", so the resulting jar contains all needed classes and can be executed directly with "java -jar", no classpath has to be set, no additional jars have to be deployed.
The Fat Jar Eclipse Plug-In is a Deployment-Tool which deploys an Eclipse java-project into one executable jar.
It adds the Entry "Build Fat-JAR" to the Export-Wizard.
In addition to the eclipse standard jar-exporter referenced classes and jars are included to the "Fat-Jar", so the resulting jar contains all needed classes and can be executed directly with "java -jar", no classpath has to be set, no additional jars have to be deployed.
How to Run a .Jar Java File. .jar files are used for archiving, archive unpacking. One of the essential features of jar file is lossless data compression. Need to know how to run one? Here's how. Make sure you have Java installed on your...
If you've spent any time doing Java programming with Eclipse it must have occurred to you that support for viewing and editing Jar files is a little limited. Having used Eclipse for over eighteen months, and since I hadn't yet built an Eclipse plugin, I decided to dive right in and build a viewer/editor that would let me stop using File Explorer or WinZip(1) for manipulating the Jar files in my projects. Hopefully forever.
Five days later here it is: JarPlug, the Java ARchive PLUGin for Eclipse (sorry... :). And what days: going up the learning curve of Eclipse plugin internals and trying to figure out a workflow paradigm for editing Jar files that made sense inside the Eclipse IDE. More on that later.
What I usually do is, in Eclipse preferences, I define an Installed JRE called "JDK X.Y.Z" and include tools.jar as part of it libraries. Then I change the project preferences to use that JRE "JDK X.Y.Z".
JBoss Tattletale is a tool that can help you get an overview of the project you are working on or a product that you depend on.
The tool will provide you with reports that can help you
* Identify dependencies between JAR files
* Find missing classes from the classpath
* Spot if a class is located in multiple JAR files
* Spot if the same JAR file is located in multiple locations
* With a list of what each JAR file requires and provides
* Verify the SerialVersionUID of a class
* Find similar JAR files that have different version numbers
* Find JAR files without a version number
* Locate a class in a JAR file
* Get the OSGi status of your project
* Remove black listed API usage
JBoss Tattletale will recursive scan the directory pass as the argument for JAR files and then build the reports as HTML files.
The main HTML file is: index.html
JBoss Tattletale is licensed under GNU Lesser General Public License (LGPL) version 2.1 or later.
We hope that JBoss Tattletale will help you in your development tasks !
Reports
* Dependants
* Depends On
* Graphical Dependencies
* Transitive Dependants
* Transitive Depends On
* Class Location
* OSGi
* Eliminate Jar files with different versions
* Invalid version
* Multiple Jar files
* Multiple Locations
* No version
* Black listed API
* JAR archive
JUDIE steht für Java Universal Database Import and Export. Das Tool exportiert einzelne oder alle Tabellen einer JDBC Datenbank nach XML und importiert diese wieder in andere Datenbanken. Es ist als API (JAR), Kommandozeilenprogramm oder Eclipse Plugin verfügbar. Es kann für Entwickler und Administratoren nützlich sein, um Daten zwischen Datenbanken zu übertragen, besonders zum Aufsetzen von Testdatenbanken. Wegen der einfachen API kann das auch automatisiert werden, z.B. als Skript oder Ant-Task.
Die ersten javafähigen Handys verwendeten netzwerkabhängige Techniken, um Software auf dem Handy zu installieren. Alle Verfahren waren völlig unterschiedlich.
On October 11, 1745, German cleric Ewald Georg von Kleist and independently of him Dutch scientist Pieter van Musschenbroek from the city of Leiden, Netherlands, invented a predecessor of today's battery, the Leyden Jar.
Xerces used to be released as a single jar (xerces.jar), but was split into two jars, one containing the API (xml-apis.jar) and one containing the implementations of those APIs (xercesImpl.jar). Many older Maven POMs still declare a dependency on xerces.jar. At some point in the past, Xerces was also released as xmlParserAPIs.jar, which some older POMs also depend on.