From 28baf80275c939fa0d377f954dbc6d6f13c4dd0de946a6a89e4c4463093a108d Mon Sep 17 00:00:00 2001
From: Michal Vyskocil <michal.vyskocil@gmail.com>
Date: Thu, 22 Aug 2013 12:08:43 +0000
Subject: [PATCH] - disable javadoc generation - remove xerces-j2-bootstrap
 dependency (bnc#789163)

OBS-URL: https://build.opensuse.org/package/show/Java:packages/bcel?expand=0&rev=14
---
 bcel.changes |  7 ++++++-
 bcel.spec    | 41 -----------------------------------------
 2 files changed, 6 insertions(+), 42 deletions(-)

diff --git a/bcel.changes b/bcel.changes
index 3839803..1e9f7c1 100644
--- a/bcel.changes
+++ b/bcel.changes
@@ -1,7 +1,12 @@
+-------------------------------------------------------------------
+Thu Aug 22 12:08:11 UTC 2013 - mvyskocil@suse.com
+
+- disable javadoc generation 
+
 -------------------------------------------------------------------
 Mon Jan  7 12:16:54 UTC 2013 - mvyskocil@suse.com
 
-- remove xerces-j2-bootstrap depenency (bnc#789163)
+- remove xerces-j2-bootstrap dependency (bnc#789163)
 
 -------------------------------------------------------------------
 Tue May 15 07:59:18 UTC 2012 - mvyskocil@suse.cz
diff --git a/bcel.spec b/bcel.spec
index fec5828..84cd907 100644
--- a/bcel.spec
+++ b/bcel.spec
@@ -67,39 +67,6 @@ It contains a byte code verifier named JustIce, which usually gives you
 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 @@ touch manifest.txt
 %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