[wise: 2/10] Fix spec file for this package

[Gerard Ryan]

commit 88b6195953a25d83873477048187c544ba58f66c
Author: Gerard Ryan <gerard at ryan.lt>
Date:   Sun Aug 4 20:55:26 2013 +0100

    Fix spec file for this package

 wise.spec |   87 +++++++++++++++++++++++++++++++++++-------------------------
 1 files changed, 51 insertions(+), 36 deletions(-)
---
diff --git a/wise.spec b/wise.spec
index 9edd94a..3b03458 100644
--- a/wise.spec
+++ b/wise.spec
@@ -1,60 +1,75 @@
+%global reltag Final
+
 Name:           wise
-Version:        2.0.3.Final
+Version:        2.0.3
 Release:        1%{?dist}
-Summary:        Wise
+Summary:        JBoss Wise: 'Wise invokes services easily'
 
-Group:          Development/Libraries
-License:        GNU Lesser General Public License, v. 2.1
-URL:            http://www.jboss.org/wise
-Source0:        #FIXME
+License:        LGPLv2+
+URL:            http://www.jboss.org/%{name}
+Source0:        http://download.jboss.org/%{name}/%{name}-distribution-%{version}.%{reltag}.zip
 BuildArch: noarch
 
+BuildRequires: maven-local
 
 %description
-Wise Core
+Wise is a Java framework for easily invoking webservices, which can be used as
+base for zero-code webservice invocation applications. Wise can be the proper
+solution when total and effective client/server decoupling through WS is
+required.
+
+While basic JAX-WS tool for wsdl-to-java generation (like wsconsume) are great
+for most Java developer usecases, the generated stub classes kind of introduce
+a new (or renewed :)) level of coupling very similar to Corba IDL; by
+generating statical webservice stubs you actually couple client and server.
+
+So what is the alternative? Writing dynamic client using dynamic
+Provider/Dispatch JAX-WS API? That's possibly an option, yet not the easiest
+to understand, implement and maintain in most enterprise environments. Wise
+provides a different solution using dynamic mapping on JAX-WS tools generated
+code. Wise allows calling a ws service by mapping a generic Object model to
+JAXWS generated code. This opens up multiple Wise usage scenarios, like
+zero-code WS invocation (used in JBoss ESB) or GUI driven WS invocation.
 
 %package javadoc
-Group:          Documentation
 Summary:        Javadoc for %{name}
-Requires:       jpackage-utils
 
 %description javadoc
 API documentation for %{name}.
 
+%package core
+Summary: JBoss Wise Core
 
-%prep
-%setup -q #You may need to update this according to your Source0
+%description core
+It is a library to simplify web service invocation from a client point of view:
+it aims at providing a near zero-code solution to find and parse wsdls, select
+service and endpoint and call operations mapping user defined object model to
+JAX-WS objects required to perform the call.
 
-%build
-mvn-rpmbuild \
-        -e \
-        install javadoc:javadoc
+%package core-cxf
+Summary: JBoss Wise Core CXF
 
-%install
-# jars
-install -d -m 0755 %{buildroot}%{_javadir}
-install -m 644 target/%{name}-%{version}.jar   %{buildroot}%{_javadir}/%{name}.jar
+%description core-cxf
+%{summary}.
 
-# poms
-install -d -m 755 %{buildroot}%{_mavenpomdir}
-install -pm 644 pom.xml \
-    %{buildroot}%{_mavenpomdir}/JPP.%{name}.pom
+%prep
+%setup -qn %{name}-%{version}.%{reltag}/src
 
-%add_maven_depmap JPP.%{name}.pom %{name}.jar
+find ../ -name '*.class' -delete
+find ../ -name '*.jar' -delete
 
-# javadoc
-install -d -m 0755 %{buildroot}%{_javadocdir}/%{name}
-cp -pr target/site/api*/* %{buildroot}%{_javadocdir}/%{name}/
-rm -rf target/site/api*
+%build
+# Tests fail because of different hamcrest versions
+%mvn_build -s --skip-tests
 
-%files
-%{_javadir}/*
-%{_mavenpomdir}/*
-%{_mavendepmapfragdir}/*
+%install
+%mvn_install
 
-%files javadoc
-%{_javadocdir}/%{name}
+%files -f .mfiles-wise
+%files javadoc -f .mfiles-javadoc
+%files core -f .mfiles-%{name}-core
+%files core-cxf -f .mfiles-%{name}-core-cxf
 
 %changelog
-
-#FIXME
+* Mon Jul 29 2013 Gerard Ryan <galileo at fedoraproject.org> - 2.0.3-1
+- Initial package.