Apache Projects
< Java, OSGI, Eclipse
< psyal
Get flash to fully experience Pearltrees
Easy to use, affordable, and over 300% faster, Open Source Java Enterprise Edition of popular Apache Tomcat application server ideally suited for Cloud environments The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 150 Open Source projects and initiatives, today announced Apache TomEE v1.0. Apache TomEE... High-performance, fault-tolerant Open Source "Big Data" powerhouse scales petabytes of data at Adobe, Cisco, IBM, Morningstar, Netflix, PBS, Rackspace, Twitter, US Government, and more. Forest Hill, MD –24 April 2012– The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 150 Open Source projects and initiatives, today...
The Logging Component When writing a library it is very useful to log information. However there are many logging implementations out there, and a library cannot impose the use of a particular one on the overall application that the library is a part of. The Logging package is an ultra-thin bridge between different logging implementations. A library that uses the commons-logging API can be used with any logging implementation at runtime. Commons-logging comes with support for a number of popular logging implementations, and writing adapters for others is a reasonably simple task.
Commons CLI The Apache Commons CLI library provides an API for parsing command line options passed to programs. It's also able to print help messages detailing the options available for a command line tool. usage: ls -A,--almost-all do not list implied . and ..
Apache log4j 1.3 alpha releases are in limited use. Apache log4j 1.3 added many interesting features, but was compatibility with log4j 1.2 was problematic. Many features original developed for log4j 1.3 have been back-ported as companions for log4j 1.2.
log4j is probably the most common logging framework in use in the Java world. Even if a project/framework uses commons-logging most deployments configure log4j to be the underlying logger. log4j is usually configured via a properties file (most common, in my experience) or an XML file (more powerful).
Apache Ant™ Apache Ant is a Java library and command-line tool whose mission is to drive processes described in build files as targets and extension points dependent upon each other. The main known usage of Ant is the build of Java applications. Ant supplies a number of built-in tasks allowing to compile, assemble, test and run Java applications. Ant can also be used effectively to build non Java applications, for instance C or C++ applications. More generally, Ant can be used to pilot any type of process which can be described in terms of targets and tasks.
We just released the second milestone of Ant4Eclipse containing some new features and bug fixes. You can download the release from our Sourceforge Website at http://sourceforge.net/projects/ant4eclipse/files/ .
Rationale Executing external processes from Java is a well-known problem area. It is inheriently platform dependent and requires the developer to know and test for platform specific behaviors, for example using cmd.exe on Windows or limited buffer sizes causing deadlocks. The JRE support for this is very limited, albeit better with the new Java SE 1.5 ProcessBuilder class. Reliably executing external processes can also require knowledge of the environment variables before or after the command is executed. In J2SE 1.1-1.4 there is not support for this, since the method, System.getenv() , for retriving environment variables is deprecated.