excalibur-lifecycle-api-2.2.1-4.7 > t
D H ` p JG/= ` 2,&-Kyn
NE>ҨS9O@; @
fn C u~E~<0>(Ae|JD?+ʰat5woᱯAȶg +9oRo
ꦯ5&9L4"MEwO!ǢG1-dŧR^msk*
}ziQ$VLգ3iMn|H=还{ڲ`BF5ͮn1+⛜etaMԩd62ea3ea351a5ea5ff407fdf8ddc24825ca64e0f JG/=CvQ2+uАn^ܪP340kd:d8?h%Ra98?f_O DOS5 |G"_,vL<x͛DN4w7e!K'!$O ŹyWP@]DaE L4|];|/`2d.(j=NH#W,%AG)Wd xMKI=3@x#
k g<qM$''t. > 9 ? d $ U l p x | ( ,
0 8 Z
( 8 9 :
>
@
F G H $ I , X 0 Y 4 \ @ ] H ^ b c d o e t f y l { z C excalibur-lifecycle-api 2.2.1 4.7 Excalibur IOC Frameworks, Containers, Components 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. Jrbuild30 openSUSE 11.2 openSUSE Apache Software License .. http://bugs.opensuse.org Development/Libraries/Java http://excalibur.apache.org/ linux noarch
echo -e "\n" > /etc/maven/maven2-depmap.xml
if [ -d /etc/maven/fragments ] && [ -n "`find /etc/maven/fragments -type f`" ]; then
cat /etc/maven/fragments/* >> /etc/maven/maven2-depmap.xml
fi
echo -e "\n" >> /etc/maven/maven2-depmap.xml
echo -e "\n" > /etc/maven/maven2-depmap.xml
if [ -d /etc/maven/fragments ] && [ -n "`find /etc/maven/fragments -type f`" ]; then
cat /etc/maven/fragments/* >> /etc/maven/maven2-depmap.xml
fi
echo -e "\n" >> /etc/maven/maven2-depmap.xml ! J{JD3dbea6b5498707478c0f70a1140f6b20 excalibur-lifecycle-api-2.2.1.jar root root root root excalibur-0.91.r508111-4.7.src.rpm excalibur-lifecycle-api
excalibur excalibur-avalon-framework-api /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) rpmlib(CompressedFileNames) rpmlib(PayloadIsLzma) 1.0 4.3.1 4.0-1 3.0.4-1 4.4.6-1 4.7.1 J@JęJJ
Y@mvyskocil@suse.cz mvyskocil@suse.cz mvyskocil@suse.cz mvyskocil@suse.cz - Added excalibur-rpmlintrc to sources - Added license-wrapper.txt to docdir of excalibur-fortress-platform
to met the tanukiwrapper license requirements. - Fixed requires - 'Initial SUSE packaging of excalibur (from jpackage.org 5.0)' /bin/sh /bin/sh build30 1257084530 x 2.2.1-4.7 excalibur-lifecycle-api-2.2.1.jar excalibur-lifecycle-api.jar /usr/share/java/excalibur/ -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g obs://build.opensuse.org/openSUSE:11.2/standard/5edd3452c1ca2b22c0e657ec4e579191-excalibur cpio lzma 2 noarch-suse-linux ')Um7$Lv ? p ]
b2p @@!VH1k f#@7pxDzu؈7~8gV/WTx[- Rmt+Du7e%wz MX"f. t! 2e9*_I霢F1,&SxvZ0t Nx{/
X(WLZP{pZx/NP$) :֠Vȇ3=P9.⭪p,oT2ʜSou,Bv6W
|gzZwLCw3KR+dGbڲH
F4 Ip-XA#uҕ ؛k>kZZCb& XfHi_]ugO氹Y}@|T5P&'e#Qo;Ol.`Gc{HE()n ȃ m@N);xVh&[j6AtZ︯H\7^pLxKM
oL:CZ}Dſ^+fJLBC6#*7Zd