Free spring software for linux

TA Spring is an open source project developing a new realtime strategy game.
Spring is a full 3D RTS game engine with good balanced content.
Games can be intense and the engine allows some diverse strategies.
At this moment the Spring engine is capable to run most (all) content that was available for the Total Annihilation engine.
Around 8 high profile mods have been made to run specificly on the Spring engine.
Spring is mainly a multi player game engine.
Some light AIs are available but they are not really challenging at this moment.
Spring runs on Windows and is stable. The Spring Linux ports runs alright but it cant connect to other Windows clients (yet) so Linux users are limited to single player.
The developers try to make Spring run natively on different platforms. (Windows, Linux, Mac and *BSD) And (try to) add features that modders request.
Main features:
- High resolution maps, viewable from all angles and ranges
- Dynamic map with craters from weapon and unit explosions
- Work with unit files from Total annihilation
- Realistic 3D trajectories for weapons
- Fully 3D air combat
- Several camera modes to suit different tastes
- Mod switcher
- Lobby Client
Enhancements:
- LUA related changes
- AI improvements
- balancing improvements
- lots of bugs fixed

Rhino in Spring is a project that intends to integrate Mozilla Rhino JavaScript interpreter, the interpreter for the best (in our opinion) dynamic language on the Java platform with Spring Framework, the also best (again, in our opinion) enterprise framework on the Java platform.
Rhino in Springs aim is to provide a system that amalgamates the rapid development benefits and flexibility of a dynamic language with the strength, scalability and versatility of the Java platform and the Spring framework.
At the moment, the project delivers a controller component for Spring MVC that allows complex control flows spanning several webpages in web applications to be expressed as a single structured algorithm in JavaScript, putting the rich set of control flow structures and function reusability of a full-blown language at your fingertips. It transparently maps the users requests to the correct points of execution in your JavaScript code, even as the user freely navigates your website using the browsers back button or even "File-New Window" functionality!
A flexible set of state persistence options (including one where all state management is shifted to the browser, for maximum server scalability) is included.
Enhancements:
- Added support for relative pathnames in include(), with backward compatible lookup of absolute pathnames
- Fixed bug when an implicitly created ScriptStorage wasnt properly initialized

Spring IDE for Eclipse project provides Eclipse plugins to ease working with Bean Factory configuration files for the Spring Framework.
It contains a Spring project nature (with an incremental builder for validating Spring bean config files), an image decorator (which decorates Spring projects and all Spring bean config files), a Spring view (which allows one to browse Spring projects and their Spring bean config files, including bean properties), and an editor showing a graph from the beans of a single config file or a set of config files.
Main features:
- Project nature which support a list of Spring bean config files and sets of bean config files (aka beans config sets)
- Incremental builder which validates all modified Spring bean config files defined in a Spring project
- View which displays a tree with all Spring projects and their Spring bean config files
- Image decorator which decorates all Spring projects, their bean config files and all Java classes which are used as bean classes
- Editor (read-only) which displays a graph from all beans defined in a single config file or a config set
- The following features are currently under development:
- Graphical editor for Spring Webflow configuration files
- XML editor for Spring beans configuration files
System requirements:
- Eclipse Project
- Spring
Installation:
- Open Eclipse. Go to Help -> Software Updates -> Find and Install.
- Select "Search for new features to install". Click "Next".
- Click "New Remote Site". Enter "Spring IDE updatesite" for the Name and "http://springide.org/updatesite/" for the URL (Screenshot). Click "OK".
- You should now see a a new entry name "Spring IDE updatesite" with a mark next to it (Screenshot). Click on that and check "Spring IDE".
- Click on the mark next to "Eclipse.org updatesite" and check the version of GEF which is sufficient for your version of Eclipse. Click "Next".
- Select the features "Graphical Editing Framework" and the lastest version of "Spring IDE" from the list. Click "Next".
- Check "I accept..." and click "Next". Select or add the appropriate site to install the features. Click "Finish".
- Click Install on the warning dialogs during feature verification (both features are not digitally signed).
- After successfully downloading and installing the features click "Yes" on the "Would you like to restart now?" dialog.

Spike Asset Manager (SAM) is an open-source cross-platform framework for probing a system for components and reporting them. It includes a driver file that probes for components commonly found in a LAMPJ stack (Apache, MySQL, PHP, Tomcat, etc).
SAM can find multiple versions that are installed, query the rpm database and indicate whether components are running. Driver files may be edited to search for different components.
SAM can be extended by writing extension plugins (shell, perl, python, java, etc). It can also be extended by changing the code and creating additional directives for the driver file.
The list of components that SAM currently looks for include:
- apache2
- axis
- commons-logging
- hibernate
- java
- jetspeed
- jboss
- log4j
- mysql
- openldap
- openssl
- perl
- php
- python
- spring
- struts
- tomcat
Enhancements:
- This development release adds a Web server.
- There is now an AJAX enabled Web client to perform what was previously done via command line.
- This allows a common interface (across operating systems) as well as local and remote administration. AJAX is made possible with integration through MochiKit and JSON.
- The Web site has also moved to the SpikeSource developer Web site.

Apache MINA comes from Multipurpose Infrastructure for Network Applications and is a network application framework which helps users develop high performance and high scalability network applications easily.
Main features:
- Unified API for various transport types:
- TCP/IP
- UDP/IP
- In-VM pipe communication
- You can implement your own!
- Low-level and high-level API:
- Low-level: uses ByteBuffers
- High-level: uses user-defined message objects and codecs
- Stream-based I/O support via StreamIoHandler
- Filter interface as an extension point; similar to Servlet filters
- SSL support via SSLFilter thanks to Java 5 SSLEngine
- Thread pools are implemented as filters so that users can customize thread model.
- Unit testability using mock objects,
- JMX managability, (coming soon)
- Traffic throttling, (coming soon)
- Overload shielding, (coming soon)
- Integration with well known containers such as Spring and OSGi, (coming soon)
- Smooth migration from Netty, a popular NIO framework. (See Netty Tutorial)
Enhancements:
- This release introduces a new API with an integrated I/O layer and protocol layer.
- New features include traffic control, StartTLS, out-of-the-box protocol codecs, and Spring framework integration.

