Name: izpack Version: 4.3.5 Release: 1%{?dist} Summary: An installers generator for the Java platform Group: Development/Libraries License: ASL 2.0 Url: http://izpack.org/ # git clone git://github.com/jponge/izpack.git izpack-4.3.5 # cd izpack-4.3.5/ && git archive --format=tar --prefix=izpack-4.3.5/ v4.3.5 | xz > ../izpack-4.3.5.tar.xz Source0: izpack-%{version}.tar.xz Source1: izpack-compiler-%{version}.pom Source2: izpack-installer-%{version}.pom Source3: izpack-izevent-%{version}.pom Source4: izpack-standalone-compiler-%{version}.pom Source5: izpack-uninstaller-%{version}.pom Source6: izpack-uninstaller-ext-%{version}.pom Patch0: izpack-%{version}-do_not_copy_native.patch # renove Class-Path from mainfest Patch1: izpack-%{version}-build_xml.patch BuildRequires: java-devel BuildRequires: jpackage-utils BuildRequires: ant BuildRequires: ant-junit BuildRequires: bsf BuildRequires: junit BuildRequires: regexp # manual deps BuildRequires: python-docutils BuildRequires: texlive Requires: java Requires: jpackage-utils BuildArch: noarch %description IzPack is an installers generator for the Java platform. It produces lightweight installers that can be run on any operating system where a Java virtual machine is available. Depending on the operating system, it can be launched by a double-click or a simple 'java -jar installer.jar' on a shell. The most common use is to distribute applications for the Java platform, but you can also use it for other kinds of projects. The main benefit of IzPack is that it provides a clean and unique way of distributing a project to users using different operating systems. IzPack is reported to run on : * Unix-like systems, mostly Linux and BSD * MacOS X * Windows variants A big care has been put in making IzPack as small as possible in order to reduce the weight of IzPack itself in the final installer archive. Also, IzPack has been designed around modularity and flexibility. As a consequence, you are able to specify how your installer should be by selecting the panels that you want to show to the final user. Sometimes there are even several panels for the same usage so that you can pick the one that suits the best your needs. If ever you don't find your way through the available panels, you can still develop your own ones with the nice and easy IzPack API. There's even an embedded XML parser ! %package demo Group: Development/Libraries Summary: Samples for %{name} %description demo This package contains samples for %{name}. %package javadoc Group: Documentation Summary: Javadoc for %{name} Requires: jpackage-utils %description javadoc This package contains javadoc for %{name}. %package manual Group: Documentation License: CC-BY-SA Summary: Manual for %{name} %description manual This package contains manual for %{name}. %prep %setup -q # clean up find . -name '*.bat' -delete find . -name '*.class' -delete find . -name '*.dll' -delete find . -name '*.jar' -type f -delete find . -name '.cvsignore' -delete find . -name '.gitignore' -delete rm -rf doc/izpack/javadoc/* doc/nanoxml/* %patch0 -p0 %patch1 -p0 pushd lib ln -sf $(build-classpath regexp) jakarta-regexp-1.3.jar ln -sf $(build-classpath ant) . ln -sf $(build-classpath bsf) . popd for s in src/lib/com/izforge/izpack/adaptator/impl/XMLElementImpl.java \ src/lib/com/izforge/izpack/installer/PanelActionFactory.java \ src/lib/com/izforge/izpack/installer/PanelAction.java;do native2ascii -encoding UTF8 ${s} ${s} done %build cd src ant all build.javadoc build.docu %install mkdir -p %{buildroot}%{_javadir}/%{name} install -m 644 lib/compiler.jar %{buildroot}%{_javadir}/%{name}/ install -m 644 lib/installer.jar %{buildroot}%{_javadir}/%{name}/ install -m 644 lib/izevent.jar %{buildroot}%{_javadir}/%{name}/ install -m 644 lib/standalone-compiler.jar %{buildroot}%{_javadir}/%{name}/ install -m 644 lib/uninstaller-ext.jar %{buildroot}%{_javadir}/%{name}/ install -m 644 lib/uninstaller.jar %{buildroot}%{_javadir}/%{name}/ mkdir -p %{buildroot}%{_mavenpomdir} install -pm 644 %{SOURCE1} %{buildroot}%{_mavenpomdir}/JPP.%{name}-compiler.pom %add_maven_depmap JPP.%{name}-compiler.pom %{name}/compiler.jar install -pm 644 %{SOURCE2} %{buildroot}%{_mavenpomdir}/JPP.%{name}-installer.pom %add_maven_depmap JPP.%{name}-installer.pom %{name}/installer.jar install -pm 644 %{SOURCE3} %{buildroot}%{_mavenpomdir}/JPP.%{name}-izevent.pom %add_maven_depmap JPP.%{name}-izevent.pom %{name}/izevent.jar install -pm 644 %{SOURCE4} %{buildroot}%{_mavenpomdir}/JPP.%{name}-standalone-compiler.pom %add_maven_depmap JPP.%{name}-standalone-compiler.pom %{name}/standalone-compiler.jar install -pm 644 %{SOURCE5} %{buildroot}%{_mavenpomdir}/JPP.%{name}-uninstaller.pom %add_maven_depmap JPP.%{name}-uninstaller.pom %{name}/uninstaller.jar install -pm 644 %{SOURCE6} %{buildroot}%{_mavenpomdir}/JPP.%{name}-uninstaller-ext.pom %add_maven_depmap JPP.%{name}-uninstaller-ext.pom %{name}/uninstaller-ext.jar mkdir -p %{buildroot}%{_javadocdir}/%{name} cp -rp _build/javadoc/* %{buildroot}%{_javadocdir}/%{name} rm -rf bin/native mkdir -p %{buildroot}%{_datadir}/%{name} cp -a bin %{buildroot}%{_datadir}/%{name}/ chmod 755 %{buildroot}%{_datadir}/%{name}/bin/langpacks/checklangpack chmod 755 %{buildroot}%{_datadir}/%{name}/bin/langpacks/installer/testLangpacks.ksh cp -a sample %{buildroot}%{_datadir}/%{name}/ mkdir -p %{buildroot}%{_docdir}/%{name} #cp -rp doc/izpack/pdf/* cp -a doc/izpack/html %{buildroot}%{_docdir}/%{name}/ %files %dir %{_javadir}/%{name} %{_javadir}/%{name}/*.jar %{_mavenpomdir}/JPP.%{name}-*.pom %{_mavendepmapfragdir}/%{name} %doc License.txt NOTICE Readme.txt %files demo %dir %{_datadir}/%{name} %{_datadir}/%{name}/* %doc License.txt NOTICE %files javadoc %{_javadocdir}/%{name} %doc License.txt NOTICE %files manual %dir %{_docdir}/%{name} %doc %{_docdir}/%{name}/html/* %doc License.txt NOTICE %changelog * Sat Aug 18 2012 gil cattaneo 4.3.5-1 - initial rpm