Name: buildnumber-maven-plugin Version: 1.0 Release: %mkrel 2 Summary: Build Number Maven Plugin Group: Development/Java License: MIT # svn export http://svn.codehaus.org/mojo/tags/buildnumber-maven-plugin-1.0 buildnumber-maven-plugin URL: http://svn.codehaus.org/mojo/tags/buildnumber-maven-plugin-1.0 # tar caf buildnumber-maven-plugin-1.0.tar.xz buildnumber-maven-plugin Source0: buildnumber-maven-plugin-1.0.tar.xz Source1: %{name}-depmap.xml Patch0: 0001-Add-source-and-target-version-for-compiler.patch Patch1: 0002-Remove-maven-scm-provider-svnjava-dependency.patch BuildArch: noarch # Basic stuff BuildRequires: jpackage-utils BuildRequires: java-devel >= 0:1.6.0 # Maven and its dependencies BuildRequires: maven BuildRequires: maven2-common-poms BuildRequires: maven-plugin-plugin BuildRequires: maven-idea-plugin BuildRequires: maven-resources-plugin BuildRequires: maven-compiler-plugin BuildRequires: maven-install-plugin BuildRequires: maven-javadoc-plugin BuildRequires: maven-jar-plugin BuildRequires: maven-enforcer-plugin BuildRequires: maven-invoker-plugin BuildRequires: maven-doxia BuildRequires: maven-doxia-tools BuildRequires: maven-doxia-sitetools BuildRequires: maven-surefire-provider-junit BuildRequires: maven-surefire-maven-plugin BuildRequires: maven-plugin-cobertura BuildRequires: plexus-containers-component-javadoc BuildRequires: svnkit BuildRequires: jna BuildRequires: mojo-parent # can be removed once maven is rebuilt with proper BR/R BuildRequires: apache-commons-parent Requires: java Requires: maven2 Requires: jna Requires: svnkit Requires: jpackage-utils Requires: mojo-parent Requires(post): jpackage-utils Requires(postun): jpackage-utils %description This mojo is designed to get a unique build number for each time you build your project. So while your version may remain constant at 1.0-SNAPSHOT for many iterations until release, you will have a build number that can uniquely identify each build during that time. The build number is obtained from scm, and in particular, at this time, from svn. You can then place that build number in metadata, which can be accessed from your app, if desired. The mojo also has a couple of extra functions to ensure you get the proper build number. First, your local repository is checked to make sure it is up to date. Second, your local repository is automatically updated, so that you get the latest build number. Both these functions can be suppressed, if desired. Optionally, you can configure this mojo to produce a revision based on a timestamp, or on a sequence, without requiring any interaction with an SCM system. Note that currently, the only supported SCM is subversion. %package javadoc Group: Development/Java Summary: Javadoc for %{name} Requires: jpackage-utils %description javadoc API documentation for %{name}. %prep %setup -q -n %{name} %patch0 -p1 %patch1 -p1 %build # tests skipped due to invoker problems with local repository tests mvn-rpmbuild -DskipTests=true \ -Dmaven.local.depmap.file=%{SOURCE1} \ -Dmaven.test.skip=true \ install javadoc:javadoc %install # jars install -d -m 0755 %{buildroot}%{_javadir} install -m 644 target/%{name}-%{version}.jar %{buildroot}%{_javadir}/%{name}.jar %add_to_maven_depmap org.codehaus.mojo buildnumber-maven-plugin %{version} JPP buildnumber-maven-plugin # poms install -d -m 755 %{buildroot}%{_mavenpomdir} install -pm 644 pom.xml \ %{buildroot}%{_mavenpomdir}/JPP-%{name}.pom # javadoc install -d -m 0755 %{buildroot}%{_javadocdir}/%{name} cp -pr target/site/api*/* %{buildroot}%{_javadocdir}/%{name} %pre javadoc # workaround for rpm bug, can be removed in F-17 [ $1 -gt 1 ] && [ -L %{_javadocdir}/%{name} ] && \ rm -rf $(readlink -f %{_javadocdir}/%{name}) %{_javadocdir}/%{name} || : %post %update_maven_depmap %postun %update_maven_depmap %files %defattr(-,root,root,-) %doc LICENSE.txt %{_javadir}/* %{_mavenpomdir}/* %{_mavendepmapfragdir}/* %files javadoc %defattr(-,root,root,-) %doc LICENSE.txt %{_javadocdir}/%{name} %changelog * Thu Apr 28 2011 dmorgan <dmorgan> 1.0-2.mga1 + Revision: 92409 - Rebuild after bootstrapping - imported package buildnumber-maven-plugin * Mon Apr 18 2011 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1.0-1 - Update to latest upstream - Build with maven 3 - Tweaks according to new guidelines - Versionless jars & javadocs * Tue Feb 08 2011 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 1.0-0.11.b4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild * Thu Nov 11 2010 Stanislav Ochotnicky <sochotnicky@redhat.com> - 1.0-0.10.b4 - Added mojo-parent to BR/R * Wed Sep 1 2010 Alexander Kurtakov <akurtako@redhat.com> 1.0-0.9.b4 - Fix build and use new maven plugins names. * Thu Jun 17 2010 Alexander Kurtakov <akurtako@redhat.com> 1.0-0.8.b4 - BR maven2-common-poms. * Thu Jun 17 2010 Alexander Kurtakov <akurtako@redhat.com> 1.0-0.7.b4 - Disable it-tests and changes plugin. * Thu Jun 17 2010 Alexander Kurtakov <akurtako@redhat.com> 1.0-0.6.b4 - Skip tests to be able to rebuild. * Thu Jun 17 2010 Alexander Kurtakov <akurtako@redhat.com> 1.0-0.5.b4 - Add missing requires. * Thu May 27 2010 Weinan Li <weli@redhat.com> - 1.0-0.4.b4 - License.txt and Readme.txt added as %%doc * Thu May 27 2010 Weinan Li <weli@redhat.com> - 1.0-0.3.b4 - Fix javadoc dangling-relative-symlink * Wed May 26 2010 Weinan Li <weli@redhat.com> - 1.0-0.2.b4 - Add requires on jpackage-utils for javadoc subpackage - Add standard jpackage-utils requires on main package - Use global instead of define - Fix license to MIT - fix incoherent-version-in-changelog * Mon May 24 2010 Weinan Li <weli@redhat.com> - 1.0-0.1.b4 - Initial package