Free jars software for linux

Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a projects build, reporting and documentation from a central piece of information.
Main features:
Model based builds
- Maven is able to build any number of projects into predefined output types such as a JAR, WAR, or distribution based on metadata about the project, without any need to do any scripting in most cases.
Coherent site of project information
- Using the same metadata as for the build process, Maven is able to generate a web site or PDF including any documentation you care to add, and adds to that standard reports about the state of development of the project. Examples of this information can be seen at the bottom of the left-hand navigation of this site under the "Project Information" and "Project Reports" submenus.
Release management and distribution publication
- Without much additional configuration, Maven will integrate with your source control system such as CVS and manage the release of a project based on a certain tag. It can also publish this to a distribution location for use by other projects. Maven is able to publish individual outputs such as a JAR, an archive including other dependencies and documentation, or as a source distribution.
Dependency management
- Maven encourages the use of a central repository of JARs and other dependencies. Maven comes with a mechanism that your projects clients can use to download any JARs required for building your project from a central JAR repository much like Perls CPAN. This allows users of Maven to reuse JARs across projects and encourages communication between projects to ensure backward compatibility issues are dealt with. We are collaborating with the folks at Ibiblio who have graciously allowed the central repository to live on their servers.
Gump integration
- Integration with Gump. For those who are not familiar with Gump it is a tool used at Apache to help projects maintain backward compatibility with their clients. If you have a Maven project descriptor then you can easily participate in nightly Gump builds that will help your project stay abreast of the impact your changes actually have in Java developer community. We are working on our own massive build tool but integration with Gump comes at no cost to Maven users.

gnu.hylafax is open source software distributed under the terms of the GNU
Library General Public License.

See the COPYING.LIB file for details. Some included utilities are distributed under the terms of the GNU General Public License, a copy of which is included in the file COPYING.

Installation:

Copy the gnu-hylafax-0.0.8.jar file (located in the lib directory)
to your usual installation directory for Java archives.

To use gnu.hylafax, you will need to include it in your classpath setting. Typically this is done by adding an entry to your CLASSPATH variable setting with the full path to the JAR file, e.g.

csh: % setenv CLASSPATH ${CLASSPATH}:/usr/java/lib/gnu-hylafax-0.0.8.jar
bash: % export CLASSPATH=${CLASSPATH}:/usr/java/lib/gnu-hylafax-0.0.8.jar
DOS: > set CLASSPATH %CLASSPATH%;C:Javalibgnu-hylafax-0.0.8.jar

Various shells and operating systems may have slightly different methods.
Consult your Java virtual machine documentation for details.

You may also:

specify the -classpath option to the java executable, e.g.
compile: % javac -classpath /usr/java/lib/gnu-hylafax-0.0.8.jar MyClass.java
execute: % java -classpath /usr/java/lib/gnu-hylafax-0.0.8.jar MyClass

ChiliMac is an interactive macro language implemented in 100% Java. It emphasizes ease of use and portability, while still providing several features for the power user.

It is built around XML (eXtensible Markup Language), which is a vibrant industry standard. This ensures compatibility with several third party tools and remarkable flexibility.

ChiliMac processes source documents, performs the specified actions and then generates output from the processed source documents.

Installation:

ChiliMac currently lacks an automated installation procedure. This will be remedied in future versions. Until then, the following should serve as a guide to manual installation of ChiliMac.
Firstly, you must install a Java Standard Edition Runtime Environment 5.0 (1.5.0) or greater.

Next, you will need to download the ChiliMac binary (the JAR file) to a suitable location for your system. Finally, the tricky part, you have to manually integrate the ChiliMac binary into your system.

This varies greatly from system to system, but is generally achieved by creating a shell script or batch file and adding it to your systems path.

Alternatively, you can just run the ChiliMac binary from the command line as follows (where x.y.z is substituded with the actual version number of the JAR file):

java -jar chilimac-x.y.z-bin.jar

FTP SyncAgent is a software that keeps a local folder and a remote FTP folder in sync. All what you need to do is to create a Java properties file (explained here) and start it.

Currently there is only a console-based UI and you will be asked for files to download/upload or remove.

Later on, I will provide a more intelligent agent module which can be pre-configured for common descision patterns and which will be able to choose automatically what to do. Thus, the agent should be able to run as a cron job and periodically check for required updates.

Quick Start

1. Download the latest release of FTP SyncAgent and the two dependent libraries: Jakarta Commons Net and ORO (you will only need the two JAR files commons-net-[version].jar and jakarta-oro-[version].jar).
2. Create a properties (config) file for each directory to sync, e.g. syncedFolder.properties and save it somewhere, lets say in /home/myUser/syncedFolder.properties. The file should contain at least the following lines (you can copy it from here!):

