Use OSGi API JARs to run BND classpath, instead of Eclipse

This commit is contained in:
Mikolaj Izdebski 2016-10-10 18:56:09 +02:00
parent 68e789f59d
commit e1d8362a92

View File

@ -1,6 +1,6 @@
Name: objectweb-asm
Version: 5.1
Release: 5%{?dist}
Release: 6%{?dist}
Summary: Java bytecode manipulation and analysis framework
License: BSD
URL: http://asm.ow2.org/
@ -33,7 +33,7 @@ find -name *.jar -delete
sed -i /Class-Path/d archive/*.bnd
sed -i "s/Import-Package:/&org.objectweb.asm,org.objectweb.asm.util,/" archive/asm-xml.bnd
sed -i "s|\${config}/biz.aQute.bnd.jar|`build-classpath aqute-bnd slf4j/api slf4j/simple eclipse/osgi.services`|" archive/*.xml
sed -i "s|\${config}/biz.aQute.bnd.jar|`build-classpath aqute-bnd slf4j/api slf4j/simple osgi-core osgi-compendium`|" archive/*.xml
sed -i -e '/kind="lib"/d' -e 's|output/eclipse|output/build|' .classpath
%build
@ -58,6 +58,9 @@ done
%license LICENSE.txt
%changelog
* Mon Oct 10 2016 Mikolaj Izdebski <mizdebsk@redhat.com> - 5.1-6
- Use OSGi API JARs to run BND classpath, instead of Eclipse
* Sat Sep 24 2016 Mikolaj Izdebski <mizdebsk@redhat.com> - 5.1-5
- Update to current packaging guidelines
- Remove obsoletes and provides for objectweb-asm4