Free all 1.1 software for linux

BALL is Rapid Software Prototyping can significantly reduce development times in the field of Computational Molecular Biology and Molecular Modeling. BALL (Biochemical Algorithms Library) is an application framework in C++ that has been specifically designed for this purpose.
BALL has been carefully designed to be robust, easy to use, and open to extensions. Especially its extensibility which results from an object-oriented and generic programming approach distinguishes it from other software packages.
BALL is well suited to serve as a public repository for reliable data structures and algorithms. Based on BALL we have developed a stand-alone tool for molecular visualization, BALLView . BALLView makes the broad functionality available through an integrated user-friendly GUI.
BALL is distributed under the Lesser GNU Public License (LGPL), parts of it are under the GNU Public License (GPL).
Enhancements:
- This version finally brings full support for Python, DLLs, and nmake Makefiles under Windows.
- A large number of prominent fixes were made, especialy for g++ 4.x.
- Some new functionality was added to BALLView.

EL4J, the Extension Library for the J2EE, adds incremental improvements to the Spring Java framework.
Main features:
- The ability to split applications in modules
- A module can consist of code, jar-files and configurations
- There can be transitive dependencies between modules
- A module can automatically enable its spring configuration when it is present
- The order and the location of configuration-information works accross various J2EE containers
- Simplified remoting
- Optional implicit context passing to cleanly add technical context with remote method invocations (e.g. to add a security principal or the sub-company on whose behalf a request is being made)
- Remote a POJO as SLSB or SFSB, remote a POJO via SOAP
- Clean remoting support for interfaces that lack a RemoteException in their interface where its required
- A light daemon manager service
- Various improvements
- Make the active beans and their configuration visible in JMX
- A light exception handling framework that implements a safety facade
- Simplified configuration of attribute-interceptor mappings
Enhancements:
- Many clean-ups in the build infrastructure and in the file organization
- Added a database plugin that allows to execute SQL scripts on the database.
- It can optionally launch an embedded database (Derby for now).
- Added a dependency plugin that illustrates the dependencies between modules graphically.
- Added a basic EL4J archetype to get started more easily
- We provide a mechanim to override the configuration files that are in the automatic Tomcat download (files etc/tomcat are copied to Tomcat).
- Test run now in the maven integration phase (in order for us to launch the database in the right moment).
- Some issues in the site-generation were fixed.
- Added an experimental version plugin that checks whether there are new versions available of existing maven plugins or of other jar-files a project depends on.
- Provided fixes for the external exec plugin
- Upgrade to some newer maven plugins: eclipse, javadoc, deploy.

ln_local is a simple shell script for managing the installation of software packages (typically in /usr/local). Its a program between stow and lndir/cleanlinks.

The approach used by ln_local (based on Stow) is to install each package into its own tree, then use symbolic links to make it appear as though the files are installed in the common tree (see examples for more details).

Contrary to stow, ln_local create all subdirectory tree and then create all symbolic links (stow create simbolic links for subdirectories and normals files, so conflicts may appends when two programs share the same subdirectory).

Usage

Usage: ln_local [options] [do] Action

Action : create | delete | clean
create : create symlink and directory in /usr/local from current directory
delete : delete symlink and empty directory in /usr/local from current directory
clean : remove broken symlink and empty directory in /usr/local

If do is presents in the command line then changes are made,
else NO CHANGE ARE MADE

Options are :
-s, --source the source directory (default:current directory)
-t, --target the target directory (/usr/local)
-V, --version display version and exit
-u, --usage long help
-h, --help display this help

Example

Standard way to use ln_local:

* download source package (.tar.gz, tar.bz2 ...)

* extract the archive:
tar -xzvf archive-x.x.x.tar.gz
or tar -xjvf archive-x.x.x.tar.bz2

* go to archive directory:
cd archive-x.x.x

* configure the program compilation:
./configure --prefix="/usr/install/archive-x.x.x"

* build the program:
make

* install the program:
make install
or make install DESTDIR=/usr/install/archive-x.x.x if theres no ./configure in this last case, you may have to edit manually the Makefile.

* create symlinks in /usr/local:
cd /usr/install/archive-x.x.x
ln_local create do

* delete the source and archive
cd in the archive-x.x.x.tar.gz directory
rm -rf archive-x.x.x*

you can change the target directory (/usr/local) by editing the file /usr/local/bin/ln_local or use the --target option

To remove an existing program:
cd /usr/install/archive-x.x.x
ln_local delete do

To clean the /usr/local directory:
ln_local clean do

To remove definitively a program:
rm -rf /usr/install/archive-x.x.x
ln_local clean do

If you want to see what ln_local will do, remove the do in create, delete and clean action, so no action will be done

ARAAS is a ticket-based authentication and authorization system. Can provide single-sign-on for multiple web servers. LDAP authentication.

It consists of a J2EE web application to authenticate users and generate secure session tickets and an Apache module to verify the tickets. It is possible to use the tickets on multiple web servers to provide single-sign-on.

Users are authenticated against an LDAP server. However, the authentication mechanism is extendable to allow the use of other kinds of authentication servers.
Once the user is authenticated normal Apache authorization configuration can be used to grant access to web pages.

A later release of ARASS will also allow to centralize the authorization information in a separate repository, like a database or an LDAP server. This can be used by web applications to store generic authorization information, similar to OMGs RAD service.

jaxen is a universal XPath evaluation engine. jaxen is currently capable of executing XPath expressions against W3C DOM, JDOM, dom4j, and XOM document trees.
Enhancements:
- Assorted bugfixes, including one that affects the results of XPath expressions. Improved documentation.