rpm/bcel
SHA256
1
0
Fork 0
forked from pool/bcel
Code Pull Requests Activity

- Drop gpg-offline

Browse Source 
- Drop conditional for manual that is never triggered

OBS-URL: https://build.opensuse.org/package/show/Java:packages/bcel?expand=0&rev=21
This commit is contained in:
Tomáš Chvátal 2015-03-25 09:23:24 +00:00 committed by Git OBS Bridge
parent ddbba2492b
commit 1a44e44db2
2 changed files with 9 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bcel.changes
View File

@ -1,3 +1,9 @@
-------------------------------------------------------------------
Wed Mar 25 09:22:33 UTC 2015 - tchvatal@suse.com
- Drop gpg-offline
- Drop conditional for manual that is never triggered
-------------------------------------------------------------------
Tue Jul 8 10:59:06 UTC 2014 - tchvatal@suse.com

45
bcel.spec
View File

@ -1,7 +1,7 @@
#
# spec file for package bcel
#
# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@ -16,7 +16,6 @@
#
%define manual 0
Name: bcel
Version: 5.2
Release: 0
@ -28,7 +27,6 @@ Source0: http://www.apache.org/dist/commons/bcel/source/%{name}-%{version
Source1: http://www.apache.org/dist/commons/bcel/source/%{name}-%{version}-src.tar.gz.asc
Source2: bcel.keyring
BuildRequires: ant
BuildRequires: gpg-offline
BuildRequires: java-1_5_0-gcj-compat-devel
BuildRequires: regexp
#BuildRequires: xerces-j2-bootstrap
@ -64,38 +62,7 @@ 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.
%if %{manual}
%package manual
Summary: Manual for bcel
Group: Development/Libraries/Java
%description manual
This package contains the manual for 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.
%endif
%prep
%gpg_verify %{SOURCE1}
%setup -q
# remove all binary libs
find . -name "*.jar" -exec rm -f {} \;
@ -106,8 +73,8 @@ touch manifest.txt
%build
export CLASSPATH=%(build-classpath regexp)
export OPT_JAR_LIST="ant/ant-nodeps"
%{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} compile
ant -Dbuild.dest=./build -Dbuild.dir=./build -Dname=%{name} jar
%install
# jars
@ -120,10 +87,4 @@ install -m 644 target/%{name}-%{version}.jar %{buildroot}%{_javadir}/%{name}-%{v
%doc LICENSE.txt
%{_javadir}/*
%if %{manual}
%files manual
%defattr(0644,root,root,0755)
%doc docs/*
%endif
%changelog