[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399479 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- The metro build is invoked every time, even when we had a successful build previously [tdiesler@tddell trunk]$ ./build.sh deploy-jboss500 .... [exec] BUILD SUCCESSFUL [exec] Total time: 1 minute 23 seconds [echo] ********************************* [echo] The metro binaries have been copied to 'thirdparty-gen' [echo] ********************************* You fix this, you can study the CXF build [tdiesler@tddell trunk]$ cat ant-import/build-thirdparty.xml | grep "target " <target name="thirdparty" depends="thirdparty-classpath"> <target name="thirdparty-init" depends="prepare"> <target name="thirdparty-get" depends="thirdparty-init, cxf-copy-jars" if="force.thirdparty.get" <target name="thirdparty-classpath" depends="thirdparty-get"> <target name="cxf-build" depends="cxf-copy-jars" description="Build Apache CXF from source"> <target name="cxf-checkout-dir" depends="thirdparty-init" unless="apache.cxf.available"> <target name="cxf-checkout-required" depends="cxf-checkout-dir" if="apache.cxf.available"> <target name="cxf-checkout" depends="cxf-checkout-required" if="cxf.checkout.required"> <target name="cxf-update-required" depends="thirdparty-init" if="apache.cxf.available"> <target name="cxf-update" depends="cxf-update-required" if="cxf.update.required" unless="cxf.checkout.required"> <target name="cxf-svn-info" depends="cxf-checkout,cxf-update"> <target name="cxf-maven-build" depends="cxf-svn-info" unless="cxf.build.available"> <target name="cxf-copy-jars" depends="cxf-maven-build"> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=all ] Thomas Diesler updated JBWS-1994: --------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399483 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- Rename all "sunri" references to "metro". Most importantly, the deployment should be called jbossws-metro.sar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399488 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- build-jars-jaxws: [war] Building war: /home/tdiesler/svn/jbossws/stack/metro/trunk/output/tests/libs/wsit-rm.war [war] Warning: selected war files include a WEB-INF/web.xml which will be ignored (please use webxml attribute to war task) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399492 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- The metro build uses cvs/wsit/wsit thirdparty-get checkout_id-metro1_1-release this should be simplified to glassfish-metro - wsit - output - build-marker-metro1_1-release hence requiring a single svn:ignore -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399495 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- Have a look at native build-release.xml Here is the svn:externals check <target name="check-svn-externals" depends="init"> <exec dir="${core.dir}/src/test-framework" executable="svn" failonerror="true" output="${core.dir}/output/svn-info.xml"> <arg line="info"/> <arg line="--xml"/> </exec> <xmlproperty file="${core.dir}/output/svn-info.xml"/> <condition property="framework.externals.ok"> <or> <contains string="${info.entry.url}" substring="jbossws/framework/tags"/> <equals arg1="${repository.id}" arg2="snapshot"/> </or> </condition> </target> <target name="warn-svn-externals" depends="init" unless="framework.externals.ok"> <echo> *********************************************** * External link to framework is not tagged! * * Run: svn pe svn:externals src * *********************************************** </echo> </target> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12399498 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- Release to portal is missing <!-- Release to portal content --> <target name="release-to-portal" depends="check-portal-content,build-src-dist,build-bin-dist" description="Release to portal-content" if="jbossws.portal.content.available"> As a result of which we currently have binary filenames that dont make much sense jbossws-3.0-metro-1.0.0.GA jbossws-3.0-cxf-1.0.0.GA jbossws-native-2.0.3.GA With the next release this should be jbossws-3.0.1-metro-1.0.x.GA jbossws-3.0.1-cxf-1.0.x.GA jbossws-3.0.1-native-2.0.x.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=all ] Thomas Diesler updated JBWS-1994: --------------------------------- Component/s: jbossws-metro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=all ] Thomas Diesler reopened JBWS-1994: ---------------------------------- The metro build needs to copy named artifacts to the thirdparty directory like this <!-- Copy the cxf jars --> <target name="cxf-copy-jars" depends="cxf-maven-build"> <mkdir dir="${thirdparty.dir}"/> <property name="cxf.distribution.lib" value="${apache.cxf.dir}/distribution/target/apache-cxf-${cxf.version}.dir/apache-cxf-${cxf.version}/lib"/> <available property="cxf.available" filepath="${cxf.distribution.lib}" file="cxf-${cxf.version}.jar"/> <available property="geronimo-javamail.available" filepath="${cxf.distribution.lib}" file="geronimo-javamail_${cxf.geronimo.javamail}.jar"/> <available property="geronimo-ws-metadata.available" filepath="${cxf.distribution.lib}" file="geronimo-ws-metadata_${cxf.geronimo.ws.metadata}.jar"/> <available property="jaxws-api.available" filepath="${cxf.distribution.lib}" file="jaxws-api-${cxf.jaxws.api}.jar"/> <available property="jetty.available" filepath="${cxf.distribution.lib}" file="jetty-${cxf.jetty}.jar"/> <available property="jetty-util.available" filepath="${cxf.distribution.lib}" file="jetty-util-${cxf.jetty}.jar"/> <available property="jdom.available" filepath="${cxf.distribution.lib}" file="jdom-${cxf.jdom}.jar"/> <available property="neethi.available" filepath="${cxf.distribution.lib}" file="neethi-${cxf.neethi}.jar"/> <available property="saaj-api.available" filepath="${cxf.distribution.lib}" file="saaj-api-${cxf.saaj}.jar"/> <available property="saaj-impl.available" filepath="${cxf.distribution.lib}" file="saaj-impl-${cxf.saaj}.jar"/> <available property="spring-beans.available" filepath="${cxf.distribution.lib}" file="spring-beans-${cxf.spring}.jar"/> <available property="spring-context.available" filepath="${cxf.distribution.lib}" file="spring-context-${cxf.spring}.jar"/> <available property="spring-core.available" filepath="${cxf.distribution.lib}" file="spring-core-${cxf.spring}.jar"/> <available property="xbean.available" filepath="${cxf.distribution.lib}" file="xbean-${cxf.xbean}.jar"/> <available property="xml-resolver.available" filepath="${cxf.distribution.lib}" file="xml-resolver-${cxf.xml.resolver}.jar"/> <available property="XmlSchema.available" filepath="${cxf.distribution.lib}" file="XmlSchema-${cxf.xmlschema}.jar"/> <fail message="cxf-${cxf.version}.jar not available" unless="cxf.available"/> <fail message="geronimo-javamail_${cxf.geronimo.javamail}.jar not available" unless="geronimo-javamail.available"/> <fail message="geronimo-ws-metadata_${cxf.geronimo.ws.metadata}.jar not available" unless="geronimo-ws-metadata.available"/> <fail message="jaxws-api-${cxf.jaxws.api}.jar not available" unless="jaxws-api.available"/> <fail message="jetty-${cxf.jetty}.jar not available" unless="jetty.available"/> <fail message="jetty-util-${cxf.jetty}.jar not available" unless="jetty-util.available"/> <fail message="jdom-${cxf.jdom}.jar not available" unless="jdom.available"/> <fail message="neethi-${cxf.neethi}.jar not available" unless="neethi.available"/> <fail message="saaj-api-${cxf.saaj}.jar not available" unless="saaj-api.available"/> <fail message="saaj-impl-${cxf.saaj}.jar not available" unless="saaj-impl.available"/> <fail message="spring-beans-${cxf.spring}.jar not available" unless="spring-beans.available"/> <fail message="spring-context-${cxf.spring}.jar not available" unless="spring-context.available"/> <fail message="spring-core-${cxf.spring}.jar not available" unless="spring-core.available"/> <fail message="xbean-${cxf.xbean}.jar not available" unless="xbean.available"/> <fail message="xml-resolver-${cxf.xml.resolver}.jar not available" unless="xml-resolver.available"/> <fail message="XmlSchema-${cxf.xmlschema}.jar not available" unless="XmlSchema.available"/> <copy todir="${thirdparty.dir}"> <fileset dir="${cxf.distribution.lib}"> <include name="cxf-${cxf.version}.jar"/> <include name="geronimo-javamail_${cxf.geronimo.javamail}.jar"/> <include name="geronimo-ws-metadata_${cxf.geronimo.ws.metadata}.jar"/> <include name="jaxws-api-${cxf.jaxws.api}.jar"/> <include name="jetty-${cxf.jetty}.jar"/> <include name="jetty-util-${cxf.jetty}.jar"/> <include name="jdom-${cxf.jdom}.jar"/> <include name="neethi-${cxf.neethi}.jar"/> <include name="saaj-api-${cxf.saaj}.jar"/> <include name="saaj-impl-${cxf.saaj}.jar"/> <include name="spring-beans-${cxf.spring}.jar"/> <include name="spring-context-${cxf.spring}.jar"/> <include name="spring-core-${cxf.spring}.jar"/> <include name="xbean-${cxf.xbean}.jar"/> <include name="xml-resolver-${cxf.xml.resolver}.jar"/> <include name="XmlSchema-${cxf.xmlschema}.jar"/> </fileset> </copy> </target> This should go in prepare-deploy <fileset dir="glassfish-metro/output"> <patternset refid="jbossws.client.patternset"/> <patternset refid="jbossws.lib.patternset"/> <patternset refid="jbossws.lib.endorsed.patternset"/> <patternset refid="jbossws.server.lib.patternset"/> <patternset refid="jbossws.service.lib.patternset"/> </fileset> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12402859 ] Thomas Diesler commented on JBWS-1994: -------------------------------------- The reason to copy named artifacts to the thirdparty directory instead of *.jar is that we can detect version conflicts and maintain compatibility version information in component-info.xml and the future maven build. Generally, we must be in control of every thirdparty artifact used by our deployments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=all ] Thomas Diesler updated JBWS-1994: --------------------------------- JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131833 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=all ] Thomas Diesler updated JBWS-1994: --------------------------------- Fix Version/s: jbossws-metro-1.0.1 (was: jbossws-metro-1.0.2) Please fix for 1.0.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1994?page=comments#action_12404367 ] Richard Opalka commented on JBWS-1994: -------------------------------------- Heiko, fix it for QA branch first so I could run release QA tests ASAP: https://svn.jboss.org/repos/jbossws/stack/metro/branches/jbossws-3.0.1-me... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira