Hello community, here is the log from the commit of package bcel for openSUSE:Factory checked in at 2013-08-23 11:05:53 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/bcel (Old) and /work/SRC/openSUSE:Factory/.bcel.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "bcel" Changes: -------- --- /work/SRC/openSUSE:Factory/bcel/bcel.changes 2013-01-08 13:32:52.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.bcel.new/bcel.changes 2013-08-23 11:05:55.000000000 +0200 @@ -1,0 +2,5 @@ +Thu Aug 22 12:08:11 UTC 2013 - [email protected] + +- disable javadoc generation + +------------------------------------------------------------------- @@ -4 +9 @@ -- remove xerces-j2-bootstrap depenency (bnc#789163) +- remove xerces-j2-bootstrap dependency (bnc#789163) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ bcel.spec ++++++ --- /var/tmp/diff_new_pack.VLrkPC/_old 2013-08-23 11:05:55.000000000 +0200 +++ /var/tmp/diff_new_pack.VLrkPC/_new 2013-08-23 11:05:55.000000000 +0200 @@ -67,39 +67,6 @@ much better information about what is wrong with your code than the standard JVM message. - - -%package javadoc -PreReq: coreutils -Summary: Javadoc for bcel -Group: Development/Libraries/Java - -%description javadoc -This package contains the javadoc documentation of the Byte Code -Engineering Library. - -The Byte Code Engineering Library is intended to give users a -convenient way to analyze, create, and manipulate (binary) Java class -files (those ending with .class). Classes are represented by objects -which contain all the symbolic information of the given class: methods, -fields and byte code instructions, in particular. - -Such objects can be read from an existing file, be transformed by a -program (e.g. a class loader at run-time) and dumped to a file again. -An even more interesting application is the creation of classes from -scratch at run-time. The Byte Code Engineering Library (BCEL) may also -be useful if you want to learn about the Java Virtual Machine (JVM) and -the format of Java .class files. - -BCEL is already being used successfully in several projects such as -compilers, optimizers, obfuscators, code generators and analysis tools. - -It contains a byte code verifier named JustIce, which usually gives you -much better information about what's wrong with your code than the -standard JVM message. - - - %if %manual %package manual @@ -144,28 +111,20 @@ %build export CLASSPATH=%(build-classpath regexp) export OPT_JAR_LIST="ant/ant-nodeps" -export LC_ALL="en_US.UTF-8" # necessary for javadoc %ant -Dbuild.dest=./build -Dbuild.dir=./build -Dname=%{name} compile %ant -Dbuild.dest=./build -Dbuild.dir=./build -Dname=%{name} jar -%ant -Dbuild.dest=./build -Dbuild.dir=./build -Dname=%{name} javadoc %install # jars %__mkdir_p %{buildroot}%{_javadir} %__install -m 644 target/%{name}-%{version}.jar %{buildroot}%{_javadir}/%{name}-%{version}.jar (cd %{buildroot}%{_javadir} && for jar in *-%{version}*; do %__ln_s ${jar} `echo $jar| sed "s|-%{version}||g"`; done) -# javadoc -%__mkdir_p %{buildroot}%{_javadocdir}/%{name}-%{version} -%__cp -a dist/docs/api/* %{buildroot}%{_javadocdir}/%{name}-%{version} %files %defattr(0644,root,root,0755) %doc LICENSE.txt %{_javadir}/* -%files javadoc -%defattr(0644,root,root,0755) -%{_javadocdir}/%{name}-%{version} %if %manual %files manual -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