host=ftp.theFTPserver.com
port=21
user=myUserName
pass=myPassword
remoteFolder=absolutePathToTheLocalFolderToSync
localFolder=relativePathToTheRemoteFolderToSync
verbose=true
passive=true
ignore=.backup .bak ~

The host, port, user, and pass properties should be clear, the remoteFolder is the path to the remote folder relative to the FTP home directory (e.g. /mySyncedFiles), the localFolder is the absolute directory path to the local folder to be synced (e.g. /home/myUser/aFolderToSync). The property verbose is just for a more detailed output to the shell when sychronising, passive will enable (or disable) a passive connection to the server (if you are behind a firewall our gateway router), and using ignore you can specify file suffices to exclude.
3. Setup the classpath or specify it when starting (as shown here at the next step). The classpath must contain the two dependent JARs as described under requirements and the FTP SyncAgent JAR file ftpsyncagent.jar.
4. Now you can run FTP SyncAgent with the following command (you must adjust the path to the JAR files according to your directory structure! Create a shell script or batch file for an easier startup):

java -cp /opt/javalibs/ftpsyncagent.jar:/opt/javalibs/commons-net-1.4.1.jar:
/opt/javalibs/jakarta-oro-2.0.8.jar at.langegger.ftpsa.SyncAgent
/home/myUser/syncedFolder.properties

The basic usage is:

java -cp [jar-files] at.langegger.ftpsa.SyncAgent [custom properties-file]

5. Thats all. For any questions, contact me (via e-mail, address below).

Cleaner is a Java beautifier that transforms ugly syntax into beautiful syntax. The Java code syntax is parsed using ANTLR and then printed to standard output.

Source is included.

Something like this:

public void foo(String bar)
{
for(int x=0; x < 9; x++ )
{
System.out.println ("X = " + x);
}
}

Will become

public void foo( String bar ){
for ( int x = 0; x < 9; x++ ){
System.out.println( "X = " + x );
}
}

Compile:

$ ant

Run:

$ java -classpath cleaner.jar:lib/antlr.jar cleaner.Cleaner < some-file >

Xgrid Agent for Java is an agent for Apples Xgrid clustering protocol written entirely in Java. This makes multiple platform Xgrid clusters possible.
Usage:
usage: java -jar xgridagent.jar -r|host name mhz
-r will resolve the controller via bonjour
host is the address or hostname on the controller
name is the name of this agent
mhz is the CPU power of one CPU in this agent
run the program from within the xgridagent directory
Enhancements:
- Many changes (may break things).

How do you build a web application without data? Suppose it has many pages, including forms and pages for display. Until theyre developed, users cant enter information. Mock data has to be provided to the application, to test the interaction between screens, business logic, and database.
It may take a good amount of effort to create a mock dataset large and complex enough to mimic real world situations. For example, it is not unusual for an application to be supported by a database schema with hundreds of tables, each with many columns and many foreign key relationships. The database may have millions of rows of data. Datatypes include integer, floating precision, datetime, and string. There are a wide range of values, and they are dependent on each other in ways that must satisfy the business requirements.
Mock data is useful at various points in development. It can be used with an HTTP test client, to simulate the responses a user makes at the front end. It can be inserted directly into the database, to test the database access layer. It can replace the database layer, and be provided directly to the business logic implementation.
It might be nice if the datasets at these different stages come from the same pool, so that their values represent the same underlying model. It would be nice if this model could be constructed once, and then the presentation of the data tailored for the stage at which its used.
Often a great deal of effort is spent reducing the worlds objects into a compact object model. Datamixer goes the other way: it takes a conceptual object model, and explodes it back into a diversity of objects. It tries to make this diversity easy to manage, through configuration and customization. It interacts with data repositories, and is able to mix and merge mock values with real ones. The aim is to make it easy to create the data, so that time can be spent on the data model.
Datamixer does not attempt to analyze a problem domain, in order to generate data that does a better job at testing the domain. It could be driven by a tool that does that kind of analysis.
Installation:
To install, simply unzip or unjar the distribution package to a directory of your choice. A distribution has these directories:
- The data directory has files with samples of commonly used data, such as names. It is intended to grow.
- The doc directory has documentation.
- The examples directory has example Java source and XML configuration scripts. Apache Ant is used to run these examples: type ant build
- The lib directory has all jars required by the application.
Enhancements:
- license changed to BSD.