JBoss Tools SVN: r22104 - trunk/bpel/docs/reference/en-US/modules.
by jbosstools-commits＠lists.jboss.org
Author: ochikvina
Date: 2010-05-15 10:51:11 -0400 (Sat, 15 May 2010)
New Revision: 22104
Modified:
trunk/bpel/docs/reference/en-US/modules/install.xml
Log:
<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/browse/TOOLSDOC-48 - Updated "Installation JBoss BPEL Runtime" section and added the info about the prerequisites. </p>
</body></html>
Modified: trunk/bpel/docs/reference/en-US/modules/install.xml
===================================================================
--- trunk/bpel/docs/reference/en-US/modules/install.xml 2010-05-15 12:50:13 UTC (rev 22103)
+++ trunk/bpel/docs/reference/en-US/modules/install.xml 2010-05-15 14:51:11 UTC (rev 22104)
@@ -12,11 +12,35 @@
Please, note, that only JBoss Tools 3.1 or higher version includes JBoss BPEL editor.
</para>
</section>
+ <section>
+ <title>Prerequisites</title>
+ <para>For installation and configuring BPEL engine into a JBossAS environment
+ you will need the following: </para>
+ <itemizedlist>
+ <listitem><para> JBossAS (version 5.1.0.GA or higher),
+ available from <ulink url="http://www.jboss.org/jbossas">
+ http://www.jboss.org/jbossas</ulink>.</para></listitem>
+ <listitem><para>RiftSaw (version 2.0 or higher), available from <ulink url="http://www.jboss.org/riftsaw">http://www.jboss.org/riftsaw</ulink>.</para></listitem>
+ <listitem><para>Ant, available from <ulink url="http://ant.apache.org">here</ulink>.</para></listitem>
+ </itemizedlist>
+
+ </section>
<section id="installRuntime">
<title>Installation JBoss BPEL Runtime</title>
- <para>If you want to deploy a BPEL project to JBoss server,
- you should download JBoss BPEL Runtime by yourself. The JBoss BPEL Runtime
- is named RiftSaw. You can get it from <ulink url="http://jboss.org/riftsaw">JBoss RiftSaw page </ulink>.
- </para>
+ <itemizedlist>
+ <listitem><para>Unpack the JBossAS installation archive into the required location.Then in the
+ <property>${RiftSaw}/install</property> folder run the command:
+ <property>ant deploy -Ddatabase=hsql -Dws.stack=native -Dws.version=3.2.2.GA</property>
+ It will help you to download the web service stack, and then upgrade it for JBoss AS.
+ </para></listitem>
+ <listitem><para>Unpack the RiftSaw distribution into the location alongside the JBossAS installation.
+ * Edit the <property>install/deployment.properties</property> file to update the JBossAS location settings.
+ * From the <property>install</property> folder, run: <property>ant deploy -Ddatabase=hsql</property>
+ to deploy RiftSaw to JBossAS.
+ </para></listitem>
+ </itemizedlist>
+
+
+
</section>
</chapter>
\ No newline at end of file
15 years, 11 months
JBoss Tools SVN: r22103 - trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-05-15 08:50:13 -0400 (Sat, 15 May 2010)
New Revision: 22103
Added:
trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2a.png
trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2b.png
Log:
https://jira.jboss.org/browse/TOOLSDOC-11 - Updated the doc according to new functionality added to Project Examples. Added new images.
Added: trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2a.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2a.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2b.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/GettingStartedGuide/en-US/images/project_examples/pr_example_2b.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
15 years, 11 months
JBoss Tools SVN: r22102 - trunk/documentation/guides/GettingStartedGuide/en-US.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-05-15 08:49:33 -0400 (Sat, 15 May 2010)
New Revision: 22102
Modified:
trunk/documentation/guides/GettingStartedGuide/en-US/project_examples.xml
Log:
https://jira.jboss.org/browse/TOOLSDOC-11 - Updated the doc according to new functionality added to Project Examples.
Modified: trunk/documentation/guides/GettingStartedGuide/en-US/project_examples.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/project_examples.xml 2010-05-15 12:46:52 UTC (rev 22101)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/project_examples.xml 2010-05-15 12:49:33 UTC (rev 22102)
@@ -119,6 +119,31 @@
</mediaobject>
</figure>
+
+ <para>Some project examples have dependencies which could not be automatically configured.
+ In such cases you will receive the message prompted about detected requirements (see the figure below).</para>
+
+ <figure>
+ <title>Prompt about Project Example Requirements</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/project_examples/pr_example_2a.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>You should click <emphasis><property>Details</property></emphasis> to see the list of requirements
+ and make fixes.</para>
+
+ <figure>
+ <title>Requirements Details Dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/project_examples/pr_example_2b.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
<para>If you have previously specified user sites (see the <link linkend="UserSites">User Sites</link> chapter) they also will be displayed in the list of project examples in the category that was defined in the xml file with user sites settings. </para>
<figure>
<title>User Site</title>
15 years, 11 months
JBoss Tools SVN: r22101 - trunk/esb/docs/esb_ref_guide/en-US/images/esb_project.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-05-15 08:46:52 -0400 (Sat, 15 May 2010)
New Revision: 22101
Added:
trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/05a_esb_project_example.png
Log:
https://jira.jboss.org/jira/browse/TOOLSDOC-11 - Updated the doc according to ESB for SOA-P 5.0 examples added.
Added: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/05a_esb_project_example.png
===================================================================
(Binary files differ)
Property changes on: trunk/esb/docs/esb_ref_guide/en-US/images/esb_project/05a_esb_project_example.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
15 years, 11 months
JBoss Tools SVN: r22100 - trunk/jmx/docs/reference/en-US.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-05-15 07:51:21 -0400 (Sat, 15 May 2010)
New Revision: 22100
Modified:
trunk/jmx/docs/reference/en-US/tasks.xml
Log:
https://jira.jboss.org/jira/browse/TOOLSDOC-49
added imageshttps://jira.jboss.org/jira/browse/TOOLSDOC-49
Managing Application is updated
Modified: trunk/jmx/docs/reference/en-US/tasks.xml
===================================================================
--- trunk/jmx/docs/reference/en-US/tasks.xml 2010-05-15 11:50:38 UTC (rev 22099)
+++ trunk/jmx/docs/reference/en-US/tasks.xml 2010-05-15 11:51:21 UTC (rev 22100)
@@ -37,9 +37,13 @@
-<para>Like it's said earlier in the guide the JMX technology allows to monitor and manage Java applications. In this section we will show you how to get connected to
+<para>As it's been said earlier in the guide the JMX technology allows to monitor and manage Java applications. In this section we will show you how to get connected to
a sample Java application and run the <property>sayHello()</property> method remotely from inside of the <property>MBean Explorer</property>.</para>
<orderedlist>
+
+http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip
+
+<listitem><para>Save the bundle of JMX API sample classes, <ulink url="http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip">jmx_examples.zip</ulink>, to your working directory</para></listitem>
<listitem><para>Unzip the bundle of sample classes.</para></listitem>
<listitem><para>Compile the example Java classes from within where you unpacked the files directory.</para>
@@ -86,6 +90,14 @@
service:jmx:rmi:///jndi/rmi://:9999/jmxrmi
]]></programlisting>
+ <figure>
+ <title>JMX Connection</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/mbeans.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
</listitem>
<listitem><para>Press <property>Finish</property> to esteblish the connection with the application.</para>
@@ -97,6 +109,15 @@
</listitem>
<listitem><para>In the <property>MBean Editor</property> go to the <property>Operation Details</property> section and hit the <property>sayHello()</property> button.</para><para> You will get the "Operation inoked successfully" message. </para>
+
+ <figure>
+ <title>Ivoking Method via JMX</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/invokemethod.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
</listitem>
<listitem><para>The final step is to make sure the application worked as it was expected. Open the terminal where you launched the application in step 3. Now you see the "hello, world" message on the screen. </para>
15 years, 11 months
JBoss Tools SVN: r22099 - trunk/jmx/docs/reference/en-US/images.
by jbosstools-commits＠lists.jboss.org
Author: abogachuk
Date: 2010-05-15 07:50:38 -0400 (Sat, 15 May 2010)
New Revision: 22099
Added:
trunk/jmx/docs/reference/en-US/images/equinox.png
trunk/jmx/docs/reference/en-US/images/invokemethod.png
trunk/jmx/docs/reference/en-US/images/mbeans.png
Log:
https://jira.jboss.org/jira/browse/TOOLSDOC-49
added images
Added: trunk/jmx/docs/reference/en-US/images/equinox.png
===================================================================
(Binary files differ)
Property changes on: trunk/jmx/docs/reference/en-US/images/equinox.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jmx/docs/reference/en-US/images/invokemethod.png
===================================================================
(Binary files differ)
Property changes on: trunk/jmx/docs/reference/en-US/images/invokemethod.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/jmx/docs/reference/en-US/images/mbeans.png
===================================================================
(Binary files differ)
Property changes on: trunk/jmx/docs/reference/en-US/images/mbeans.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
15 years, 11 months
JBoss Tools SVN: r22098 - branches/modular_build/build.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2010-05-15 02:43:44 -0400 (Sat, 15 May 2010)
New Revision: 22098
Modified:
branches/modular_build/build/build.xml
Log:
debug why maven keeps dying
Modified: branches/modular_build/build/build.xml
===================================================================
--- branches/modular_build/build/build.xml 2010-05-15 06:15:14 UTC (rev 22097)
+++ branches/modular_build/build/build.xml 2010-05-15 06:43:44 UTC (rev 22098)
@@ -688,6 +688,7 @@
</else>
</if>
<!-- 3 hr timeout = 10800000ms -->
+ <echo level="info">${mvnExe} ${MAVEN_FLAGS} ${maven.repo.local}</echo>
<exec executable="${COMMON_TOOLS}/apache-maven-${maven.version}/bin/${mvnExe}"
dir="${MAVEN_DIR}"
failifexecutionfails="true"
@@ -698,7 +699,7 @@
<env key="MAVEN_OPTS" value="-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m" />
<!-- more debug output with <env key="MAVEN_OPTS" value="-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000"/> -->
<!-- <arg line="-o -Dmaven.test.skip" /> -->
- <arg line="${MAVEN_FLAGS} -Dmaven.repo.local=${COMMON_TOOLS}/m2-repository" />
+ <arg line="${MAVEN_FLAGS} ${maven.repo.local}" />
</exec>
</target>
15 years, 11 months
JBoss Tools SVN: r22097 - branches/modular_build/build.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2010-05-15 02:15:14 -0400 (Sat, 15 May 2010)
New Revision: 22097
Modified:
branches/modular_build/build/build.xml
Log:
remove svn revert before update so that local source changes in workspace won't be overwritten
Modified: branches/modular_build/build/build.xml
===================================================================
--- branches/modular_build/build/build.xml 2010-05-15 05:46:18 UTC (rev 22096)
+++ branches/modular_build/build/build.xml 2010-05-15 06:15:14 UTC (rev 22097)
@@ -325,9 +325,11 @@
/>
</then>
</if>
+ <!--
<svn javahl="false" svnkit="true" failonerror="false">
<revert recurse="${svn.recurse}" dir="@{component}" />
</svn>
+ -->
<svn javahl="false" svnkit="true" failonerror="false">
<update recurse="${svn.recurse}" dir="@{component}" />
</svn>
15 years, 11 months
JBoss Tools SVN: r22096 - branches/modular_build/build.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2010-05-15 01:46:18 -0400 (Sat, 15 May 2010)
New Revision: 22096
Modified:
branches/modular_build/build/build.xml
Log:
rename any leftover site.zip files when collecting results
Modified: branches/modular_build/build/build.xml
===================================================================
--- branches/modular_build/build/build.xml 2010-05-15 04:10:56 UTC (rev 22095)
+++ branches/modular_build/build/build.xml 2010-05-15 05:46:18 UTC (rev 22096)
@@ -65,14 +65,13 @@
or, to (re-)run tests w/o (re-)building first:
ant -DMAVEN_FLAGS="osgi-test:test -B -fn"
-or, to build specific module(s):
+or, to build, test, and install 1 or more specific module(s):
ant -DCOMPONENTS=tests,common,flow,jbpm
-or, to re-build a single component's update site w/o first building, testing, and installing it into the m2 repo:
- ant -DCOMPONENT=jmx create.update.site; \
- ant -DCOMPONENT=jbpm create.update.site
+or, to re-build a single component's update site w/o building, testing, and installing it into the m2 repo:
+ ant -DCOMPONENT=jmx create.update.site
-or, to re-build the overall update site w/o building first:
+or, to re-build the overall update site w/o building first (no applicable when COMPONENTS=.):
ant create.overall.update.site -Dbuild.if.sources.unchanged=true
To have hudson manage sources (rather than having this script checkout/update them) use:
@@ -536,6 +535,12 @@
</echo>
</then>
</elseif>
+ <elseif>
+ <equals arg1="${COMPONENTS.to.build}" arg2=".," />
+ <then>
+ <property name="no.overall" value="true" />
+ </then>
+ </elseif>
</if>
</then>
<else>
@@ -629,11 +634,16 @@
</else>
</if>
- <!-- prevent recursion: overall site component is built with create.overall.update.site, not simpler create.update.site -->
+ <!-- prevent recursion: overall site component is built with create.overall.update.site, not simpler create.update.site; also, don't rebuild the site if it's already been done by "." component -->
<if>
- <not>
- <equals arg1="@{COMPONENT}" arg2="site" />
- </not>
+ <and>
+ <not>
+ <equals arg1="@{COMPONENT}" arg2="site" />
+ </not>
+ <not>
+ <equals arg1="@{COMPONENT}" arg2="." />
+ </not>
+ </and>
<then>
<antcall target="create.update.site">
<param name="COMPONENT" value="@{COMPONENT}" />
@@ -853,9 +863,14 @@
</else>
</if>
<if>
- <not>
- <contains string="${COMPONENTS.to.check}" substring=",site" />
- </not>
+ <and>
+ <not>
+ <equals arg1="${COMPONENTS.to.check}" arg2="." />
+ </not>
+ <not>
+ <contains string="${COMPONENTS.to.check}" substring=",site" />
+ </not>
+ </and>
<then>
<var name="COMPONENTS.to.check" value="${COMPONENTS.to.check},site" />
</then>
@@ -863,8 +878,46 @@
<for param="COMPONENT" list="${COMPONENTS.to.check}" delimiter=",;
">
<sequential>
+ <!-- rename any leftover site.zip files -->
<for param="updateZip">
<path>
+ <fileset dir="${WORKINGDIR}/@{COMPONENT}" includes="**/site.zip" />
+ </path>
+ <sequential>
+ <if>
+ <equals arg1="@{COMPONENT}" arg2="site" />
+ <then>
+ <var name="destinationZip"
+ value="${WORKINGDIR}/(a){COMPONENT}/site/target/JBossTools-ALL-Update-SNAPSHOT.zip"
+ />
+ </then>
+ <else>
+ <var name="COMPONENT.name" value="" />
+ <if>
+ <equals arg1="@{COMPONENT}" arg2="." />
+ <then>
+ <var name="COMPONENT.name" value="${product.id}" />
+ </then>
+ <else>
+ <var name="COMPONENT.name" value="@{COMPONENTS}" />
+ </else>
+ </if>
+ <var name="destinationZip"
+ value="${WORKINGDIR}/(a){COMPONENT}/site/target/JBossTools-${COMPONENT.name}-Update-SNAPSHOT.zip"
+ />
+ </else>
+ </if>
+ <!-- rename resulting update site zip -->
+ <move file="${WORKINGDIR}/(a){COMPONENT}/site/target/site.zip"
+ tofile="${destinationZip}"
+ overwrite="true"
+ preservelastmodified="false"
+ />
+ </sequential>
+ </for>
+
+ <for param="updateZip">
+ <path>
<fileset dir="${WORKINGDIR}/@{COMPONENT}" includes="**/JBossTools*Update*.zip" />
</path>
<sequential>
@@ -985,8 +1038,18 @@
/>
</then>
<else>
+ <var name="COMPONENT.name" value="" />
+ <if>
+ <equals arg1="${COMPONENT}" arg2="." />
+ <then>
+ <var name="COMPONENT.name" value="${product.id}" />
+ </then>
+ <else>
+ <var name="COMPONENT.name" value="${COMPONENTS.to.build}" />
+ </else>
+ </if>
<var name="destinationZip"
- value="${WORKINGDIR}/${update.site.path}/target/JBossTools-${COMPONENTS.to.build}-Update-SNAPSHOT.zip"
+ value="${WORKINGDIR}/${update.site.path}/target/JBossTools-${COMPONENT.name}-Update-SNAPSHOT.zip"
/>
</else>
</if>
@@ -1067,7 +1130,7 @@
</if>
</target>
- <!-- Used to build the update site of a component; requires a site.xml and pom.xml be generated first -->
+ <!-- Used to build the update site of a component; requires a site.xml and pom.xml be generated first, if not already checked in -->
<target name="create.update.site" depends="init">
<var name="site.pom.exists" unset="true" />
<condition property="site.pom.exists">
15 years, 11 months
JBoss Tools SVN: r22095 - branches/modular_build/build.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2010-05-15 00:10:56 -0400 (Sat, 15 May 2010)
New Revision: 22095
Modified:
branches/modular_build/build/build.xml
Log:
tweak examples to make more generic and backport changes from teiid designer version: do not do overall site if component='.'; do no overwrite existing site/{pom,site}.xml; do not delete site/ dir if component='.'
Modified: branches/modular_build/build/build.xml
===================================================================
--- branches/modular_build/build/build.xml 2010-05-15 04:06:57 UTC (rev 22094)
+++ branches/modular_build/build/build.xml 2010-05-15 04:10:56 UTC (rev 22095)
@@ -1,27 +1,27 @@
-<project default="run" basedir="." name="jbosstools build.xml">
- <!-- Build a given list of ${COMPONENTS} -->
-
+<project default="run" basedir="." name="build.xml to wrap maven">
<!-- ****************************** Configuration ****************************** -->
- <!-- set name of component(s) to build+test, IN ORDER -->
+ <!-- default maven version -->
+ <property name="maven.version" value="3.0-beta-1" />
+
+ <!-- set name of component(s) to build+test, IN ORDER; if no subcomponents, use "." -->
<property name="COMPONENTS"
value="tests,common;
flow,jbpm;
jmx,archives,as;
- drools,bpel,smooks,freemarker,profiler,portlet;
+ drools,bpel,smooks,freemarker,profiler,portlet,modeshape;
xulrunner,jst,vpe,jsf;
esb,tptp,ws;
cdi,struts,hibernatetools,seam;
examples,birt;
maven"
/>
- <!-- TODO: add modeshape, which reqs JDK6 -->
<!-- svn root, including trunk or branch path -->
<property name="svn.root" value="http://anonsvn.jboss.org/repos/jbosstools/branches/modular_build" />
- <!-- default maven version -->
- <property name="maven.version" value="3.0-beta-1" />
+ <!-- if true, use -Dmaven.repo.local=${COMMON_TOOLS}/m2-repository; if false, use default ~/.m2/repository; or set another path if preferred -->
+ <property name="maven.repo.local" value="true" />
<!-- name/version we're building -->
<property name="product.name" value="JBoss Tools" />
@@ -34,6 +34,7 @@
-->
<!-- TODO: connect build type (snapshot, milestone, release) to update site description (nightly, milestone, stable) -->
+ <!-- update site description :: not used if site.xml already present -->
<property name="update.site.description" value="Nightly Build" />
<!-- ****************************** Usage Instructions ****************************** -->
@@ -43,45 +44,37 @@
Run As > Ant Build
To run this script via commandline (build default modules + run tests, then collect test results and build per-component + overall update site zips):
- cd /home/nboldt/workspace36/jbosstools-modular_build; ant
+ cd /path/to/checked/out/source/tree; ant
or, to build everything but not *run* the tests:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
ant -DMAVEN_FLAGS="clean install -Dmaven.test.skip"
or
ant -Dnotests=true
or, to purge the local repo (or purge then build):
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
ant purge -q
or
ant clean-run
-or, to build specific module(s):
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
- ant -DCOMPONENTS=tests,common,flow,jbpm
-
or, to rebuild even if sources have not changed:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
- ant -DCOMPONENTS=tests,common -Dbuild.if.sources.unchanged=true
+ ant -Dbuild.if.sources.unchanged=true
or, to fetch fresh sources, then build anew:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
- ant -DCOMPONENTS=tests,common,flow,jbpm -Dclean.sources=true
+ ant -Dclean.sources=true
or, to (re-)run tests w/o (re-)building first:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
- ant -DCOMPONENTS=tests,common,jmx -DMAVEN_FLAGS="osgi-test:test -B -fn"
+ ant -DMAVEN_FLAGS="osgi-test:test -B -fn"
+or, to build specific module(s):
+ ant -DCOMPONENTS=tests,common,flow,jbpm
+
+or, to re-build a single component's update site w/o first building, testing, and installing it into the m2 repo:
+ ant -DCOMPONENT=jmx create.update.site; \
+ ant -DCOMPONENT=jbpm create.update.site
+
or, to re-build the overall update site w/o building first:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
ant create.overall.update.site -Dbuild.if.sources.unchanged=true
-or, to re-build a single component's update site w/o first building, testing, and installing it into the m2 repo:
- cd /home/nboldt/workspace36/jbosstools-modular_build; \
- ant -DCOMPONENT=jmx create.update.site; \
- ant -DCOMPONENT=jbpm create.update.site
-
To have hudson manage sources (rather than having this script checkout/update them) use:
-Dhudson.managed.sources=true
@@ -317,12 +310,22 @@
<if>
<equals arg1="@{op}" arg2="up" />
<then>
- <now level="info">Update @{COMPONENT}</now>
+ <now level="info">Update '@{COMPONENT}'</now>
<if>
<istrue value="${svnant.enabled}" />
<then>
<!-- remove generated site/ folder -->
- <delete dir="${WORKINGDIR}/@{component}/site" includeemptydirs="true" quiet="true" />
+ <if>
+ <not>
+ <equals arg1="@{component}" arg2="." />
+ </not>
+ <then>
+ <delete dir="${WORKINGDIR}/@{component}/site"
+ includeemptydirs="true"
+ quiet="true"
+ />
+ </then>
+ </if>
<svn javahl="false" svnkit="true" failonerror="false">
<revert recurse="${svn.recurse}" dir="@{component}" />
</svn>
@@ -523,11 +526,16 @@
<property name="no.tests.run" value="true" />
<property name="no.overall" value="true" />
</then>
- <else>
- <echo level="warning">The following components' sources have changed and will be built:
+ <elseif>
+ <not>
+ <equals arg1="${COMPONENTS.to.build}" arg2=".," />
+ </not>
+ <then>
+ <echo level="warning">The following components' sources have changed and will be built:
COMPONENTS.to.build = ${COMPONENTS.to.build}
</echo>
- </else>
+ </then>
+ </elseif>
</if>
</then>
<else>
@@ -570,10 +578,10 @@
<now level="warning">Build overall update @{COMPONENT}</now>
</then>
<else>
- <now level="warning">Build @{COMPONENT} component</now>
+ <now level="warning">Build '@{COMPONENT}' component</now>
</else>
</if>
- <!-- optional extra instructions to do before a maven build -->
+ <!-- TODO if needed: optional extra instructions to do before a maven build -->
<loadfile property="@{COMPONENT}.pom.xml" srcfile="${WORKINGDIR}/(a){COMPONENT}/pom.xml" />
<if>
<and>
@@ -584,9 +592,12 @@
/>
</not>
<available file="${WORKINGDIR}/(a){COMPONENT}/build.xml" type="file" />
+ <not>
+ <equals arg1="@{COMPONENT}" arg2="." />
+ </not>
</and>
<then>
- <echo>Run custom @{COMPONENT}/build.xml</echo>
+ <echo>Run custom '@{COMPONENT}/build.xml'</echo>
<ant antfile="${WORKINGDIR}/(a){COMPONENT}/build.xml">
<property name="COMPONENT" value="@{COMPONENT}" />
<property name="basedir" value="${WORKINGDIR}/@{COMPONENT}" />
@@ -730,7 +741,10 @@
<for param="testresultfile" delimiter=",
">
<path>
- <fileset dir="${basedir}/surefire-reports/" includes="**/TEST-*.xml" excludes="**/*pom.xml, **/build.xml"/>
+ <fileset dir="${basedir}/surefire-reports/"
+ includes="**/TEST-*.xml"
+ excludes="**/*pom.xml, **/build.xml"
+ />
</path>
<sequential>
<var name="testsuite.name" unset="true" />
@@ -1055,15 +1069,25 @@
<!-- Used to build the update site of a component; requires a site.xml and pom.xml be generated first -->
<target name="create.update.site" depends="init">
+ <var name="site.pom.exists" unset="true" />
+ <condition property="site.pom.exists">
+ <available file="${WORKINGDIR}/${COMPONENT}/site/pom.xml" type="file" />
+ </condition>
<antcall target="genPomXml" />
+
+ <var name="site.sitexml.exists" unset="true" />
+ <condition property="site.sitexml.exists">
+ <available file="${WORKINGDIR}/${COMPONENT}/site/site.xml" type="file" />
+ </condition>
<antcall target="genSiteXml" />
+
<antcall target="build.update.site">
<param name="COMPONENTS.to.build" value="${COMPONENT}" />
<param name="update.site.path" value="${COMPONENT}/site" />
</antcall>
</target>
- <target name="genPomXml" description="Generate a pom.xml">
+ <target name="genPomXml" description="Generate a pom.xml" unless="site.pom.exists">
<property name="pomDir" value="${WORKINGDIR}/${COMPONENT}/site" />
<property name="COMPONENT" value="${COMPONENT}" />
<property name="packaging" value="eclipse-update-site" />
@@ -1085,7 +1109,10 @@
</target>
- <target name="genSiteXml" description="Generate a site.xml to contain the features in a category">
+ <target name="genSiteXml"
+ description="Generate a site.xml to contain the features in a category"
+ unless="site.sitexml.exists"
+ >
<property name="updateSiteJarDir" value="${WORKINGDIR}/${COMPONENT}/site" />
<property name="COMPONENT" value="${COMPONENT}" />
<property name="category.name" value="${product.name} ${COMPONENT} ${update.site.description} Update Site" />
15 years, 11 months