Free jars software for linux

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. ProGuard project can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions.
Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
More compact jar files also means smaller storage requirements, faster transfer of applications across networks, faster loading, and smaller memory footprints.
ProGuards main advantage compared to other Java obfuscators is probably its compact template-based configuration. A few intuitive command line options or a simple configuration file are usually sufficient. For instance, the following configuration option preserves all applets in a jar:
-keep public class * extends java.applet.Applet
The user manual explains all available options and shows more examples of this powerful configuration style.
ProGuard is fast. It only takes seconds to process programs and libraries of several megabytes. The results section presents actual figures for a number of applications.
ProGuard is a command-line tool with an optional graphical user interface. It also comes with plugins for Ant and for the J2ME Wireless Toolkit.
ProGuard is a Java class file shrinker, optimizer, and obfuscator. The shrinking step detects and removes unused classes, fields, methods, and attributes. The optimization step analyzes and optimizes the bytecode of the methods. The obfuscation step renames the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard can also be used to list unused fields and methods in an application, and to print out the internal structure of class files.
ProGuard typically reads the input jars (or wars, ears, zips, or directories). It then shrinks, optimizes, and obfuscates them. It then writes the results to one or more output jars (or wars, ears, zips, or directories). The input jars can optionally contain resource files. ProGuard copies all non-class resource files from the input jars to the output jars. Their names and contents remain unchanged.
ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
In order to determine which code has to be preserved and which code can be discarded or obfuscated, you have to specify one or more entry points to your code. These entry points are typically classes with main methods, applets, midlets, etc.
- In the shrinking step, ProGuard starts from these seeds and recursively determines which classes and class members are used. All other classes and class members are discarded.
- In the optimization step, ProGuard further optimizes the code. Among other optimizations, classes and methods that are not entry points can be made final, and some methods may be inlined.
- In the obfuscation step, ProGuard renames classes and class members that are not entry points. In this entire process, keeping the entry points ensures that they can still be accessed by their original names.
Any classes or class members of your code that are created or invoked dynamically (that is, by name) have to be specified as entry points too. It is generally impossible to determine these cases automatically, but ProGuard will offer some suggestions if keeping some classes or class members appears necessary. For proper results, you should at least be somewhat familiar with the code that you are processing.
ProGuard does handle Class.forName("SomeClass") and SomeClass.class constructs automatically. The referenced classes are preserved in the shrinking phase, and the string arguments are properly replaced in the obfuscation phase. With variable string arguments, it is generally impossible to determine their possible values (they might be read from a configuration file, for instance).
However, as mentioned, ProGuard will note constructs like "(SomeClass)Class.forName(variable).newInstance()". These might be an indication that the class or interface SomeClass and/or its implementations may need to be preserved. You can then adapt your configuration accordingly.
Whats New in 3.9 Stable Release:
- This release fixes a number of bugs.
- Notably, ".class" constructs compiled in Java 6 are now handled correctly.
- The optimization step now avoids a possible division by 0 and correctly processes local variables with indices larger than 255.
- The documentation and examples have been updated.
Whats New in 4.0 Beta Development Release:
- Added preverifier for Java 6 and Java Micro Edition, with new option -dontpreverify.
- Added new option -target to modify java version of processed class files.
- Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation.
- Added support for configuration by means of annotations.
- Improved shrinking of unused annotations.
- Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing.
- Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of packages names.
- Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names.
- Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept.
- Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values.
- Added optimized local variable allocation.
- Added over 250 new peephole optimizations.
- Improved making classes and class members public or protected.
- Now printing notes on suspiciously unkept classes in parameters of specified methods.
- Now printing notes for class names that dont seem to be fully qualified.
- Added support for uppercase filename extensions.
- Rewritten class file I/O code.
- Updated documentation and examples.

Jar::Signer Perl module ease the process of creating a signed Jar file.

SYNOPSIS

# using FindBin is just a suggestion.
use FindBin qw( $RealBin );
use Jar::Signer;
my $signer = Jar::Signer->new;
# location of the keystore, created if needed.
$signer->keystore("$RealBin/MyKeyStore");
# dname properties of the certificate.
$signer->dname("CN=Mark Southern, O=My Corporation, L=My State, C=USA");
# name for .fingerprint and ..cert files, created if needed.
$signer->alias("$RealBin/MyCert");
# the Jar file that we want to sign.
$signer->jar(shift);
# if signed_jar is undefined then the default is basename.signed.jar where basename is the basename of the Jar file.
$signer->signed_jar(shift);
# create the signed Jar.
$signer->process;

This module, and the script that uses it make it a lot simpler to generate signed Jar files for use in Java applets etc. It steps through all the needed jar, jarsigner and keytool command lines.

j2Bin is a software that helps Java developers distribute their Java programs (.jars) as Linux executables, making the programs easy to run and use for the end user.
Note: This is the very first release, even so we invite everyone to try it and send feedback.
Enhancements:
- added english translation
- added portuguese-portugal translation

guglhupf commons resource repository is a tool that manages dependencies between program resources (e.g., Java jar files).
guglhupf commons resource repository comes with a mechanism to download needed resources from a central repository and stores these resources in a local repository. This allows reuse of resources between different projects.
Main features:
- Central resource repository to share resources between multiple projects.
- Needed resource are downloaded and stored in a local repository.
- Dependencies between resources are solved.
- Setup the classpath with all needed resources (jars).
- Start java progams with the needed resources.
- Ant integration to setup the classpath.
- Modular ant build script support
- Eclipse classpath builder to setup the classpath in eclipse.

