rpms/jcip-annotations/F-8 jcip-annotations.spec, NONE, 1.1 sources, 1.1, 1.2

[Jerry James (jjames)]

Author: jjames

Update of /cvs/extras/rpms/jcip-annotations/F-8
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14836/F-8

Modified Files:
	sources 
Added Files:
	jcip-annotations.spec 
Log Message:
Initial import to F-8 and F-9 branches.



--- NEW FILE jcip-annotations.spec ---
Name:           jcip-annotations
Version:        0
Release:        20060626.4%{?dist}
Summary:        Java annotations for multithreaded software

Group:          Development/Libraries/Java
License:        CC-BY
URL:            http://www.jcip.net/
Source0:        http://www.jcip.net/%{name}-src.jar
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

# There is no point in building native libraries, as the sources contain only
# annotation definitions, so no code would be generated.
BuildArch:      noarch
BuildRequires:  java-devel >= 1.5.0, jpackage-utils

Requires:       java >= 1.5.0, jpackage-utils

%description
This package provides class, field, and method level annotations for
describing thread-safety policies.  These annotations are relatively
unintrusive and are beneficial to both users and maintainers.  Users can see
immediately whether a class is thread-safe, and maintainers can see
immediately whether thread-safety guarantees must be preserved.  Annotations
are also useful to a third constituency: tools.  Static code-analysis tools
may be able to verify that the code complies with the contract indicated by
the annotation, such as verifying that a class annotated with @Immutable
actually is immutable.

%package javadoc
Group:          Development/Documentation
Summary:        Javadoc for jcip-annotations
Requires:       %{name} = %{version}-%{release}, jpackage-utils

%description javadoc
Javadoc documentation for the jcip-annotations package.
On systems where javadoc is sinjdoc, this package contains nothing useful
since sinjdoc does not understand annotations.

%prep
%setup -q -c

# Get rid of the manifest created upstream with ant
rm -fr META-INF

# Fix DOS line endings
sed -i 's/\r//' net/jcip/annotations/package.html

%build
mkdir classes
find . -type f -name '*.java' | xargs javac -g -source 1.5 -target 1.5 -d classes
cd classes
jar cf ../%{name}-%{version}.jar net
cd ..
ln -s %{name}-%{version}.jar %{name}.jar
javadoc -d docs -source 1.5 net.jcip.annotations

%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT%{_javadir}
mv *.jar $RPM_BUILD_ROOT%{_javadir}
mkdir -p $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
cp -pr docs/* $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
ln -s %{name}-%{version} $RPM_BUILD_ROOT%{_javadocdir}/%{name}

%clean
rm -rf $RPM_BUILD_ROOT

%files
%defattr(-,root,root,-)
%{_javadir}/%{name}-%{version}.jar
%{_javadir}/%{name}.jar

%files javadoc
%defattr(-,root,root,-)
%{_javadocdir}/%{name}-%{version}
%{_javadocdir}/%{name}

%changelog
* Mon May  5 2008 Jerry James <loganjerry at gmail.com> - 0-20060626.4
- Don't package source or HTML files in the jar

* Fri Apr 18 2008 Jerry James <loganjerry at gmail.com> - 0-20060626.3
- Changes required by new Java packaging guidelines

* Wed Nov 14 2007 Jerry James <loganjerry at gmail.com> - 0-20060626.2
- Don't make the javadocs appear in a docs subdirectory

* Tue Sep 18 2007 Jerry James <loganjerry at gmail.com> - 0-20060626.1
- Initial RPM


Index: sources
===================================================================
RCS file: /cvs/extras/rpms/jcip-annotations/F-8/sources,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sources	6 May 2008 16:16:00 -0000	1.1
+++ sources	6 May 2008 16:55:52 -0000	1.2
@@ -0,0 +1 @@
+0a63cc4bca4a045aa56f3a12857857ea  jcip-annotations-src.jar