openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

File bcel.spec of Package bcel (Revision d66b57fa51edeacc540730529c11c3aa)

Currently displaying revision d66b57fa51edeacc540730529c11c3aa , Show latest

#
# spec file for package bcel
#
# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
# icecream 0

%define manual  0

Name:           bcel
Version:        5.2
Release:        0
Summary:        Byte Code Engineering Library
License:        Apache-2.0
Group:          Development/Libraries/Java
Source0:        http://www.apache.org/dist/commons/bcel/source/%{name}-%{version}-src.tar.gz
Source1:        http://www.apache.org/dist/commons/bcel/source/%{name}-%{version}-src.tar.gz.asc
Source2:        bcel.keyring
Url:            http://commons.apache.org/proper/commons-bcel/
Requires:       regexp
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build

BuildRequires:  ant
BuildRequires:  gpg-offline
BuildRequires:  java-1_5_0-gcj-compat-devel
BuildRequires:  regexp
#BuildRequires:  xerces-j2-bootstrap
#!BuildIgnore:  xerces-j2-bootstrap
BuildRequires:  xml-commons-apis-bootstrap
#!BuildIgnore:  xml-commons-apis xml-commons-resolver xml-commons xerces-j2
#!BuildIgnore:  xml-commons-jaxp-1.3-apis
#!BuildIgnore:  java-1_6_0-openjdk-devel
#!BuildIgnore:  java-1_7_0-openjdk-devel
BuildRequires:  ant-nodeps

%description
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
that 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, transformed by a
program (such as a class loader at runtime), and dumped to a file
again. An even more interesting application is the creation of classes
from scratch at runtime. 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 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 {} \;
# very broken build
perl -p -i -e 's| depends=\"examples\"||g;' build.xml
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

%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)

%files
%defattr(0644,root,root,0755)
%doc LICENSE.txt 
%{_javadir}/*

%if %manual

%files manual
%defattr(0644,root,root,0755)
%doc docs/*
%endif
# -----------------------------------------------------------------------------

%changelog

Places

File bcel.spec of Package bcel (Revision d66b57fa51edeacc540730529c11c3aa)

Places