JBoss Tools SVN: r31616 - trunk/build/results.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-30 01:13:13 -0400 (Mon, 30 May 2011)
New Revision: 31616
Modified:
trunk/build/results/build.xml
Log:
check in two places for properties file to drive results page generation
Modified: trunk/build/results/build.xml
===================================================================
--- trunk/build/results/build.xml 2011-05-30 05:13:12 UTC (rev 31615)
+++ trunk/build/results/build.xml 2011-05-30 05:13:13 UTC (rev 31616)
@@ -134,18 +134,22 @@
</target>
<target name="buildResults" description="generate buildResults.html from build properties" depends="init">
- <if>
- <available file="zips/build.properties.all.xml" type="file"/>
- <then>
- <delete quiet="true" file="buildResults.out.html" />
- <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
- <classpath location="${COMMON_TOOLS}/saxon.jar" />
- </xslt>
- </then>
- <else>
- <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
- </else>
- </if>
+ <for param="propertiesFile" delimiter=", " list="zips/build.properties.all.xml, ../../logs/zips/build.properties.all.xml">
+ <sequential>
+ <if>
+ <available file="@{propertiesFile}" type="file"/>
+ <then>
+ <delete quiet="true" file="buildResults.out.html" />
+ <xslt in="@{propertiesFile}" out="buildResults.out.html" style="buildResults.xsl" force="true">
+ <classpath location="${COMMON_TOOLS}/saxon.jar" />
+ </xslt>
+ </then>
+ <else>
+ <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
+ </else>
+ </if>
+ </sequential>
+ </for>
</target>
</project>
13 years, 1 month
JBoss Tools SVN: r31615 - branches/jbosstools-3.2.x/build/results.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-30 01:13:12 -0400 (Mon, 30 May 2011)
New Revision: 31615
Modified:
branches/jbosstools-3.2.x/build/results/build.xml
Log:
check in two places for properties file to drive results page generation
Modified: branches/jbosstools-3.2.x/build/results/build.xml
===================================================================
--- branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 05:02:59 UTC (rev 31614)
+++ branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 05:13:12 UTC (rev 31615)
@@ -134,18 +134,22 @@
</target>
<target name="buildResults" description="generate buildResults.html from build properties" depends="init">
- <if>
- <available file="zips/build.properties.all.xml" type="file"/>
- <then>
- <delete quiet="true" file="buildResults.out.html" />
- <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
- <classpath location="${COMMON_TOOLS}/saxon.jar" />
- </xslt>
- </then>
- <else>
- <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
- </else>
- </if>
+ <for param="propertiesFile" delimiter=", " list="zips/build.properties.all.xml, ../../logs/zips/build.properties.all.xml">
+ <sequential>
+ <if>
+ <available file="@{propertiesFile}" type="file"/>
+ <then>
+ <delete quiet="true" file="buildResults.out.html" />
+ <xslt in="@{propertiesFile}" out="buildResults.out.html" style="buildResults.xsl" force="true">
+ <classpath location="${COMMON_TOOLS}/saxon.jar" />
+ </xslt>
+ </then>
+ <else>
+ <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
+ </else>
+ </if>
+ </sequential>
+ </for>
</target>
</project>
13 years, 1 month
JBoss Tools SVN: r31614 - trunk/build/results.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-30 01:02:59 -0400 (Mon, 30 May 2011)
New Revision: 31614
Modified:
trunk/build/results/build.xml
Log:
trap for case where zips/build.properties.all.xml does not exist
Modified: trunk/build/results/build.xml
===================================================================
--- trunk/build/results/build.xml 2011-05-30 05:01:49 UTC (rev 31613)
+++ trunk/build/results/build.xml 2011-05-30 05:02:59 UTC (rev 31614)
@@ -134,10 +134,18 @@
</target>
<target name="buildResults" description="generate buildResults.html from build properties" depends="init">
- <delete quiet="true" file="buildResults.out.html" />
- <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
- <classpath location="${COMMON_TOOLS}/saxon.jar" />
- </xslt>
+ <if>
+ <available file="zips/build.properties.all.xml" type="file"/>
+ <then>
+ <delete quiet="true" file="buildResults.out.html" />
+ <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
+ <classpath location="${COMMON_TOOLS}/saxon.jar" />
+ </xslt>
+ </then>
+ <else>
+ <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
+ </else>
+ </if>
</target>
</project>
13 years, 1 month
JBoss Tools SVN: r31613 - branches/jbosstools-3.2.x/build/results.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-30 01:01:49 -0400 (Mon, 30 May 2011)
New Revision: 31613
Modified:
branches/jbosstools-3.2.x/build/results/build.xml
Log:
remove obsolete comment
Modified: branches/jbosstools-3.2.x/build/results/build.xml
===================================================================
--- branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 05:01:30 UTC (rev 31612)
+++ branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 05:01:49 UTC (rev 31613)
@@ -6,8 +6,6 @@
<!-- should be set by Hudson -->
<!-- <property name="JOB_NAME" value="jbosstools-3.2.0.M2.continuous" /> -->
- <!-- if a different template file (eg., a partially expanded one) should be used, feed it in here -->
-
<!-- if ${WORKSPACE}/site folder exists, target that folder; else generate here. -->
<condition property="output.dir" value="${WORKSPACE}/results" else="${basedir}">
<available file="${WORKSPACE}/results" />
@@ -112,6 +110,7 @@
</ant>
<antcall target="buildResults" />
</target>
+
<target name="test.buildResults.aggregate" depends="init" description="generate buildResults.html from build properties">
<property name="isTest" value="true" />
<ant target="collect.zips" antfile="../aggregate/site/build.xml">
13 years, 1 month
JBoss Tools SVN: r31612 - branches/jbosstools-3.2.x/build/results.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-30 01:01:30 -0400 (Mon, 30 May 2011)
New Revision: 31612
Modified:
branches/jbosstools-3.2.x/build/results/build.xml
Log:
trap for case where zips/build.properties.all.xml does not exist
Modified: branches/jbosstools-3.2.x/build/results/build.xml
===================================================================
--- branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 02:42:03 UTC (rev 31611)
+++ branches/jbosstools-3.2.x/build/results/build.xml 2011-05-30 05:01:30 UTC (rev 31612)
@@ -135,10 +135,18 @@
</target>
<target name="buildResults" description="generate buildResults.html from build properties" depends="init">
- <delete quiet="true" file="buildResults.out.html" />
- <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
- <classpath location="${COMMON_TOOLS}/saxon.jar" />
- </xslt>
+ <if>
+ <available file="zips/build.properties.all.xml" type="file"/>
+ <then>
+ <delete quiet="true" file="buildResults.out.html" />
+ <xslt in="zips/build.properties.all.xml" out="buildResults.out.html" style="buildResults.xsl" force="true">
+ <classpath location="${COMMON_TOOLS}/saxon.jar" />
+ </xslt>
+ </then>
+ <else>
+ <echo>Could not generate buildResults.out.html from zips/build.properties.all.xml - file does not exist!</echo>
+ </else>
+ </if>
</target>
</project>
13 years, 1 month
JBoss Tools SVN: r31611 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2011-05-29 22:42:03 -0400 (Sun, 29 May 2011)
New Revision: 31611
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
updated with new fixed issues
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-05-29 06:10:28 UTC (rev 31610)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-05-30 02:42:03 UTC (rev 31611)
@@ -12,7 +12,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-0000">JBIDE-0000</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3126">JBIDE-3126</ulink>: Validation for the serializablity of injected beans into passive-scoped beans has been added. This ensures that if a bean belongs to <property>@SessionScoped</property>, <property>@ConversationScope</property> or any <property>@NormalScope(passivating=true)</property> and it is not stateful (<property>@Stateful</property>), the bean is checked to see if it implements <classname>java.io.Serializible</classname>. If it does implement the Serializible class, then it is marked as an error.
</para>
</listitem>
</itemizedlist>
@@ -32,7 +32,7 @@
</itemizedlist>
</para>
</formalpara> -->
- <formalpara>
+ <!-- <formalpara>
<title>Drools</title>
<para>
<itemizedlist>
@@ -43,16 +43,26 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara> -->
<formalpara>
<title>ESB</title>
<para>
<itemizedlist>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBIDE-0000">JBIDE-0000</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8569">JBIDE-8569</ulink>: Classes within the JBoss ESB Editor and ESB Message Persister are now filtered within the <guilabel>Select class</guilabel> dialog that is invoked through the <guilabel>Browse</guilabel> button. Content assist proposals are also filtered within the text field instead of a drop-down list, providing a significant performance enhancement over previously voiced solutions.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8567">JBIDE-8567</ulink>: A drop-down list has been added to the JBoss ESB Editor and Route in order to allow selection of a predefined <guilabel>Service Category</guilabel> or <guilabel>Service Name</guilabel>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8466">JBIDE-8466</ulink>: The <guilabel>Rule Agent Properties</guilabel> property has been added to the <guilabel>Content Based Router Action</guilabel> section of the JBoss ESB Editor. The following actions are now also supported through drop-down lists: <property>org.jboss.soa.esb.actions.ContentBasedWiretap</property> and <property>org.jboss.soa.esb.actions.MessageFilter</property>.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
@@ -70,7 +80,7 @@
</itemizedlist>
</para>
</formalpara> -->
- <formalpara>
+ <!--<formalpara>
<title>Hibernate</title>
<para>
<itemizedlist>
@@ -81,8 +91,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!--<formalpara>
<title>jBPM</title>
<para>
<itemizedlist>
@@ -93,8 +103,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!--<formalpara>
<title>JBoss Enterprise Portal Platform</title>
<para>
<itemizedlist>
@@ -105,8 +115,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!-- <formalpara>
<title>JavaServer Faces (JSF)</title>
<para>
<itemizedlist>
@@ -117,8 +127,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!-- <formalpara>
<title>JBoss Application Server</title>
<para>
<itemizedlist>
@@ -129,7 +139,7 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>-->
<!-- Include in JBT Release Notes only!!! -->
<!--
<formalpara>
@@ -145,7 +155,7 @@
</para>
</formalpara> -->
- <formalpara>
+ <!--<formalpara>
<title>Portlet</title>
<para>
<itemizedlist>
@@ -156,7 +166,7 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>-->
<formalpara>
<title>RichFaces</title>
<para>
@@ -169,7 +179,7 @@
</itemizedlist>
</para>
</formalpara>
- <formalpara>
+ <!--<formalpara>
<title>Seam</title>
<para>
<itemizedlist>
@@ -180,8 +190,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara> -->
+ <!--<formalpara>
<title>Smooks</title>
<para>
<itemizedlist>
@@ -192,8 +202,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!-- <formalpara>
<title>Struts</title>
<para>
<itemizedlist>
@@ -204,8 +214,40 @@
</listitem>
</itemizedlist>
</para>
+ </formalpara>-->
+ <formalpara>
+ <title>Teiid Designer</title>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8399">JBIDE-8399</ulink>: The engine behind the incorporated project examples that are distributed with the tools can now recognize a Teiid instance within a JBoss server. This has allowed for Teiid requirements to be added to Teiid Designer project examples.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-934">TEIIDDES-934</ulink>: An error was apparent in previous releases of Teiid Designer where the number of models added to a VDB could grow so large that data roles became inaccessible from the menu. This was caused because no scrollbar existed for the menu, meaning menu items would persist past the bottom of the screen without any way for the user to see them. This issue has been corrected in this latest release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-877">TEIIDDES-877</ulink>: When creating a new Teiid project, the Teiid Designer perspective would not be opened by default. In this version, a user is asked if they would like to open the corresponding Teiid Designer perspective when they have created a new Teiid project.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-869">TEIIDDES-869</ulink>: The Web Service model that was generated by the <guilabel>New Model Wizard</guilabel> was incorrect, with errors in the <methodname>invoke</methodname> and <methodname>invokeHTTP</methodname> procedures. These errors meant that the resulting parameters from the methods would be modeled as <property>IN</property>, rather than as a <property>result</property>. It also meant that the <property>contenttype</property> of the <methodname>invokeHttp</methodname> should be an <property>OUT</property> parameter. These errors have been corrected in this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-859">TEIIDDES-859</ulink>: In an example project, the ability to preview data would fail due to the preview jobs starting before the auto-build and locking model resources. Scheduling of the preview jobs are now delayed in order to ensure there is enough time for the auto-build to start.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
</formalpara>
- <formalpara>
+ <!--<formalpara>
<title>Usage</title>
<para>
<itemizedlist>
@@ -216,8 +258,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!-- <formalpara>
<title>Visual Page Editor</title>
<para>
<itemizedlist>
@@ -228,7 +270,7 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>-->
<formalpara>
<title>Web Tools Platform</title>
<para>
@@ -238,10 +280,15 @@
<ulink url="http://jira.jboss.com/jira/browse/JBDS-1602">JBDS-1602</ulink>: The Web Service Tester tool included as part of the Web Tools Platform contained an issue that would generate incorrect SOAP code, causing marshaling issues expressed as a <exceptionname>NullPointerException</exceptionname>. Multiple namespaces can now be handled without error and correct SOAP code is generated, removing marshaling issues.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8770">JBIDE-8770</ulink>: Sample input has been provided for Web Service Definition Language (WSDL) with a Simple Object Access Protocol (SOAP) header definition. This allows users a foundation to create their own WSDL applications that utilize SOAP definitions.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
- <formalpara>
+ <!--<formalpara>
<title>XHTML Editor</title>
<para>
<itemizedlist>
@@ -252,8 +299,8 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
- <formalpara>
+ </formalpara>-->
+ <!-- <formalpara>
<title>XML Structured Editor</title>
<para>
<itemizedlist>
@@ -264,7 +311,7 @@
</listitem>
</itemizedlist>
</para>
- </formalpara>
+ </formalpara>-->
<formalpara>
<title>General Issues</title>
<para>
@@ -274,6 +321,11 @@
<ulink url="http://jira.jboss.com/jira/browse/JBDS-1268">JBDS-1268</ulink>: The JBoss Developer Studio can now be installed by passing the installer a settings file named <filename>InstallConfigRecord.xml</filename>. To undertake this, setup an <filename>InstallConfigRecord.xml</filename> and run the following on a command line: <code>java -jar jbdevstudio-4.1.0.GA.jar InstallConfigRecord.xml</code>. This allows for an automated and reproducible installation. For further information consult the <emphasis>Getting Started Guide</emphasis>.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8596">JBIDE-8596</ulink>: The Properties editor for project files has been improved by allowing the <keycap>Enter</keycap> key to be pressed on a cell to begin editing its contents. Likewise, by performing a single mouse click a user can also edit the contents of a cell (previously a user had to double click to edit a cell).
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
13 years, 1 month
JBoss Tools SVN: r31609 - trunk/build/parent.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-29 02:09:34 -0400 (Sun, 29 May 2011)
New Revision: 31609
Added:
trunk/build/parent/update-site-build.xml
Log:
port update site build add-on from branch to trunk
Added: trunk/build/parent/update-site-build.xml
===================================================================
--- trunk/build/parent/update-site-build.xml (rev 0)
+++ trunk/build/parent/update-site-build.xml 2011-05-29 06:09:34 UTC (rev 31609)
@@ -0,0 +1,110 @@
+<project default="custom.build" name="site build.xml">
+
+ <!-- pass in properties to Maven/Ant via Hudson job:
+ -DJOB_NAME=${JOB_NAME}
+ -DBUILD_ID=${BUILD_ID}
+ -DBUILD_NUMBER=${BUILD_NUMBER}
+ eg.,
+ -DJOB_NAME=jbosstools-3.2_stable_branch.component-_-jmx -DBUILD_ID=2011-05-12_06-03-43 -DBUILD_NUMBER=81
+ -->
+
+ <taskdef resource="net/sf/antcontrib/antlib.xml" />
+ <dirname property="componentPath" file="${basedir}" />
+ <basename property="componentName" file="${componentPath}" />
+
+ <target name="custom.build" description="generate list of jars in the site to aid in versioning downstream">
+ <if>
+ <available file="${basedir}/target/site" type="dir" />
+ <then>
+ <var name="all.features" value="" />
+ <var name="all.plugins" value="" />
+ <var name="all.feature.jars" value="" />
+ <var name="all.plugin.jars" value="" />
+
+ <!-- defaults if not set / running outside Hudson -->
+ <if>
+ <not>
+ <isset property="JOB_NAME" />
+ </not>
+ <then>
+ <var name="JOB_NAME" value="${componentName}" />
+ </then>
+ </if>
+
+ <if>
+ <not>
+ <isset property="BUILD_NUMBER" />
+ </not>
+ <then>
+ <var name="BUILD_NUMBER" value="000" />
+ </then>
+ </if>
+
+ <if>
+ <not>
+ <isset property="BUILD_ID" />
+ </not>
+ <then>
+ <tstamp>
+ <!-- eg., 2011-05-12_06-03-43 -->
+ <format property="BUILD_ID" pattern="yyyy-MM-dd_hh-mm-ss" />
+ </tstamp>
+ </then>
+ </if>
+
+ <!-- collect jars -->
+ <for keepgoing="true" param="jarName">
+ <path>
+ <fileset dir="${basedir}/target/site" includes="*/*.jar" />
+ </path>
+ <sequential>
+ <propertyregex property="jarNameProp" defaultvalue="@{jarName}" input="@{jarName}"
+ regexp=".+/(plugins|features)/(.+)_([^_]+).jar"
+ replace="${JOB_NAME}[${BUILD_ID}][H${BUILD_NUMBER}][\1][\2]" casesensitive="true" override="true" />
+ <propertyregex property="jarNameRelPath" defaultvalue="@{jarName}" input="@{jarName}" regexp="${basedir}/target/site/(features|plugins)/" replace="" casesensitive="true" override="true" />
+ <propertyregex property="jarNameName" defaultvalue="${jarNameRelPath}" input="${jarNameRelPath}" regexp="(.+)_([0-9]+\.[0-9]+\.[0-9]+\.[^_]*).jar" replace="\1" casesensitive="true" override="true" />
+ <property value="${jarNameRelPath}" name="${jarNameProp}" />
+ <if>
+ <contains string="${jarNameProp}" substring="[features]" />
+ <then>
+ <var name="all.features" value="${all.features}, ${jarNameName}" />
+ <var name="all.feature.jars" value="${all.feature.jars}, ${jarNameRelPath}" />
+ </then>
+ <elseif>
+ <contains string="${jarNameProp}" substring="[plugins]" />
+ <then>
+ <var name="all.plugins" value="${all.plugins}, ${jarNameName}" />
+ <var name="all.plugin.jars" value="${all.plugin.jars}, ${jarNameRelPath}" />
+ </then>
+ </elseif>
+ </if>
+ <var name="jarNameProp" unset="true" />
+ </sequential>
+ </for>
+
+ <!-- rename overall feature/plugin containers + remove prefix delim -->
+ <propertyregex property="all.${componentName}.features" defaultvalue="${all.features}" input="${all.features}" regexp=", (.+)" replace="\1" casesensitive="true" override="true" />
+ <propertyregex property="all.${componentName}.plugins" defaultvalue="${all.plugins}" input="${all.plugins}" regexp=", (.+)" replace="\1" casesensitive="true" override="true" />
+ <var unset="true" name="all.features" />
+ <var unset="true" name="all.plugins" />
+ <propertyregex property="all.${componentName}.feature.jars" defaultvalue="${all.feature.jars}" input="${all.feature.jars}" regexp=", (.+)" replace="\1" casesensitive="true" override="true" />
+ <propertyregex property="all.${componentName}.plugin.jars" defaultvalue="${all.plugin.jars}" input="${all.plugin.jars}" regexp=", (.+)" replace="\1" casesensitive="true" override="true" />
+ <var unset="true" name="all.feature.jars" />
+ <var unset="true" name="all.plugin.jars" />
+ <var name="${componentName}.JOB_NAME" value="${JOB_NAME}" />
+ <var name="${componentName}.BUILD_ID" value="${BUILD_ID}" />
+ <var name="${componentName}.BUILD_NUMBER" value="${BUILD_NUMBER}" />
+
+ <!-- dump properties to an XML file, filtering for only those properties we care about -->
+ <echoproperties format="xml" destfile="${basedir}/target/site/jarlist.xml">
+ <propertyset>
+ <propertyref regex="${JOB_NAME}\[${BUILD_ID}\]\[H${BUILD_NUMBER}\]|${componentName}.JOB_NAME|${componentName}.BUILD_ID|${componentName}.BUILD_NUMBER|all.${componentName}.feature|all.${componentName}.plugin" />
+ </propertyset>
+ </echoproperties>
+
+ <!-- stick jarlist.xml into the update site zip, too -->
+ <zip destfile="${basedir}/target/site_assembly.zip" update="true" basedir="${basedir}/target/site" includes="jarlist.xml" />
+ </then>
+ </if>
+ </target>
+</project>
13 years, 1 month
JBoss Tools SVN: r31608 - trunk/build/target-platform.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-29 01:44:11 -0400 (Sun, 29 May 2011)
New Revision: 31608
Modified:
trunk/build/target-platform/build.xml
Log:
add instructions for building JBDS while JBT is running in parallel (avoid collisions)
Modified: trunk/build/target-platform/build.xml
===================================================================
--- trunk/build/target-platform/build.xml 2011-05-29 05:43:58 UTC (rev 31607)
+++ trunk/build/target-platform/build.xml 2011-05-29 05:44:11 UTC (rev 31608)
@@ -77,6 +77,10 @@
Or, simply call the jbds target, to use the defaults in the previous example:
$ ant jbds
+
+To run for JBDS target file WHILE JBT target file is being run:
+
+ $ ant jbds -DWORKINGDIR=${basedir}
</echo>
</target>
13 years, 1 month
JBoss Tools SVN: r31607 - trunk/build.
by jbosstools-commits＠lists.jboss.org
Author: nickboldt
Date: 2011-05-29 01:43:58 -0400 (Sun, 29 May 2011)
New Revision: 31607
Modified:
trunk/build/publish.sh
Log:
re-enable results builder
Modified: trunk/build/publish.sh
===================================================================
--- trunk/build/publish.sh 2011-05-29 05:43:25 UTC (rev 31606)
+++ trunk/build/publish.sh 2011-05-29 05:43:58 UTC (rev 31607)
@@ -192,24 +192,14 @@
md5sum $(find . -name "*Source*.zip" | egrep -v "aggregate-Sources|nightly-Update") >> ${md5sumsFile}
echo " " >> ${md5sumsFile}
-# TODO: JBIDE-7045 this is obsolete - replace it with xslt'd transform of build.properties.all.xml (agg site overall metadata)
-# generate HTML snippet, download-snippet.html, for inclusion on jboss.org
-# TODO: currently broken; see https://issues.jboss.org/browse/JBIDE-7444
-# [xslt] : Error! Error checking type of the expression 'funcall(replace, [funcall(substring-after, [cast(step("attribute", 17), string), literal-expr(jbosstools-)]), literal-expr(_stable_branch), literal-expr()])'.
-# [xslt] : Fatal Error! Could not compile stylesheet
-
mkdir -p ${STAGINGDIR}/logs
-#ANT_PARAMS=" -DZIPSUFFIX=${ZIPSUFFIX} -DJOB_NAME=${JOB_NAME} -Dinput.dir=${STAGINGDIR} -Doutput.dir=${STAGINGDIR}/logs -DWORKSPACE=${WORKSPACE}"
- # no longer using upstream continuous or nightly build in aggregation
- #if [[ ${JOB_NAME/.aggregate} != ${JOB_NAME} ]]; then # reuse snippet from upstream build
- # ANT_PARAMS="${ANT_PARAMS} -Dtemplate.file=http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME/.aggregate/.continuous}/logs/download-snippet.html"
- #fi
-#for buildxml in ${WORKSPACE}/build/results/build.xml ${WORKSPACE}/sources/build/results/build.xml ${WORKSPACE}/sources/results/build.xml; do
-# if [[ -f ${buildxml} ]]; then
-# ANT_SCRIPT=${buildxml}
-# fi
-#done
-#ant -f ${ANT_SCRIPT} ${ANT_PARAMS}
+ANT_PARAMS=" -DZIPSUFFIX=${ZIPSUFFIX} -DJOB_NAME=${JOB_NAME} -Dinput.dir=${STAGINGDIR} -Doutput.dir=${STAGINGDIR}/logs -DWORKSPACE=${WORKSPACE}"
+for buildxml in ${WORKSPACE}/build/results/build.xml ${WORKSPACE}/sources/build/results/build.xml ${WORKSPACE}/sources/results/build.xml; do
+ if [[ -f ${buildxml} ]]; then
+ ANT_SCRIPT=${buildxml}
+ fi
+done
+ant -f ${ANT_SCRIPT} ${ANT_PARAMS}
# ${bl} is full build log; see above
mkdir -p ${STAGINGDIR}/logs
13 years, 1 month