Free compile java to exe software for linux

Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications and applets.
Java Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.
It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.
Main features:
- GUI with built-in help and small footprint.
- Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
- Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
- Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
- Point and click creation of all files (Java, manifest and HTML) and directories (package).
- Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
- Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
- Checking for unused, redundant and missing imports.
- Logging of all commands invoked by GUI.
- Code metrics for Java files.
- Built-in text editor (see Edit for details).
- Built-in user interface for the Java debugger with command-line editing and history.
- Self-installing executable (Java archive file).
- Comprehensive installation and user documentation for Java and Java Tools.

Sitemaps for Java provides a Java API for the creation of Google Sitemaps and -Indexes.
Sitemaps for Java allows developers to easily create Google Sitemaps. It handles every aspect of Sitemap creation, allowing you to create unlimited Sitemaps and -Indexes.
Provided is API / Javadoc, an example-usage as well as Sitemap ressources and other information
Enhancements:
- Initial beta-release of Sitemaps for Java, this includes basic functionality to create Google Sitemaps and -Indexes with/without compressed Sitemaps
- unlimited number of URLs, Sitemaps and -Indexes.

The Java Exorcist projects aim is to create a small and easy to use tool, that can be used to extend the Java language syntactically. Why would you do that? There are basically two reasons:
First, you just might want to fix your pet-peeve in the language itself. For example, create new keywords like unless, foreach, new operators, or generate setter getters automatically for a bean property.

Secondly, you might tune the language itself for a specific project, so the project code may look more clean and thought out. For example: specific logger keyword, which automatically checks (if statement) whether the logger should be invoked or not, or even ommits the whole logging compile-time, when its disabled! Or create a method modifier transaction to enclose the whole method in a project specific transaction.

How it works on the outside

Exorcist is a compiler of extended Java code. The compiler can be used in command-line mode, or through Ant. Basically, with no extensions configured, Exorcist only compiles the standard java code. To extend the language, you can plug in classes, which extend a single interface of the exorcist framework, and implement a single (and simple) method. Thats it.

How it works inside

Exorcist works like a pre-processor. It translates the extended language into plain Java code, and then compiles it using the standard Java compiler (javac).

To analyze a language, there are two steps involved. The first is a Lexical analysis, the second is the Parsing of the lexical tokens. Lexical tokens are strings, numbers, operators, dots, semicolons, etc. These are also called terminal symbols, because they can not be analyzed further. During parsing, lexical tokens are read, and non-terminal symbols may be produced.

These include things like: expression, method body, declaration, if-statement, etc. The Exorcists tranformation engine works basically with lexical token lists. Each extension first matches itself to the start of the received token list, using terminal and non-terminal symbols freely. If the match is detected, the extension is free to modify the input token list as it pleases, and with it modify the output clean Java source code.

Java Tetris project is a simple Tetris game.
Java Tetris is a game written with Eclipse and the VE Plugin. It is a nice starting point if you want to learn Java and Eclipse.
The game can be started as Java applet or Java application.
Enhancements:
- The dependency on jdom was removed.
- The jar is now only 30kb.
- A bug was fixed in the score list.

XML::Compile::Schema is a Perl module to compile a schema.

INHERITANCE

XML::Compile::Schema
is a XML::Compile

SYNOPSIS

# preparation
my $parser = XML::LibXML->new;
my $tree = $parser->parse...(...);

my $schema = XML::Compile::Schema->new($tree);

my $schema = XML::Compile::Schema->new($xml_string);
my $read = $schema->compile(READER => mytype);
my $hash = $read->($xml);

my $doc = XML::LibXML::Document->new(1.0, UTF-8);
my $write = $schema->compile(WRITER => mytype);
my $xml = $write->($doc, $hash);
print $xml->toString;

This module collects knowledge about a schema. The most important method is compile() which can create XML file readers and writers based on the schema information and some selected type.

WARNING: The compiler is implemented in XML::Compile::Schema::Translate, which is NOT FINISHED. See that manual page about the specific behavior and its (current) limitations! Please help to find missing pieces and mistakes.

WARNING: the provided schema is not validated! In some cases, compile-time and run-time errors will be reported, but typically only in cases that the parser has no idea what to do with such a mistake. On the other hand, the processed data is validated: the output should follow the specs closely.

Two implementations use the translator, and more can be added later. Both get created with the compile() method.

XML Reader

The XML reader produces a hash from a XML::LibXML::Node tree, or an XML string. The values are checked and will be ignored if the value is not according to the specs.

XML Writer

The writer produces schema compliant XML, based on a hash. To get the data encoding correct, you are required to pass a document in which the XML nodes may get a place later.

Java for C++ is a tool to generate C++-wrapper-classes for existing Java-classes. This tool reads a list of Java class names and creates source code for C++-classes to wrap them.
The implementation of the wrapper classes uses JNI (Java Native Interface) to call the "real" Java classes.
The C++-API to use these wrapper classes is very close to the API of the original Java classes. So developers of C++-software can use Java-classes as if they have been implemented in C++.
Enhancements:
- A problem where null values for method arguments, method return values, or field values caused some generated code to crash was fixed.
- Updating is strongly encouraged.

Java-GNOME is a set of Java bindings for GNOME and GTK libraries, so GNOME applications can be written in Java.

libvte-java is implemented as a JNI layer that delegates the Java calls out to the underlying C library.

Installation:

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.