Free apache 1.1 software for linux

Apache Solr is a high performace search server based on Lucene, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, and a Web administration interface.
The project is currently under incubation at the Apache Software Foundation.
Instructions for Building Apache Solr
1. Download the J2SE 5.0 JDK (Java Development Kit) or later from http://java.sun.com. You will need the JDK installed, and the %JAVA_HOME%bin directory included on your command path. To test this, issue a "java -version" command from your shell and verify that the Java version is 5.0 or later.
2. Download the Apache Ant binary distribution from http://ant.apache.org. You will need Ant installed and the %ANT_HOME%bin directory included on your command path. To test this, issue a "ant -version" command from your shell and verify that Ant is available.
3. Download the Apache Solr source distribution, linked from the above incubator web site. Expand the distribution to a folder of your choice, e.g. c:solr.
4. Navigate to that folder and issue an "ant" command to see the available options for building, testing, and packaging solr.
Enhancements:
- This is the first release since graduating from the Apache Incubator.
- Some of the new features include CSV/delimited-text data loading, time based autocommit, faster faceting, negative filters, a spell-check handler, sounds-like word filters, regex text filters, and more flexible plugins.

Apache Ant is a Java based build tool, similar to make, but with better support for the cross platform issues involved with developing Java applications.
Apache Ant is the build tool of choice for all Java projects at Apache and many other Open Source Java projects.
Enhancements:
- A resource framework was introduced.
- Some of the core ant tasks such as copy are now able to process not only file system resources but also zip entries, tar entries, and paths.
- Resource collections group resources, and can be further combined with operators such as union and intersection.
- This version starts outsourcing of optional tasks to Antlibs.
- The .NET antlib replaces the .NET optional tasks.
- Support for the version control system Subversion is also provided as an antlib.
- A large number of bugs were fixed.
- Some initial support for Java6 features was added.

Apache MyFaces is the first free open source Java Server Faces implementation.

What is Java Server Faces (JSF)?

Java Server Faces is a new and upcoming web application framework that accomplishes the MVC paradigm. It is comparable to the well-known Struts Framework but has features and concepts that are beyond those of Struts - especially the component orientation.

Look at Suns JSF Page to learn more about the Java Specification Request 127 and to download the specification. You can also find a useful Tutorial there!

Quickstart

Make sure to have a look at our examples - you can find a working distribution here.
Find instructions on installing them yourselves in our Getting Started section. If you cant find information you need on these pages, make sure you also go to our WIKI

Apache::PageKit is a MVCC web framework using mod_perl, XML and HTML::Template.

SYNOPSIS

In httpd.conf

SetHandler perl-script
PerlSetVar PKIT_ROOT /path/to/pagekit/files
PerlSetVar PKIT_SERVER staging

PerlHandler +Apache::PageKit
< Perl>
Apache::PageKit->startup(/path/to/pagekit/files, staging);
< /Perl>
In MyPageKit/Common.pm
package MyPageKit::Common;

use base Apache::PageKit::Model;

sub pkit_dbi_connect {
return DBI->connect("DBI:mysql:db","user","passwd");
}

sub pkit_session_setup {
my $model = shift;
my $dbh = $model->dbh;
return {
session_lock_class => MySQL,
session_store_class => MySQL,
session_args => {
Handle => $dbh,
LockHandle => $dbh,
},
};
}

sub pkit_auth_credential {
my ($model) = @_;

# in this example, login and passwd are the names of the credential fields
my $login = $model->input(login);
my $passwd = $model->input(passwd);

# create a session key
# your code here.........

return $ses_key;
}

sub pkit_auth_session_key {
my ($model, $ses_key) = @_;

# check whether $ses_key is valid, if so return user id in $user_id
# your code here.........

return $ok ? $user_id : undef;
}

Gump is Apaches continuous integration tool. Apache Gump is written in python and fully supports Apache Ant, Apache Maven and other build tools. Gump is unique in that it builds and compiles software against the latest development versions of those projects. This allows gump to detect potentially incompatible changes to that software just a few hours after those changes are checked into the version control system. Notifications are sent to the project team as soon as such a change is detected, referencing more detailed reports available online.

You can set up and run Gump on your own machine and run it on your own projects, however it is currently most famous for building most of Apaches java-based projects and their dependencies (which constitutes several million lines of code split up into hundreds of projects). For this purpose, the gump project maintains its own dedicated server.

How does Gump work?

With Traditional Gump, project definitions are converted from XML to scripts native to the platform on which you are running. With Python Gump the XML is mapped into in memory objects for processing. Scripts execute cvs or svn update commands for every module which contains a project being built, and invoke builds for each project in an order that ensures that dependencies are satisfied. Build outputs are processed and, if successful, dependent projects are then built on these outputs.

The commands use the actual build.xml files from the projects, but do not use the scripts or jar files checked into CVS/SVN. Instead, the CLASSPATH is set and properties are passed on the command line.

Note

Gump sets Ants build.sysclasspath to only and manages the system classpath:
To quote Ant: Only the system classpath is used and classpaths specified in build files, etc are ignored. This situation could be considered as the person running the build file knows more about the environment than the person writing the build file

The net effect is that every project is built every day with the latest version of every dependency - including the latest Ant, latest JUnit, latest XML parser.

The results are captured into html pages that largely are consistent with the style of the Jakarta project. An extensive amount of hypertext links are added to allow quick and easy navigation, and failures are color coded on the main build page.

A Perl script which is driven off of a naglist will optionally send e-mails to various newsgroups upon matching strings being found in the build output. This is typically used to alert developers of build failures.

Apache OFBiz is an open source enterprise automation software project licensed under the Apache License Version 2.0.
By open source enterprise automation we mean: Open Source ERP, Open Source CRM, Open Source E-Business / E-Commerce, Open Source SCM, Open Source MRP, Open Source CMMS/EAM, and so on.
Main features:
- advanced e-commerce
- catalog management
- promotion & pricing management
- order management (sales & purchase)
- customer management (part of general party management)
- warehouse management
- fulfillment (auto stock moves, batched pick, pack & ship)
- accounting (invoice, payment & billing accounts, fixed assets)
- manufacturing management
- general work effort management (events, tasks, projects, requests, etc)
- content management (for product content, web sites, general content, blogging, forums, etc)
- and much more all in an open source package!

Apache mod_suid allows per-vhost execution of scripts under their own UIDs. It functions in a way similar to Apaches perchild MPM, but differs in a number of ways.

Apache mod_suid does per child user/group switching; the Apache MPM makes switches based on vhosts. All processing is done under a specific UID/GID, including PHP and mod_perl scripts.