Name: | excalibur |
---|---|
Epoch: | 1 |
Version: | 1.0 |
Release: | 0.r508111.13.jpp5 |
Architecture: | noarch |
Group: | Development/Java |
Size: | 199502 |
License: | ASL 2.0 |
RPM: | excalibur-1.0-0.r508111.13.jpp5.noarch.rpm |
Source RPM: | excalibur-1.0-0.r508111.13.jpp5.src.rpm |
Build Date: | Fri Sep 06 2013 |
Build Host: | ca-build7.us.oracle.com |
Vendor: | Oracle America |
URL: | http://excalibur.apache.org/ |
Summary: | Excalibur IOC Frameworks, Containers, Components |
Description: | Excalibur is a platform for component and container applications built on key design patterns such as Inversion of Control and Separation of Concerns available for the Java platform. You can use Excalibur to build any number of other applications from desktop centric Swing apps to complicated servers. The Avalon Framework (the core of Excalibur) is often used as the "underpinning" of a larger application or platform. Such applications include Apache Cocoon, Apache James, and the Keel Framework. Excalibur is not part of the J2EE stack. While Excalibur can be used in developing J2EE applications and even used to build a J2EE server, the platform is not part of J2EE or a J2EE application server. Excalibur is much simpler and does not include many J2EE specifications out of the box. That said, you might write a J2EE application which embeds Excalibur (such as in a servlet) or you may embed a J2EE server in a larger Excalibur-based container. The Excalibur platform is the following: * A core framework for component programming (The Avalon Framework) * An IoC container called Fortress * A set of container utilities called ContainerKit * A component library called Cornerstone When working with Excalibur you may use one or all of these. |
- fix build on JDK5
- fix build on JDK6
- fix logkit component info
- fix logkit component info
- remove %{_javadir}/avalon-logkit.jar symlink - main package owns %{_libdir}/gcj/%{name}
- Restore versionless symlinks for excalibur/avalon-framework*
- fix repolib versions
- add repolib packages for avalon-framework and avalon-logkit - remove Provides: avalon-framework and change jar location - remove Provides: avalon-logkit since it's in a different location - fix javadoc package Requires - properly unpack sources - fix maven directory ownership
- remove Vendor and Distribution - update License - update BuildRoot - remove javadoc scriptlets - use more strict file permissions - GCJ fixes - do not set JAVA_HOME
- Fix cornerstone-modules depmap frag - Build with maven2-2.0.7
- Fix depmap frag for monolithic avalon-framework - Add alternate depmap frags for avalon-framework and -logkit - Add (B)Rs
- Add more poms - Bump epoch
- Fix changelog
- Fix changelog
- Fix changelog
- Fix changelog
- Fix changelog
- First JPP-1.7 build from this codebase