Proximity project is a cross between an HTTP proxy and a pro-active mirror. One of its primary uses is as Web application to serve as a Maven proxy on a companys intranet.
As for reducing outgoing traffic (caching central and other maven repos), aggregating more repositories (reducing project config) with acting as one logical repository and for publishing in-house and other external maven artifacts which are not uploadable to ibiblio (like commercial projects, J2EE Jars, etc...).
Main features:
- 2-in-1 - With Proximity you can host your own private repo while proxying other repositories and have all the benefits of local (read FAST) repository access.
- Access control - Proximity is well suited for corporate deployments, since it has extensible and configurable AccessManager. Proximity has various AccessManager and AccessDecisionVoter implementations out-of-the-box. Some examples: IP based access restriction, HTTPS access only with client certificate verification and access management based on it. Access control may be configured on Proximity level and on repository level independently.
- HTTP, HTTPS and HTTP Proxy support - On its front, Proximity is unaware is it serving artifacts over plain HTTP or HTTPS (it is container setup, eg. Tomcat). On its back Proximity Remote Peer is powered with latest Jakarta Commons HttpClient thus has all the capabilities that Commons HttpClient has. HttpClient configuration is fully exposed through Spring context, allowing easy reconfiguration (like http proxy setup). Furthermore, by employing custom front-ends (the Servlet controller class) and appropriate AccessControl class Proximity is ready to fit any specific needs for authorization (authentication is left to container!).
- Locally reusable proxy storage - The local storage of defined repositories are complete on-demand-mirrors of real remote repositories, thus usable for republishing (eg. using simple HTTP server. But you will share only the currently downloaded artifacts then).
- Aggregating, but in a smart way - It is able to host multiple repositorties, and depending on config, they may or may not be proxied remote repositories. Proximity may be used to serve private artifacts (those not uploadable to central due to their licence) as well on local network only. Still, Proximity tracks and organizes downloaded artifacts separatly, following the origin of the artifact and not mixing them together.
- Piping - Thanx to smart aggregation, Proximity is able to form a pipe of its instances, thus for example on corporate network you may have one central Proximity on a machine with allowed fast outbound traffic, and multiple instances on local subnetworks where no direct outbound traffic is possible. Proximity will all way down to last instance in pipe follow and keep artifacts in separate storage, following their originating repository. Moreover, you will have to publish in house artifacts only in one place.
- Fresh as needed - Proximity can be persistent or not, as configured. Moreover, Proximity recognizes the following kinds of items: Maven Snapshots, Maven2 POMs, Maven2 metadata and the rest is "just" artifact. All of these kinds have independent timeout configuration. Thus, every of these item kinds can be: never updated once downloaded, always updated on request or timeouted. These are independent settings (per kind).
- Fast searches - With time, your Proximity storage will grow. Proximity uses Apache Lucene as its indexer to provide fast searches on repositories.
- Reusable software - Proximity Core is transport and J2EE technology unaware, this webapp you see is just a front-end for Proximity implemented using Springframework, Velocity and two controller class.
- Extensible - Proximity Core is extensible and usable in many different ways and containers. The author have used it in Spring framework container (this webapp actually) and in Codehaus Plexus container (together with embedded Maven2), SAS and/or Danube.
Enhancements:
- The WebDAV interface was fixed, which now enables deployment from Maven2.
- Other major fixes were made regarding maven2-repository.dev.java.net repository support, a snapshot update problem, the use of server MIME-types, and a problem where GZIP content encoding is requested from the remote peer but not handled.
- Furthermore, some minor code problems and 1.4.2 platform incompatibilies were fixed.

Jetspeed provides a JSR-168 compliant enterprise portal.
etspeed-2 is a full implementation of the Java Portlet API. It is fully compliant with the Portlet Specification 1.0 (JSR-168). It has passed the TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard.
Notable features include security components backed by LDAP and database implementations, and some robust administration interfaces. Custom portals can be built and deployed using the Jetspeed plugin for Maven.
Developers can use the Jetspeed PSML language to assemble portlets, and the Apache Portals Bridges project to bridge portals with existing technologies including Struts, JSF, PHP, and Perl.
For GUI designers, Jetspeed comes with several built-in templates used to decorate portals and portlets.
Main features:
- Fully compliant with Java Portlet API Standard 1.0 (JSR 168)
- Passed JSR-168 TCK Compatibility Test Suite
- J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy
- LDAP Support for User Authentication
- Spring-based Components and Scalable Architecture
- Configurable Pipeline Request Processor
- Auto Deployment of Portlet Applications
- Jetspeed Component Java API
- Jetspeed AJAX XML API
- Declarative Security Constraints and JAAS Database Security Policy
- Runtime Portlet API Standard Role-based Security
- Portal Content Management and Navigations: Pages, Menus, Folders, Links
- Multithreaded Aggregation Engine
- PSML Folder CMS Navigations, Menus, Links
- Jetspeed SSO (Single Sign-on)
- Rules-based Profiler for page and resource location
- Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2, Hypersonic
- Client independent capability engine (html, xhtml, wml,vml)
- Internationalization: Localized Portal Resources in 12 Languages
- Statistics Logging Engine
- Portlet Registry
- Full Text Search of Portlet Resources with Lucene
- User Registration
- Forgotten Password
- Rich Login and Password Configuration Management