Rad SFTP Applet is a graphical secure FTP (SFTP) applet. It is multi-threaded and thus capable of carrying out several concurrent uploads and downloads and resuming interrupted transfers.
The applet received a four star rating from jars.com - the premier java software review site and became featured on the official java website as well.
The secure FTP applet is ideal for Internet Service Providers and web hosting companies as a value addition to their service. The applet will also help web and software companies to reduce license costs with its per web site license model.
The desktop client is suited for individuals or organizations looking for a secure alternative to FTP.
Enhancements:
- Bugfixes and other improvements related to the management of hidden files and folders.

URL Rewriter is a tool for rewriting URL in Servlet. It is similar to mod_rewrite. This project is written in Java and it is licensed under LGPL.
< span style=color:blue >< b >Main features:< /b >< /span >< br/ >
- Easy installation
- Easy extension. You can easily write new tags.
- Maven support.
< b >Installing Rewriter< /b >
If you are not using Maven you need to add this two jars to classpath (eg. WEB-INF/lib/): softeu-rewriter-1.1.jar and xom-1.1.jar.
If you are using Maven add dependency to pom.xml:
< !-- url rewriter -- >
< dependency >
< groupId >cz.softeu< /groupId >
< artifactId >softeu-rewriter< /artifactId >
< version >1.1< /version >
< scope >runtime< /scope >
< /dependency >
this library is not yet in main Maven repository, so add SoftEU repository to pom.xml:
< repositories >
< repository >
< id >softeu-repo< /id >
< url >http://maven.softeu.cz/< /url >
< /repository >
< /repositories >
Add to web.xml:
< !-- url rewriter -- >
< filter >
< filter-name >RewriterFilter< /filter-name >
< filter-class >cz.softeu.rewriter.RewriterFilter< /filter-class >
< /filter >
< filter-mapping >
< filter-name >RewriterFilter< /filter-name >
< url-pattern >/*< /url-pattern >
< /filter-mapping >
Create WEB-INF/rewriter-config.xml:
< rewriter-config xmlns:b="http://rewriter.softeu.cz/basic/" >
< b:regex >
< from >^/news/(.*)$< /from >
< to >/news.jsf?id=$1< /to >
< /b:regex >
< /rewriter-config >

WebRun provides a simple Java application distribution tool.
WebRun is a single Java class file that implements a remote class loader and application launcher that can be used to distribute Java applications to clients.
This drastically reduces the need to continually update each client as only this class file plus the Java environment is needed on the client.
WebRun load JAR and CLASS files from URLs plus it supports basic authentication with HTTP URLs.
A simple Java Application Starter that can load jars and class files from URLs, including password protected URLs. WebRun offers the benefits of Java without the overhead or bugs of web browsers.
The front end is run as the main Java class using any Java 1.1 or later runtime environment (RT, JRE, or JDK). It may be compiled as part of a package or outside of packages. It does not depend on its package name in any way other than it is the location where we place our Java tools.
The code was specifically written in such a way as to only require a single class file (in addition to Java) to be on the users system. Thus some of the strange constructs to do the AWT windows for the password entry and for the status display.
Enhancements:
- Very minor changes and some source code cleanups.

Launch4j project is a cross-platform tool for wrapping Java applications distributed as jars in lightweight Windows native executables.
The executable can be configured to search for a certain JRE version or use a bundled one, and its possible to set runtime options, like the initial/max heap size.
The wrapper also provides better user experience through an application icon, a native pre-JRE splash screen, a custom process name, and a Java download page in case the appropriate JRE cannot be found.
Main features:
- Launch4j wraps jars in Windows native executables and allows to run them like a regular Windows program. Its possible to wrap applications on Linux!
- Doesnt extract the jar from the executable.
- Custom application icon with multiple resolutions and color depths.
- Native pre-JRE splash screen in BMP format shown until the Java application starts.
- Process name as the executable filename to easily identify your application.
- Works with a bundled JRE or searches for newest JRE / SDK in given range.
- Opens Java download page if an appropriate Java version cannot be found.
- Supports GUI and console apps.
- Passes command line arguments, also supports constant arguments.
- Allows to set the initial/max heap size.
- JVM options: set system properties, tweak the garbage collection...
- Option to change current directory to the executable location.
- Custom version information shown by Windows Explorer.
- GUI and command line interface.
- Build integration through an Ant task.
- Lightweight: 21 KB!
- Its free and may be used for commercial purposes.
- Includes a sample application and Ant script that automates the build process from Java sources to native executable.
- The wrapped program works on all Windows platforms (98/Me/NT/2K/Xp), launch4j works on NT/2K/Xp, Linux (developed and tested on FC2)
Whats New in 2.1.5 Stable Release:
- Changed the Java download site to http://java.com/download.
- Now its possible to use absolute and relative paths to specify the embedded JRE.
Enhancements:
- Enhanced GUI.
- Redesigned error reporting.
- Added custom error messages.
- Added support website feature.
- Added PWD and OLDPWD special variables and access to the registry.
- Runtime ini file extension changed to .l4j.ini, added comments (#).
- FR #1427811 Initial process priority.
- FR #1547339 Added VarFileInfo structure to Version Info (Stephan Laertz).
- FR #1584295 Updated documentation for --l4j-debug.
- Fixed and config conversion bug (found by Dafe Simonek).
- Fixed the Ant task exception reporting bug, added tmpdir and bindir attributes.
- Fixed bug #1563415 Problem with launching application when ini file exists (found by mojomax).
- Fixed bug #1527619 Console header wildcard expansion (found by erikjv).
- Fixed bug #1544167 NPE when dontwrap and only classpath given (found by Hendrik Schreiber).
- Fixed bug #1584264 Dropdown boxes get mixed up (found by Larsen).