JBoss Tools SVN: r27308 - trunk/birt/docs/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2010-12-09 20:14:01 -0500 (Thu, 09 Dec 2010)
New Revision: 27308
Modified:
trunk/birt/docs/en-US/Book_Info.xml
Log:
Modified: trunk/birt/docs/en-US/Book_Info.xml
===================================================================
--- trunk/birt/docs/en-US/Book_Info.xml 2010-12-10 01:08:48 UTC (rev 27307)
+++ trunk/birt/docs/en-US/Book_Info.xml 2010-12-10 01:14:01 UTC (rev 27308)
@@ -7,7 +7,7 @@
<productname>JBoss Developer Studio</productname>
<productnumber>4.0</productnumber>
<edition>4.0.0</edition>
- <pubsnumber>0</pubsnumber>
+ <pubsnumber>1</pubsnumber>
<abstract>
<para>
The Beginners Guide provides a reference for use of the Business Intelligence and Reporting Tools (BIRT) plug-in with the JBoss Developer Studio. The BIRT plug-in is an open source reporting system for web applications.
14 years
JBoss Tools SVN: r27307 - trunk/as/docs/reference/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2010-12-09 20:08:48 -0500 (Thu, 09 Dec 2010)
New Revision: 27307
Modified:
trunk/as/docs/reference/en-US/Book_Info.xml
Log:
Modified: trunk/as/docs/reference/en-US/Book_Info.xml
===================================================================
--- trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 00:59:45 UTC (rev 27306)
+++ trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 01:08:48 UTC (rev 27307)
@@ -1,4 +1,4 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>2</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
+<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>4</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
14 years
JBoss Tools SVN: r27306 - trunk/as/docs/reference/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2010-12-09 19:59:45 -0500 (Thu, 09 Dec 2010)
New Revision: 27306
Modified:
trunk/as/docs/reference/en-US/Book_Info.xml
Log:
Modified: trunk/as/docs/reference/en-US/Book_Info.xml
===================================================================
--- trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 00:56:52 UTC (rev 27305)
+++ trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 00:59:45 UTC (rev 27306)
@@ -1,4 +1,4 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>1</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
+<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>2</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
14 years
JBoss Tools SVN: r27305 - trunk/as/docs/reference/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2010-12-09 19:56:52 -0500 (Thu, 09 Dec 2010)
New Revision: 27305
Modified:
trunk/as/docs/reference/en-US/Book_Info.xml
Log:
Modified: trunk/as/docs/reference/en-US/Book_Info.xml
===================================================================
--- trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 00:24:44 UTC (rev 27304)
+++ trunk/as/docs/reference/en-US/Book_Info.xml 2010-12-10 00:56:52 UTC (rev 27305)
@@ -1,4 +1,4 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>0</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
+<bookinfo><title>JBoss Server Manager Reference Guide</title><subtitle>Provides information relating to the JBoss Server Manager.</subtitle><productname>JBoss Developer Studio</productname><productnumber>4.0</productnumber><edition>4.0.0</edition><pubsnumber>1</pubsnumber><abstract><para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include><xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></bookinfo>
14 years
JBoss Tools SVN: r27304 - trunk/build.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2010-12-09 19:24:44 -0500 (Thu, 09 Dec 2010)
New Revision: 27304
Modified:
trunk/build/pom-disabled-components.xml
Log:
remove more components - should now be depending on 7 upstream builds of bpel, common, flow, jbpm, jmx, modeshape, tests
Modified: trunk/build/pom-disabled-components.xml
===================================================================
--- trunk/build/pom-disabled-components.xml 2010-12-10 00:21:52 UTC (rev 27303)
+++ trunk/build/pom-disabled-components.xml 2010-12-10 00:24:44 UTC (rev 27304)
@@ -23,37 +23,6 @@
</profile>
<profile>
- <id>tests</id>
- <activation>
- <activeByDefault>false</activeByDefault>
- <property>
- <name>as-bootstrap</name>
- </property>
- </activation>
- <modules>
- <module>../tests</module>
- </modules>
- </profile>
-
- <profile>
- <id>jmx</id>
- <activation>
- <activeByDefault>false</activeByDefault>
- </activation>
- <modules>
- <module>../jmx</module>
- </modules>
- </profile>
-
- <profile>
- <id>jmx-bootstrap</id>
- <modules>
- <module>../tests</module>
- <module>../jmx</module>
- </modules>
- </profile>
-
- <profile>
<id>archives</id>
<activation>
<activeByDefault>true</activeByDefault>
@@ -69,7 +38,6 @@
<profile>
<id>archives-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../archives</module>
</modules>
</profile>
@@ -90,9 +58,7 @@
<profile>
<id>as-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../archives</module>
- <module>../jmx</module>
<module>../as</module>
</modules>
</profile>
@@ -110,7 +76,6 @@
<profile>
<id>common-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
</modules>
</profile>
@@ -128,7 +93,6 @@
<profile>
<id>jst-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../jst</module>
</modules>
@@ -165,7 +129,6 @@
<profile>
<id>vpe-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../jst</module>
<module>../xulrunner</module>
@@ -186,7 +149,6 @@
<profile>
<id>jsf-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../jst</module>
<module>../xulrunner</module>
@@ -208,7 +170,6 @@
<profile>
<id>freemarker-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../freemarker</module>
</modules>
</profile>
@@ -226,7 +187,6 @@
<profile>
<id>hibernatetools-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../freemarker</module>
<module>../hibernatetools</module>
</modules>
@@ -245,7 +205,6 @@
<profile>
<id>portlet-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../portlet</module>
</modules>
</profile>
@@ -263,7 +222,6 @@
<profile>
<id>workingset-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../workingset</module>
</modules>
</profile>
@@ -281,7 +239,6 @@
<profile>
<id>struts-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../jst</module>
<module>../xulrunner</module>
@@ -303,7 +260,6 @@
<profile>
<id>profiler-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../profiler</module>
</modules>
</profile>
@@ -321,7 +277,6 @@
<profile>
<id>smooks-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../smooks</module>
</modules>
</profile>
@@ -339,7 +294,6 @@
<profile>
<id>cdi-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../jst</module>
<module>../cdi</module>
@@ -359,30 +313,11 @@
<profile>
<id>birt-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../birt</module>
</modules>
</profile>
<profile>
- <id>bpel</id>
- <activation>
- <activeByDefault>true</activeByDefault>
- </activation>
- <modules>
- <module>../bpel</module>
- </modules>
- </profile>
-
- <profile>
- <id>bpel-bootstrap</id>
- <modules>
- <module>../tests</module>
- <module>../bpel</module>
- </modules>
- </profile>
-
- <profile>
<id>esb</id>
<activation>
<activeByDefault>true</activeByDefault>
@@ -395,7 +330,6 @@
<profile>
<id>esb-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../esb</module>
</modules>
</profile>
@@ -413,8 +347,6 @@
<profile>
<id>seam-bootstrap</id>
<modules>
- <module>../tests</module>
- <module>../jmx</module>
<module>../archives</module>
<module>../as</module>
<module>../hibernatetools</module>
@@ -440,7 +372,6 @@
<profile>
<id>examples-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../examples</module>
</modules>
</profile>
@@ -458,7 +389,6 @@
<profile>
<id>maven-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../maven</module>
</modules>
</profile>
@@ -476,7 +406,6 @@
<profile>
<id>tptp-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../tptp</module>
</modules>
</profile>
@@ -494,67 +423,12 @@
<profile>
<id>ws-bootstrap</id>
<modules>
- <module>../tests</module>
<module>../common</module>
<module>../ws</module>
</modules>
</profile>
<profile>
- <id>modeshape</id>
- <activation>
- <activeByDefault>true</activeByDefault>
- </activation>
- <modules>
- <module>../modeshape</module>
- </modules>
- </profile>
-
- <profile>
- <id>modeshape-bootstrap</id>
- <modules>
- <module>../tests</module>
- <module>../modeshape</module>
- </modules>
- </profile>
-
- <profile>
- <id>flow</id>
- <activation>
- <activeByDefault>true</activeByDefault>
- </activation>
- <modules>
- <module>../flow</module>
- </modules>
- </profile>
-
- <profile>
- <id>flow-bootstrap</id>
- <modules>
- <module>../tests</module>
- <module>../flow</module>
- </modules>
- </profile>
-
- <profile>
- <id>jbpm</id>
- <activation>
- <activeByDefault>true</activeByDefault>
- </activation>
- <modules>
- <module>../jbpm</module>
- </modules>
- </profile>
-
- <profile>
- <id>jbpm-bootstrap</id>
- <modules>
- <module>../tests</module>
- <module>../jbpm</module>
- </modules>
- </profile>
-
- <profile>
<id>gwt</id>
<activation>
<activeByDefault>true</activeByDefault>
14 years
JBoss Tools SVN: r27303 - in trunk/documentation/jboss-tools-docs: index/en-US and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-12-09 19:21:52 -0500 (Thu, 09 Dec 2010)
New Revision: 27303
Modified:
trunk/documentation/jboss-tools-docs/all-guides.xml
trunk/documentation/jboss-tools-docs/index/en-US/master.xml
Log:
changed output directory for cloud doc from deltacloud to cloud
Modified: trunk/documentation/jboss-tools-docs/all-guides.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/all-guides.xml 2010-12-10 00:17:03 UTC (rev 27302)
+++ trunk/documentation/jboss-tools-docs/all-guides.xml 2010-12-10 00:21:52 UTC (rev 27303)
@@ -100,7 +100,7 @@
</fileSet>
<fileSet>
<directory>../../deltacloud/docs/Cloud_Tools_Reference_Guide/target/docbook/publish/en-US</directory>
- <outputDirectory>/deltacloud</outputDirectory>
+ <outputDirectory>/cloud</outputDirectory>
<filtered>false</filtered>
<lineEnding>keep</lineEnding>
<includes>
Modified: trunk/documentation/jboss-tools-docs/index/en-US/master.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/index/en-US/master.xml 2010-12-10 00:17:03 UTC (rev 27302)
+++ trunk/documentation/jboss-tools-docs/index/en-US/master.xml 2010-12-10 00:21:52 UTC (rev 27303)
@@ -31,9 +31,9 @@
</indexentry>
<indexentry>
<primaryie>Cloud Tools Reference Guide <ulink
- url="en/deltacloud/html/index.html">(html)</ulink>
- <ulink url="en/deltacloud/html_single/index.html">(html single)</ulink>
- <ulink url="en/deltacloud/pdf/Beginners_Guide.pdf"
+ url="en/cloud/html/index.html">(html)</ulink>
+ <ulink url="en/cloud/html_single/index.html">(html single)</ulink>
+ <ulink url="en/cloud/pdf/Beginners_Guide.pdf"
>(pdf)</ulink>
</primaryie>
</indexentry>
14 years
JBoss Tools SVN: r27302 - in trunk/documentation/jboss-tools-docs: index/en-US and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-12-09 19:17:03 -0500 (Thu, 09 Dec 2010)
New Revision: 27302
Modified:
trunk/documentation/jboss-tools-docs/all-guides.xml
trunk/documentation/jboss-tools-docs/index/en-US/master.xml
trunk/documentation/jboss-tools-docs/pom.xml
Log:
updated with two new books
Modified: trunk/documentation/jboss-tools-docs/all-guides.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/all-guides.xml 2010-12-09 22:16:49 UTC (rev 27301)
+++ trunk/documentation/jboss-tools-docs/all-guides.xml 2010-12-10 00:17:03 UTC (rev 27302)
@@ -99,6 +99,19 @@
<directoryMode>0755</directoryMode>
</fileSet>
<fileSet>
+ <directory>../../deltacloud/docs/Cloud_Tools_Reference_Guide/target/docbook/publish/en-US</directory>
+ <outputDirectory>/deltacloud</outputDirectory>
+ <filtered>false</filtered>
+ <lineEnding>keep</lineEnding>
+ <includes>
+ <include>**/*.*</include>
+ </includes>
+ <useStrictFiltering>false</useStrictFiltering>
+ <useDefaultExcludes>true</useDefaultExcludes>
+ <fileMode>0644</fileMode>
+ <directoryMode>0755</directoryMode>
+ </fileSet>
+ <fileSet>
<directory>../../hibernatetools/docs/reference/target/docbook/publish/en-US</directory>
<outputDirectory>/hibernatetools</outputDirectory>
<filtered>false</filtered>
@@ -344,6 +357,19 @@
<fileMode>0644</fileMode>
<directoryMode>0755</directoryMode>
</fileSet>
+ <fileSet>
+ <directory>../../modeshape/docs/ModeShape_Tools_Reference_Guide/target/docbook/publish/en-US</directory>
+ <outputDirectory>/modeshape</outputDirectory>
+ <filtered>false</filtered>
+ <lineEnding>keep</lineEnding>
+ <includes>
+ <include>**/*.*</include>
+ </includes>
+ <useStrictFiltering>false</useStrictFiltering>
+ <useDefaultExcludes>true</useDefaultExcludes>
+ <fileMode>0644</fileMode>
+ <directoryMode>0755</directoryMode>
+ </fileSet>
</fileSets>
-</assembly>
\ No newline at end of file
+</assembly>
Modified: trunk/documentation/jboss-tools-docs/index/en-US/master.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/index/en-US/master.xml 2010-12-09 22:16:49 UTC (rev 27301)
+++ trunk/documentation/jboss-tools-docs/index/en-US/master.xml 2010-12-10 00:17:03 UTC (rev 27302)
@@ -29,6 +29,14 @@
>(pdf)</ulink>
</primaryie>
</indexentry>
+ <indexentry>
+ <primaryie>Cloud Tools Reference Guide <ulink
+ url="en/deltacloud/html/index.html">(html)</ulink>
+ <ulink url="en/deltacloud/html_single/index.html">(html single)</ulink>
+ <ulink url="en/deltacloud/pdf/Beginners_Guide.pdf"
+ >(pdf)</ulink>
+ </primaryie>
+ </indexentry>
<indexentry>
<primaryie>Seam Dev Tools Reference Guide <ulink url="en/seam/html/index.html"
>(html)</ulink>
@@ -204,5 +212,15 @@
</primaryie>
</indexentry>
+ <indexentry>
+ <primaryie>ModeShape Tools Reference Guide<ulink
+ url="en/modeshape/html/index.html">(html)</ulink>
+ <ulink url="en/modeshape/html_single/index.html">(html single)</ulink>
+ <ulink url="en/modeshape/pdf/JBoss BPEL User Guide.pdf"
+
+ >(pdf)</ulink>
+ </primaryie>
+ </indexentry>
+
</index>
</book>
Modified: trunk/documentation/jboss-tools-docs/pom.xml
===================================================================
--- trunk/documentation/jboss-tools-docs/pom.xml 2010-12-09 22:16:49 UTC (rev 27301)
+++ trunk/documentation/jboss-tools-docs/pom.xml 2010-12-10 00:17:03 UTC (rev 27302)
@@ -15,6 +15,7 @@
<module>../guides/GettingStartedGuide</module>
<module>../guides/Beginners_Guide</module>
<module>../../as/docs/reference</module>
+ <module>../../deltacloud/docs/Cloud_Tools_Reference_Guide</module>
<module>../../hibernatetools/docs/reference</module>
<module>../../jbpm/docs/reference</module>
<module>../../jsf/docs/userguide</module>
@@ -33,6 +34,7 @@
<module>../../jbpm/docs/converter_ref</module>
<module>../../jmx/docs/reference</module>
<module>../../bpel/docs/reference</module>
+ <module>../../modeshape/docs/ModeShape_Tools_Reference_Guide</module>
<module>index</module>
</modules>
@@ -69,11 +71,11 @@
<fileset>
<directory>${pom.basedir}/target/docbook/publish/en-US/</directory>
<includes>
- <include>html/com/</include>
+ <!-- <include>html/com/</include> -->
<include>html/org/</include>
- <include>html_single/com/</include>
+ <!-- <include>html_single/com/</include> -->
<include>html_single/org/</include>
- <include>eclipse/com/</include>
+ <!-- <include>eclipse/com/</include> -->
<include>eclipse/org/</include>
</includes>
<followSymlinks>false</followSymlinks>
@@ -88,4 +90,4 @@
<translation>en-US</translation>
</properties>
-</project>
\ No newline at end of file
+</project>
14 years
JBoss Tools SVN: r27301 - in trunk/birt/docs: en-US and 1 other directory.
by jbosstools-commits@lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2010-12-09 17:16:49 -0500 (Thu, 09 Dec 2010)
New Revision: 27301
Added:
trunk/birt/docs/en-US/birt_integration_with_seam.xml
trunk/birt/docs/en-US/birt_reports_deployment.xml
trunk/birt/docs/en-US/framework.xml
trunk/birt/docs/en-US/hibernate_datasource.xml
trunk/birt/docs/en-US/introduction.xml
trunk/birt/docs/en-US/links.xml
trunk/birt/docs/en-US/tasks.xml
trunk/birt/docs/publican.cfg
Log:
added back files
Added: trunk/birt/docs/en-US/birt_integration_with_seam.xml
===================================================================
--- trunk/birt/docs/en-US/birt_integration_with_seam.xml (rev 0)
+++ trunk/birt/docs/en-US/birt_integration_with_seam.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,255 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<section id="birt_integration_with_seam">
+ <title>Adding BIRT Functionality to Standard Seam Web Project</title>
+
+ <para>In this section you'll know how to integrate BIRT into a Seam web project. </para>
+
+ <para>You are supposed to have Seam runtime and JBoss Application Server downloaded and
+ extracted on your hard drive.
+ You can download Seam from the
+ <ulink url="http://seamframework.org/Download">Seam Framework</ulink> web page and
+ JBoss Application Server from <ulink url="http://jboss.org/jbossas/downloads/">JBoss Application Server</ulink> official site.
+
+ </para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>We used <ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=22866&package_i..."
+ >JBoss Seam 2.0.1 GA</ulink> and <ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=22866&package_i..."
+ >JBoss Application Server 4.2.2 GA</ulink> in examples of this guide.</para>
+ </tip>
+
+ <section id="creatin_project_with_birt">
+ <title>Creating Seam Web Project with Birt Facet</title>
+
+ <para>We recommend to open <property>Seam perspective</property> by going to <emphasis>
+ <property>Window > Open Perspective > Other > Seam</property></emphasis> , this way you will have all the tools to work with Seam at hand.
+ To create a new Seam Web project navigate to <emphasis>
+ <property>File > New > Seam Web Project</property>
+ </emphasis>. Otherwise you should go to <emphasis>
+
+ <property>File > New > Other > Seam > Seam Web
+ Project</property>
+ </emphasis> if <property>Seam</property> perspective is not active.</para>
+
+ <orderedlist>
+
+ <listitem>
+ <para>On the first wizard page enter the project name, then specify the target runtime and
+ target server. We recommend to use JBoss AS server and runtime environment to ensure best performance.
+ </para>
+
+
+ <figure id="CreatingSeamWebProject">
+ <title>Creating Seam Web Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_integration_with_seam/testBirtProject.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>In the <emphasis><property>Configuration</property></emphasis> group choose the version of <emphasis>
+ <property>Seam</property>
+ </emphasis> framework you are planning to use in your application. In this guide we used Seam 2.2. </para>
+ </listitem>
+ <listitem>
+ <para>Click the <emphasis><property>Modify</property></emphasis> button
+ and enable the <emphasis>
+ <property>Birt Reporting Runtime Component</property>
+ </emphasis> facet by checking the appropriate option.</para>
+
+ <figure>
+ <title>Adding the Birt Reporting Runtime Component Facet </title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_integration_with_seam/addingBirtFacet.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Alternatively you can just choose the <emphasis>
+ <property>JBoss BIRT Integration Web Project</property>
+ </emphasis> configuration from the drop-down list in the <emphasis><property>Configuration</property></emphasis> group </para>
+
+ <figure>
+ <title>Choosing the JBoss BIRT Integration Web Project Configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/birt_integration_with_seam/projectBirtConfiguration.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </listitem>
+
+
+ <listitem>
+ <para>You may leave the next two pages with default values, just press <emphasis><property>Next</property></emphasis> to proceed.
+ </para>
+ </listitem>
+
+ <listitem>
+
+ <para>On the <emphasis><property>Birt Configuration</property></emphasis> page you can modify the BIRT deployment settings, which you can edit afterwards in the web.xml of the generated project. Let's keep the default values for now.
+ </para>
+
+ <figure>
+ <title>Configuring BIRT Deployment Settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_integration_with_seam/birtDeploymentSettings.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+
+
+ </listitem>
+
+ <listitem>
+ <para>You can also leave the <emphasis><property>JSF Capabilities</property></emphasis> page with default values. </para>
+ </listitem>
+
+ <listitem>
+ <para>On the <emphasis>
+ <property>Seam Facet</property>
+ </emphasis> page you should specify the Seam runtime and Connection profile. Please note, that the Seam runtime must be of the version you initially specified in the project settings (See the <link linkend="CreatingSeamWebProject">Creating Seam Web Project</link> figure). </para>
+ <para> When creating a Seam project with BIRT capabilities you can use the <property>BIRT Classic Models Sample Database</property> connection profile to work with the BIRT sample database.</para>
+
+ <para>For more details on how to configure database connection for a Seam project please read the
+ <ulink url="http://docs.jboss.org/tools/3.0.0.GA/en/seam/html_single/index.html#seamF...">Configure Seam Facet Settings</ulink> chapter of Seam Dev Tools Reference Guide.</para>
+ <figure>
+ <title>Configuring the Seam Facet settings</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_integration_with_seam/seamFacet.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </listitem>
+
+
+ <listitem>
+ <para>Hit <emphasis>
+ <property>Finish</property>
+ </emphasis> to create the project with BIRT functionality enabled.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+
+ <section id="integration">
+ <title>Integration with Seam</title>
+<para>
+ In the previous section you have created a Seam project with BIRT capabilities.
+ Now you can create a simple kick start project to see that everything is configured correctly.
+</para>
+
+
+ <orderedlist>
+ <listitem><para>Now create a BIRT report file and insert test data into the file.
+ Name the report file <property>helloBirt.rptdesign</property>, the report should print the data from the <code>CLASSICMODELS.CUSTOMERS</code> table of the <property>BIRT Classic Models Sample Database</property>, namely: customer number (<code>CLASSICMODELS.CUSTOMERS.CUSTOMERNAME</code>),
+ contact person first name ( <code>CLASSICMODELS.CUSTOMERS.CONTACTFIRSTNAME</code>) ,
+ contact person last name (<code>CLASSICMODELS.CUSTOMERS.CONTACTLASTNAME</code>) and
+ contact person phone number(<code>CLASSICMODELS.CUSTOMERS.PHONE</code>).
+ </para>
+ <para>The title of the report should be set via <code>reportTitle</code> parameter</para>
+ <para>
+ As this guide is primarily focused on the BIRT integration and not the BIRT technology itself we will not show the steps required to make the report. If you do not feel strong about creating a BIRT report file please read <ulink url="http://eclipse.org/birt/phoenix/tutorial/">BIRT documentation</ulink>.
+ </para>
+ <para>You can download the file <property>helloBirt.rptdesign</property> <ulink url="files/helloBirt.rptdesign">here</ulink> and copy it to the WebContent folder of your Seam project.</para>
+
+ </listitem>
+
+ <listitem>
+ <para>
+ When you are done with the <property>helloBirt.rptdesign</property> file, you should create a <property>.xhtml</property> file that will contain the BIRT report you have just created.
+ </para>
+
+
+ <para>
+ The JBoss BIRT Integration framework provides 2 components represented as <emphasis role="bold"> <property><b:birt></property></emphasis> and <emphasis role="bold"> <property><b:param></property></emphasis> tags. The jboss-seam-birt.jar library implements the functionality of the components. To find more information about the framework pleas read the <link linkend="framework">JBoss BIRT Integraion Framework API Reference</link> chapter.
+ To use that tags on the page you need to declare the tag library and define the name space like this:
+ </para>
+
+
+ <programlisting role="XML"><![CDATA[
+ xmlns:b="http://jboss.com/products/seam/birt"
+ ]]></programlisting>
+
+ <para>
+ The <emphasis role="bold"> <property><b:birt></property></emphasis> is a container for a BIRT report, that helps you integrate the report into Seam environment.
+ You can manage the properties of the report using the attributes of the <emphasis role="bold"> <property><b:birt></property></emphasis> tag.
+ </para>
+
+ <para>
+
+ The <emphasis role="bold"> <property><b:param></property></emphasis> tag describes report parameters. To set a parameter you need to specify it's name the value you want to pass.
+ You can use EL expressions to bind the representation layer with back-end logic.
+ </para>
+
+ </listitem>
+
+
+
+
+ <listitem>
+
+
+ <para>Create the <property>helloBirt.xhtml</property> file in the WebContent with the following content: </para>
+
+ <programlisting role="XML"><![CDATA[...
+<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<ui:composition xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:s="http://jboss.com/products/seam/taglib"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:rich="http://richfaces.org/rich"
+ xmlns:b="http://jboss.com/products/seam/birt"
+ template="layout/template.xhtml">
+ <ui:define name="body">
+ <rich:panel>
+ <b:birt designType="embed" designName="helloBirt.rptdesign"
+ embeddable="true">
+ <b:param name="reportTitle" value="Customers Contacts" />
+ </b:birt>
+ </rich:panel>
+ </ui:define>
+</ui:composition>
+...]]></programlisting>
+
+ <para>From this listing above you see that the title of the report is set via <emphasis role="bold"> <property><b:param></property></emphasis> by setting the parameter name and defining the <emphasis><property>"value"</property></emphasis> attribute with the "Customers Contacts" value.</para>
+
+ </listitem>
+
+
+
+
+ <listitem>
+ <para>We have created a Seam project and inserted the <property>helloBirt</property> report into the <property>helloBirt.xhtml</property> view file.</para>
+
+
+<para>To see that the application works correctly and as you expect, you need to launch it on the server.</para>
+ </listitem>
+ <listitem><para>In the <property>Servers</property> view (If it is not open navigate to <property>Windows > Show View > Other > Server > Servers</property>), select the server the application is deployed to and hit the <property>Start</property> button. </para></listitem>
+ <listitem>
+ <para>When the server is started, open your favourite browser and point it to <code>http://localhost:8080/HelloBirt/helloBirt.seam</code> .</para>
+
+
+<figure>
+ <title>Integrating BIRT into Seam Project</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_integration_with_seam/helloBirtproject.png"/>
+ </imageobject>
+ </mediaobject>
+</figure>
+ </listitem>
+ </orderedlist>
+
+ </section>
+</section>
\ No newline at end of file
Added: trunk/birt/docs/en-US/birt_reports_deployment.xml
===================================================================
--- trunk/birt/docs/en-US/birt_reports_deployment.xml (rev 0)
+++ trunk/birt/docs/en-US/birt_reports_deployment.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,220 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<section id="birt_reports_deployment">
+ <title>Creating a Dynamic BIRT Report</title>
+
+ <para>The <link linkend="birt_integration_with_seam">Adding BIRT Functionality to Standard Seam Web Project</link>
+ and <link linkend="hibernate_datasource">Using Hibernate ODA Data Sourc</link> sections tell how to integrate a BIRT report into
+ a Seam web project and how to use Hibernate data source to generate a dynamic report.
+ In this section we will create a Seam web project that can make a dynamic report using the parameters that are defined on a web page.</para>
+
+
+ <para>We will use the <property>PRODUCTS</property> table of <property>DATAMODELS</property> database for the purpose of this demo project.
+ In the first place, you need to generate Seam entities like we did in the previous chapter (<link linkend="hibernate_datasource">Hibernate ODA Data Source</link> ). The demo application will generate a report about the company's products, whereas it will allow to specify a product line. </para>
+
+<orderedlist>
+ <listitem>
+ <para>The next step is to create a Java class that will store the <code>sortOrder</code> variable and its assessors, register the class in faces.config.xml.
+ The variable will be needed to pass dynamic data to the report via report parameters, therefore it has to be of session scope.</para>
+ </listitem>
+
+ <listitem>
+ <para>
+
+
+ The report will print the data from the <code>Products</code> table, hence you need to create a report file first.
+ You can use either the <property>BIRT JDBC Data Source</property> or <property>Hibernate Data Source</property> data source to create the data set for this project. If you want to use the latter please read the previous chapter <link linkend="hibernate_datasource">Hibernate ODA Data Source</link>.
+</para>
+
+
+ <para>
+ The data set should have at least the following data set items: product vendor, product name, quantity in stock and buy price. The data is retrieved from the database with this query :
+ </para>
+
+
+ <programlisting role="XML"><![CDATA[
+SELECT productvedor,
+productname,
+quantityinstock,
+buyprice
+FROM Products as products
+
+]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>Make a table in the report and put each data set item into a column.</para>
+ </listitem>
+ <listitem>
+ <para>As it was stated in the beginning of the chapter the report will be dynamic, therefore you need to declare a report parameter first, let it be <code>sortOrder</code> and to add the parameter to the query. BIRT offers rich JavaScript API, so you can modify the query programmatically like this:</para>
+<programlisting role="XML">
+
+<xml-property name="queryText"><![CDATA[
+SELECT productvedor,
+productname,
+quantityinstock,
+buyprice
+FROM Products as products
+]]></xml-property>
+ <method name="beforeOpen"><![CDATA[
+queryString = " ORDER BY products."+reportContext.getParameterValue("sortOrder")+" "+"DESC";
+this.queryText = this.queryText+queryString;
+]]></method>
+
+</programlisting>
+ </listitem>
+ <listitem>
+<para>The report is ready. You can preview it to make sure it works properly. </para>
+ </listitem>
+ <listitem> <para>To set the report parameter you should create an <property>.xhtml</property> view page, call it <property>Products.xhtml</property>. On the page you can set the value of the <code>sortOrder</code> Java bean variable and press the <property>Generate Report</property> button to open another view page that will display the resulted report.
+ </para>
+
+
+ <para>The source code of the <property>Products.xhtml</property> should be the following:</para>
+
+ <programlisting role="XML"><![CDATA[
+<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<ui:composition xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:s="http://jboss.com/products/seam/taglib"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:rich="http://richfaces.org/rich"
+ xmlns:a4j="http://richfaces.org/a4j" template="layout/template.xhtml">
+ <ui:define name="body">
+ <rich:panel>
+ <f:facet name="header">BIRT Report Generator</f:facet>
+ <a4j:form ajaxSubmit="true" reRender="criterion">
+ <table>
+ <tr>
+ <td>Select sort order criterion:</td>
+ <td><h:selectOneMenu onchange="submit()"
+ value="#{yourJavaBean.sortOrder}"> <!-- Bind to your Java Bean -->
+ <f:selectItem itemValue="buyprice" itemLabel="buy price" />
+ <f:selectItem itemValue="quantityinstock" itemLabel="quantity in stock" />
+ </h:selectOneMenu>
+ </td>
+ </tr>
+ </table>
+ </a4j:form>
+ <s:button
+ view="/#{!empty reportParameters.order ? 'Products' : 'ProductsReport'}.xhtml" id="generate" value="Generate Report" /> <!-- If the sertOrder variable is not set the button won't work -->
+ </rich:panel>
+ </ui:define>
+</ui:composition>
+]]></programlisting>
+ <para>The logic of the file is quite simple, when the sort order criterion is select the value of <code>yourJavaBean.sortOrder</code>
+ is set automatically via Ajax and the report is ready to be generated.</para>
+ </listitem>
+ <listitem>
+ <para>Now you need to create the web page that will print the report, name the file <property>ProductsReport.xhtml</property>.
+ The file to output the report should have the following content:</para>
+
+<programlisting role="XML"><![CDATA[
+<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<ui:composition xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:s="http://jboss.com/products/seam/taglib"
+ xmlns:ui="http://java.sun.com/jsf/facelets"
+ xmlns:f="http://java.sun.com/jsf/core"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:b="http://jboss.com/products/seam/birt"
+ xmlns:rich="http://richfaces.org/rich" template="layout/template.xhtml">
+ <ui:define name="body">
+ <rich:panel>
+ <f:facet name="header">Products Report</f:facet>
+ <b:birt designType="embed" designName="products.rptdesign"
+ embeddable="true" masterpage="true">
+ <b:param name="sortOrder" value="#{yourJavaBean.sortOrder}" />
+ </b:birt>
+ </rich:panel>
+</ui:define>
+</ui:composition>
+]]></programlisting>
+ <para>
+ As you know from the <link linkend="birt_integration_with_seam">Adding BIRT Functionality to Standard Seam Web Project</link> chapter, before using the BIRT Integration framework tags on the page you need to declare the tag library and specify the name space with this line:
+ </para>
+
+ <programlisting role="XML"><![CDATA[
+ xmlns:b="http://jboss.com/products/seam/birt"
+]]></programlisting>
+ <para>
+ The dynamics to the report adds this line:
+ </para>
+ <programlisting role="XML"><![CDATA[
+<b:param name="sortOrder" value="#{yourJavaBean.sortOrder}" />
+]]></programlisting>
+
+ <para>We bound the <code>sortOrder</code> report parameter to Java Bean variable <code>value="#{yourJavaBean.sortOrder}"</code> using EL expression, and the value to the variable is assigned in the <property>Products.xhtml</property> file. </para>
+ <para>By default if you embed a report into HTML page the HTML-format report contains the <html>,
+ <head>, <body> etc., tags. However if your HTML page already has those tags, you can rid of them using the <code>embeddable="true"</code> attribute of
+
+ the <emphasis role="bold"><property><b:birt></property></emphasis> component.</para>
+ </listitem>
+ <listitem>
+ <para>Deploy the project onto the server and open your browser to see the report is successfully generated. You should navigate to
+
+ <code>http://localhost:8080/yourProjectName/Products.seam</code> to select the criterion and press the <property>Generate Report</property> button. You will be redirected to the <code>http://localhost:8080/HelloBirt/ProductsReport.seam</code>
+
+ </para>
+ <figure>
+ <title>Dynamic Report</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/birt_reports_deployment/productReport.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+</orderedlist>
+ <para>Thus, a Seam project that includes the BIRT facet can be deployed as any project. If you
+ define the Hibernate ODA driver, the JBoss BIRT engine will use JNDI URL that has to be bound
+ to either Hibernate Session Factory or Hibernate Entity Manager Factory. If you
+ don't specify the JNDI URL property, our engine will try the following JNDI
+ URLs:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>java:/<project_name></emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>java:/<project_name>EntityManagerFactory</emphasis>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>When creating a Seam EAR project, Hibernate Entity Manager Factory is bound to
+ <emphasis>java:/{projectName}EntityManagerFactory</emphasis>. All you need to do is
+ to use the Hibernate Configuration created automatically. You can use default values for the
+ Hibernate Configuration and JNDI URL within the BIRT Hibernate Data Source.</para>
+
+ <para>When using a Seam WAR project, neither HSF nor HEMF aren't bound to JNDI by
+ default. You have to do this manually. For instance, HSF can be bound to JNDI by adding the
+ following property to the <emphasis>
+ <property>persistence.xml</property></emphasis> file:</para>
+
+ <programlisting role="XHTML"><![CDATA[<property name="hibernate.session_factory_name" value="java:/projectname"/>
+ ]]></programlisting>
+
+ <para>And you can use <emphasis>java:/projectname</emphasis> as the JNDI URL property when creating a BIRT
+ Hibernate Data Source.</para>
+
+ <note>
+ <title>Note:</title>
+ <para>If you want to test this feature using PDE Runtime, you need to add <emphasis>
+ <property>osgi.dev=bin</property>
+ </emphasis> to the <emphasis>
+ <property>WebContent/WEB-INF/platform/configuration/config.ini</property>
+ </emphasis> file.</para>
+ </note>
+
+ <para>In conclusion, the main goal of this document is to get you to know with a full feature set
+ that <property>JBoss BIRT Tools</property> provide. Thus if you have some questions,
+ comments or suggestions on the topic, please feel free to ask in the <ulink
+ url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=201">JBoss
+ Tools Forum</ulink>. You can also influence on how you want to see JBoss Tools docs in
+ future leaving your vote on the article <ulink
+ url="http://www.jboss.org/community/docs/DOC-10795">Overview of the improvements required by JBossTools/JBDS Docs users</ulink>.</para>
+
+</section>
Added: trunk/birt/docs/en-US/framework.xml
===================================================================
--- trunk/birt/docs/en-US/framework.xml (rev 0)
+++ trunk/birt/docs/en-US/framework.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,260 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="framework">
+ <?dbhtml filename="framework.html"?>
+
+ <chapterinfo>
+ <keywordset>
+
+ <keyword>Eclipse</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>JBoss Tools</keyword>
+ <keyword>BIRT Integration</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>JBoss BIRT Integraion Framework API Reference</title>
+
+
+<section>
+
+ <title>
+ <emphasis role="bold"> <property><b:birt></property></emphasis> Component
+ </title>
+
+
+
+<para>
+ The <emphasis role="bold"> <property><b:birt></property></emphasis> component servers to integrate a BIRT report into Seam/JSF container.
+ The <emphasis role="bold"> <property><b:birt></property></emphasis> tag recognizes most of the parameters described on the BIRT
+ <ulink url="http://www.eclipse.org/birt/phoenix/deploy/viewerUsage2.2.php#parameters">Report Viewer Parameters</ulink> page, though it has attributes of its own.
+
+</para>
+
+
+ <table>
+ <title><emphasis role="bold"> <property><b:birt></property></emphasis> Component Reference</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Correspondance to BIRT Report Viewer parameters</entry>
+ <entry>Description/</entry>
+
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>designType</entry>
+ <entry> - </entry>
+ <entry>Corresponds to the BIRT servlet mappings. Possible values are run, frameset, preview and embed.
+ If the attribute is set to embed the component is used for
+ embeddable html. This type ignores all the attributes except designName
+ and masterpage.
+ </entry>
+ </row>
+ <row>
+ <entry>embeddable</entry>
+ <entry> - </entry>
+ <entry>A BIRT report occupies the whole page by default. It contains the <html>,
+ <head>, <body> etc., tags. Embedded report can be a part of another page.
+ It doesn't contain the above mentioned tags. Only HTML report can be embedded.</entry>
+ </row>
+ <row>
+ <entry>designName</entry>
+ <entry>__report</entry>
+ <entry>Sets the name of the report design to process. This can be an absolute path or relative to the working folder. Valid values are run, frameset and preview</entry>
+ </row>
+
+ <row>
+ <entry>format</entry>
+ <entry>__format</entry>
+ <entry>Specifies the desired output format, such as pdf, html, doc, ppt, or xls.</entry>
+ </row>
+
+ <row>
+ <entry>title</entry>
+ <entry>__title</entry>
+ <entry>Sets the report title.</entry>
+ </row>
+
+ <row>
+ <entry>showtitle</entry>
+ <entry>__showtitle</entry>
+ <entry>Determines if the report title is shown in the frameset viewer. Defaults to true.</entry>
+ </row>
+
+ <row>
+ <entry>toolbar</entry>
+ <entry>__toolbar</entry>
+ <entry>
+
+ Determines if the report toolbar is shown in the frameset viewer.Defaults to true. Valid values are true and false.</entry>
+ </row>
+
+
+
+ <row>
+ <entry>navigationbar</entry>
+ <entry>__navigationbar</entry>
+ <entry>
+
+ Determines if the navigation bar is shown in the frameset viewer. Defaults to true. Valid values are true and false.</entry>
+ </row>
+
+
+ <row>
+ <entry>document</entry>
+ <entry>__document</entry>
+ <entry>
+ Sets the name for the rptdocument. The document is created when the report engine separates run and render tasks, and
+ is used to support features like table of contents and pagination.
+ This setting can be an absolute path or relative to the working folder. If no document parameter is used, a unique document is created in the document folder.
+ </entry>
+ </row>
+
+ <row>
+ <entry>locale</entry>
+ <entry>__locale</entry>
+ <entry>
+ Specifies the locale for the specific operation. Note that this will override the default locale.
+ </entry>
+ </row>
+ <row>
+ <entry>svg</entry>
+ <entry>__svg</entry>
+ <entry>
+ Specifies whether SVG is supported.
+ </entry>
+ </row>
+
+
+
+ <row>
+ <entry>page</entry>
+ <entry>__page</entry>
+ <entry>
+ Specifies specific page to render.
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>pagerange</entry>
+ <entry>__pagerange</entry>
+ <entry>
+ Specifies page range to render. Eg 1-4,7.
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>masterpage</entry>
+ <entry>__masterpage</entry>
+ <entry>
+
+ Indicates that the report master page should be used or not. Validvalues are true and false.
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>overwrite</entry>
+ <entry>__overwrite</entry>
+ <entry>
+
+ This setting if set to true will force an overwrite of the existing report document.
+ </entry>
+ </row>
+
+ <row>
+ <entry>bookmark</entry>
+ <entry>__bookmark</entry>
+ <entry>
+
+ Specifies a specific bookmark within the report to load. The viewer will automatically load the appropriate page.
+ </entry>
+ </row>
+
+
+
+ <row>
+ <entry>rtl</entry>
+ <entry>__rtl</entry>
+ <entry>
+ Specifies whether to display the report in right to left format. This setting defaults to false.
+ </entry>
+ </row>
+
+
+
+ <row>
+ <entry>fittopage</entry>
+ <entry>__fittopage</entry>
+ <entry>
+ Specifies whether PDF generation should fit content to a page. Valid values are true and false.
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>resourceFolder</entry>
+ <entry>__resourceFolder</entry>
+ <entry>
+ Specifies the resource folder to use. This setting will override the default setting in the web.xml. The resource folder is used to locate libraries, images, and resource files.
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+</section>
+
+ <section>
+ <title><emphasis role="bold"> <property><b:param></property></emphasis> Component</title>
+ <para>
+ The <emphasis role="bold"> <property><b:param></property></emphasis> tag describes report parameter.
+ </para>
+
+ <table>
+ <title><emphasis role="bold"> <property><b:param></property></emphasis> Component</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>name</entry>
+ <entry>The parameter name. Required.</entry>
+ </row>
+ <row>
+ <entry>value</entry>
+ <entry>The parameter value. Required.</entry>
+ </row>
+
+ <row>
+ <entry>isnull</entry>
+ <entry>Specifies that a report parameter has a null value</entry>
+ </row>
+ <row>
+ <entry>islocale</entry>
+ <entry>Specifies whether the parameter is localized</entry>
+ </row>
+
+ </tbody>
+
+ </tgroup>
+ </table>
+ </section>
+
+
+
+
+
+
+
+</chapter>
Added: trunk/birt/docs/en-US/hibernate_datasource.xml
===================================================================
--- trunk/birt/docs/en-US/hibernate_datasource.xml (rev 0)
+++ trunk/birt/docs/en-US/hibernate_datasource.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,213 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<section id="hibernate_datasource">
+
+
+ <title>Using Hibernate ODA Data Source</title>
+
+ <para>The JBoss BIRT Integration feature includes the Hibernate ODA Data Source which is completely
+ integrated with Hibernate Tools. You can use it the way as you would use any of BIRT ODA drivers.
+
+ </para>
+
+<orderedlist>
+ <listitem>
+ <para>First, you need to reverse engineer from the database to generate Seam entities. You can perform this operation going to <emphasis>
+ <property>File > New > Seam Generate Entities</property>
+ </emphasis> in the <property>Seam perspective</property>. More details on the Seam Generate
+ Entities please read <ulink
+ url="http://download.jboss.org/jbosstools/nightly-docs/en/seam/html_single/ind..."
+ >Seam Dev Tools Reference guide</ulink>).
+ In this guide we will use the <property>Employees</property> table of the <property>DATAMODELS</property> database.
+</para>
+
+ <tip>
+ <title>Tip:</title>
+ <para>Before performing Seam Generate Entities, you should have a connection profile
+ adjusted and connected to a database. How to do this see in the <ulink
+ url="http://download.jboss.org/jbosstools/nightly-docs/en/seam/html_single/ind..."
+ >CRUD Database Application</ulink> chapter of the Seam Dev Tools Reference
+ guide.</para>
+ <para>
+ If you followed the steps described in the
+ <link linkend="birt_integration_with_seam">Adding BIRT Functionality to Standard Seam Web Project</link> chapter,
+ you would have a connection profile already configured.
+ </para>
+ </tip>
+ </listitem>
+ <listitem>
+<para>
+ Next you should create a new BIRT report file ( <emphasis>><property>File > New > Other > Business Intelligence and Reporting
+ Tools > Report</property></emphasis>) to represent the data from the <property>Employees</property> table. Call the file <property>employees.rptdesign</property>.
+</para>
+ </listitem>
+
+<listitem>
+
+
+ <para>Now switch to the <property>BIRT Report Design</property> perspective.</para>
+</listitem>
+ <listitem>
+ <para>In the <property>Data Explorer</property> view right-click the <emphasis>
+ <property>Data Source</property>
+ </emphasis> node and choose <emphasis>
+ <property>New Data Source</property>.</emphasis></para>
+
+ <figure>
+ <title>Creating a New Data Source</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/creatingDataSource.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+</listitem>
+ <listitem>
+ <para>The wizard will prompt you to select data source type. Choose <emphasis>
+ <property>Hibernate Data Source</property>
+ </emphasis> and give it a meaningful name, for instance <emphasis>
+ <property>HibernateDataSource</property>
+ </emphasis>. Hit <emphasis>
+ <property>Next</property> to proceed.</emphasis></para>
+
+ <figure>
+ <title>Creating Hibernate Data Source</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/hibernateDataSource.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>On the next wizard's dialog you can leave the everything with default values, press the <emphasis>
+ <property>Test Connection</property>
+ </emphasis> button to verify that the connection is established successfully.</para>
+
+ <para>
+ The <property>Hibernate Data Source</property> enables you to specify a Hibernate Configuration or JNDI URL.
+
+ </para>
+
+ <figure>
+ <title>Hibernate Data Source Profile</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/connectionSuccessful.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>Press <emphasis>
+ <property>Finish</property>
+ </emphasis> to complete <property>New Data Source</property> wizard.</para>
+ </listitem>
+
+ <listitem>
+ <para>Now you need to configure a new Hibernate ODA data set. Launch the
+ <property>New Data Set</property> wizard. In the <property>Data Explorer View</property>
+ right-click the <emphasis>
+ <property>Data Set</property>
+ </emphasis> node and select <emphasis>
+ <property>New Data Set</property>.</emphasis></para>
+
+ </listitem>
+ <listitem>
+ <para>Select <property>HibernateDataSource</property> as target data source and type in the new data set name.
+ Call it <property>HibernateDataSet</property>.</para>
+
+
+
+
+ <figure>
+ <title>Creating a Hibernate ODA Data Set</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/addingHibernateODADataset.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+
+ <para>The next dialog of the wizard will help you compose a query for the new data set.</para>
+ <para>We will make a report that will print all employees in the database who has Sales Rep job title.</para>
+
+ <programlisting role="SQL"><![CDATA[...
+select jobtitle, firstname, lastname, email
+from Employees as employees where employees.jobtitle = 'Sales Rep'
+...]]></programlisting>
+
+
+
+ <para>
+
+ To validate the
+ entered query you can press the <emphasis>
+ <property>Test query</property>
+ </emphasis> button. All the HQL features like syntax highlighting, content assist,
+ formatting, drag-and-drop, etc., are available to facilitate query composing.</para>
+
+ <figure>
+ <title>Composing query for Data Set</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/testingQuery.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+
+ <para>Pressing <property>Finish</property> will call the <property>Edit Data Set</property> dialog where you can adjust the parameters of the data set and preview the resulted set.
+ If everything looks good, hit <property>Ok</property> to generate a new data set.
+ </para>
+ </listitem>
+ <listitem>
+
+ <para>Now you can insert the data set items of <property>HibernateDataSet</property> into the <property>employees.rptdesign</property>.</para>
+
+
+ <tip>
+ <title>Tip:</title>
+ <para>If you don't know how to do this we suggest that you refer to the <ulink
+ url="http://www.eclipse.org/birt/phoenix/tutorial/">Eclipse BIRT Tutorial</ulink>.</para>
+ </tip>
+
+
+<para>You can also use parameters in the query to add dynamics to your report. In the previous example we hardcoded the selection criterion in the <code>where</code> clause. </para>
+ <para>To specify the job title on-the-fly your query should look like this:</para>
+ <programlisting role="XML"><![CDATA[
+select jobtitle,firstname, lastname,email
+from Employees as employees where employees.jobtitle = ?
+]]></programlisting>
+
+ <para>The question mark represents a data set input parameter, which is not the same as a report parameter.
+ Now you need to define an new report parameter to pass the data to the report, call it <code>JobTitle</code>.
+
+
+
+ The dataset parameter can be linked to a report parameter.
+ In the <property>Data Explorer</property> view click the Data Set node to open it and right-click
+ on the data set you created previously( in our case it is <property>HibernateDataSet</property>),
+ choose <property>Edit</property> and navigate to the <property>Parameters</property> section.
+ Declare a new data set parameter, name it <code>jobtitle</code> and map it to the already existing <code>JobTitle</code> report parameter.
+ </para>
+ </listitem>
+ <listitem>
+ <para>You report is ready, you can view it by clicking on the <property>Preview</property> tab of the <property>BIRT Report Designer</property> editor. </para>
+
+
+ <para>You will be prompted to assign a value to the report parameter. For instance you can enter "Sales Rep". </para>
+
+ <figure>
+ <title>Resulted Dynamic Report</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hibernate_datasource/finalReport.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+</orderedlist>
+</section>
Added: trunk/birt/docs/en-US/introduction.xml
===================================================================
--- trunk/birt/docs/en-US/introduction.xml (rev 0)
+++ trunk/birt/docs/en-US/introduction.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction">
+ <?dbhtml filename="introduction.html"?>
+
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>JBoss Tools</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>BIRT Plugin</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Introduction</title>
+
+
+
+
+ <section>
+
+ <title>What is BIRT?</title>
+ <para>BIRT plugin is an Eclipse-based open source reporting system for web applications
+ based on Java and J2EE. BIRT consists of two main components: a report designer based on
+ Eclipse, and a runtime component that can be added to your app server. BIRT also offers
+ a charting engine that lets you add charts to your own Web application.</para>
+ <para>With the help of BIRT you can generate a great number of reports to be used in your
+ application:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Lists</para>
+ </listitem>
+ <listitem>
+ <para>Charts</para>
+ </listitem>
+ <listitem>
+ <para>Crosstabs, or cross-tabulation, or matrix</para>
+ </listitem>
+ <listitem>
+ <para>Letters and Documents</para>
+ </listitem>
+ <listitem>
+ <para>Compound Reports</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>You can find more detailed information on the BIRT plugin, its report types and
+ anatomy on the <ulink url="http://www.eclipse.org/birt/phoenix/intro/">BIRT Homepage</ulink>.</para>
+
+ <para>To understand the basic BIRT concepts and to know how to create a basic BIRT report,
+ refer to the <ulink url="http://www.eclipse.org/birt/phoenix/tutorial/">Eclipse BIRT
+ Tutorials</ulink>. What extensions <property>JBoss Tools</property> provides for
+ Eclipse BIRT you'll find out in the next sections.</para>
+ </section>
+
+
+
+ <section>
+ <title>JBoss BIRT Integration Functionality Overview</title>
+
+ <para>
+ The key feature of JBoss BIRT Integration is the JBoss BIRT Integration Framework, which allows to integrate a BIRT report into Seam/JSF container.
+ The framework API reference is in the
+ <link linkend="framework">JBoss BIRT Integraion Framework API Reference</link> chapter of the guide.
+ </para>
+ <para>
+
+ This guide also covers functionality of <property>JBoss Tools</property> module which assists in
+ integration with BIRT.
+ The integration plug-in allows you to visually configure <property>Hibernate Data Source</property> (specify a Hibernate configuration or JNDI URL),
+ compose HQL queries with syntax-highlighting, content-assist, formatting as well as other functionalities available in the HQL editor.
+
+
+ </para>
+
+ <para>
+ To enable <property>JBoss Tools</property> integration with BIRT you are intended to
+ have the next:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Eclipse with <property>JBoss Tools</property>
+ installed (how to install <property>JBoss Tools</property> on Eclipse, what
+ dependences and versions requirements are needed reed in the <!--<ulink
+ url="&gsglink;#JBossToolsInstall"
+ >-->JBoss Tools Installation<!--</ulink>--> section)</para>
+ </listitem>
+ <listitem>
+ <para>BIRT Report Designer (BIRT Report Designer 2.3.2
+ you can download from <ulink
+ url="http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/..."
+ >Eclipse downloads site</ulink>)</para>
+ </listitem>
+ <listitem>
+ <para>BIRT Web Tools Integration ( BIRT WTP Integration 2.3.2 you can download from
+ <ulink
+ url="http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/..."
+ >Eclipse downloads site</ulink>)</para>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Note:</title>
+ <para>Versions of BIRT framework and BIRT WTP integration should be no less than RC4 in
+ order to the BIRT facet works correctly.</para>
+ </note>
+ </section>
+
+
+
+</chapter>
Added: trunk/birt/docs/en-US/links.xml
===================================================================
--- trunk/birt/docs/en-US/links.xml (rev 0)
+++ trunk/birt/docs/en-US/links.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,23 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<chapter id="birt_plugin_rel_resources" xreflabel="birt_plugin_rel_resources">
+ <?dbhtml filename="links.html"?>
+ <chapterinfo>
+ <keywordset>
+
+ <keyword>Eclipse</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>JBoss Tools</keyword>
+ <keyword>BIRT Integration</keyword>
+ </keywordset>
+ </chapterinfo>
+
+
+ <title>Other Relevant Resources on the Topic</title>
+
+ <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at <ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/tools</ulink> in the corresponding release directory.</para>
+ <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.
+
+</para>
+
+</chapter>
Added: trunk/birt/docs/en-US/tasks.xml
===================================================================
--- trunk/birt/docs/en-US/tasks.xml (rev 0)
+++ trunk/birt/docs/en-US/tasks.xml 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,29 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<chapter id="tasks" xreflabel="tasks">
+ <?dbhtml filename="tasks.html"?>
+ <chapterinfo>
+ <keywordset>
+
+ <keyword>Eclipse</keyword>
+ <keyword>JBoss</keyword>
+ <keyword>JBoss Tools</keyword>
+ <keyword>BIRT Integration</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Tasks</title>
+ <para> In this chapter of the guide you will find information on the tasks that you can perform integrating BIRT. The required version of BIRT is 2.3.2 or greater.</para>
+
+
+
+
+ <!-- &birt_integration_with_seam;
+ &hibernate_datasource;
+ &birt_reports_deployment; -->
+ <xi:include href="birt_integration_with_seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="hibernate_datasource.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="birt_reports_deployment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+
+</chapter>
Added: trunk/birt/docs/publican.cfg
===================================================================
--- trunk/birt/docs/publican.cfg (rev 0)
+++ trunk/birt/docs/publican.cfg 2010-12-09 22:16:49 UTC (rev 27301)
@@ -0,0 +1,8 @@
+# Config::Simple 4.59
+# Fri Nov 27 08:57:18 2009
+
+xml_lang: en-US
+type: Book
+brand: JBoss
+debug: 1
+
14 years
JBoss Tools SVN: r27300 - trunk/build/aggregate/site.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2010-12-09 15:42:44 -0500 (Thu, 09 Dec 2010)
New Revision: 27300
Modified:
trunk/build/aggregate/site/build.xml
trunk/build/aggregate/site/pom.xml
Log:
remove comments and use only a single composite repo; support reading metadata from composite repos to get list of child sites; from those get zips to download
Modified: trunk/build/aggregate/site/build.xml
===================================================================
--- trunk/build/aggregate/site/build.xml 2010-12-09 20:42:34 UTC (rev 27299)
+++ trunk/build/aggregate/site/build.xml 2010-12-09 20:42:44 UTC (rev 27300)
@@ -42,6 +42,124 @@
</taskdef>
</target>
+ <!-- = = = = = = = = = = = = = = = = =
+ macrodef: fetchZipsFromList - given a list of zips in zip.list.txt, fetch those zips
+ = = = = = = = = = = = = = = = = = -->
+ <macrodef name="fetchZipsFromList">
+ <attribute name="repo" default="" />
+ <sequential>
+
+ <var name="location.cleaned" value="@{repo}" />
+ <propertyregex defaultvalue="${location.cleaned}" input="${location.cleaned}" regexp="/all/repo/*$" replace="" casesensitive="true" override="true" property="location.cleaned" />
+ <propertyregex defaultvalue="${location.cleaned}" input="${location.cleaned}" regexp="/tools/*$" replace="" casesensitive="true" override="true" property="location.cleaned" />
+
+ <echo level="verbose">repo = ${location.cleaned}</echo>
+ <!-- fetch zip.list.txt file, if available -->
+ <var unset="true" name="ALL_ZIPS" />
+ <var unset="true" name="wget.return" />
+ <!-- quieter output and return code check w/ wget instead of <get> -->
+ <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null">
+ <arg line="${location.cleaned}/logs/zip.list.txt -q --no-clobber" />
+ </exec>
+ <!--get src="${location.cleaned}/logs/zip.list.txt" dest="${aggegate.zips.dir}/zip.list.txt" ignoreerrors="true" /-->
+ <if>
+ <and>
+ <equals arg1="${wget.return}" arg2="0" />
+ <available file="${aggegate.zips.dir}/zip.list.txt" type="file" />
+ </and>
+ <then>
+ <!-- load zip.list.txt file, get ALL_ZIPS list -->
+ <var unset="true" name="ALL_ZIPS" />
+ <property file="${aggegate.zips.dir}/zip.list.txt" />
+ <if>
+ <isset property="ALL_ZIPS" />
+ <then>
+ <var name="relativePath" unset="true" />
+ <for list="${ALL_ZIPS}" delimiter=", " keepgoing="true" param="zipPath">
+ <sequential>
+ <propertyregex override="true" property="relativePath" defaultvalue="" input="@{zipPath}" regexp="(.+)/([^/]+.zip)" replace="\1" />
+ <mkdir dir="${aggegate.zips.dir}/${relativePath}" />
+ <!-- fetch zips to local dir -->
+ <echo level="verbose">repoNum = @{repoNum}
+relativePath = ${relativePath}
+zipPath = @{zipPath}
+DEST = ${aggegate.zips.dir}/@{zipPath}
+</echo>
+ <echo> Zip URL = ${location.cleaned}/@{zipPath}</echo>
+ <if>
+ <isset property="isTest" />
+ <then>
+ <touch file="${aggegate.zips.dir}/@{zipPath}" />
+ </then>
+ <else>
+ <var name="wget.return" unset="true" />
+ <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null">
+ <arg line="${location.cleaned}/@{zipPath} -q --no-clobber" />
+ </exec>
+ <!--get src="${location.cleaned}/@{zipPath}" dest="${aggegate.zips.dir}/@{zipPath}" /-->
+ <if>
+ <not>
+ <equals arg1="${wget.return}" arg2="0" />
+ </not>
+ <then>
+ <echo> ** Error [${wget.return}] ** Could not wget ${location.cleaned}/@{zipPath}</echo>
+ </then>
+ </if>
+ </else>
+ </if>
+ </sequential>
+ </for>
+ <var name="relativePath" unset="true" />
+ </then>
+ </if>
+ <var unset="true" name="ALL_ZIPS" />
+ <delete file="${aggegate.zips.dir}/zip.list.txt" quiet="true" />
+ </then>
+ <else>
+ <echo> ** Error [${wget.return}] ** Could not wget ${location.cleaned}/logs/zip.list.txt</echo>
+ </else>
+ </if>
+ <var name="location.cleaned" unset="true" />
+ </sequential>
+ </macrodef>
+
+ <!-- = = = = = = = = = = = = = = = = =
+ macrodef: fetchZipsFromMetadata - look for compositeArtifacts.xml and parse results
+ = = = = = = = = = = = = = = = = = -->
+ <macrodef name="fetchZipsFromMetadata">
+ <attribute name="repo" default="" />
+ <sequential>
+ <echo level="verbose">repo = @{repo}</echo>
+ <!-- if no zip.list.txt from the inputRepo, then fetch from @{repo}/compositeArtifacts.xml instead -->
+ <var name="wget.return" unset="true" />
+ <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null">
+ <arg line="@{repo}/compositeArtifacts.xml -q --no-clobber" />
+ </exec>
+ <if>
+ <and>
+ <equals arg1="${wget.return}" arg2="0" />
+ <available file="${aggegate.zips.dir}/compositeArtifacts.xml" type="file" />
+ </and>
+ <then>
+ <echo level="verbose">Got ${aggegate.zips.dir}/compositeArtifacts.xml</echo>
+ <xmlproperty file="${aggegate.zips.dir}/compositeArtifacts.xml" validate="false" collapseAttributes="true" />
+ <echo level="verbose">Found ${repository.children.size} contained repos to search</echo>
+ <!-- foreach entry repository.children.child.location -->
+ <for param="location" list="${repository.children.child.location}">
+ <sequential>
+ <echo level="error">Site URL = @{location}</echo>
+ <fetchZipsFromList repo="@{location}" />
+ </sequential>
+ </for>
+ <delete file="${aggegate.zips.dir}/compositeArtifacts.xml" quiet="true" />
+ </then>
+ <else>
+ <echo> ** Error [${wget.return}] ** Could not wget @{repo}/compositeArtifacts.xml</echo>
+ </else>
+ </if>
+ </sequential>
+ </macrodef>
+
<target name="add.associate.sites" if="associate.sites">
<if>
<and>
@@ -148,12 +266,7 @@
<isset property="BUILD_NUMBER" />
</and>
<then>
- <propertyregex override="true"
- property="update.site.version"
- defaultvalue="${JOB_NAME}"
- input="${JOB_NAME}"
- regexp="jbosstools-([0-9.]+.*).aggregate"
- replace=": \1.${BUILD_ID}-H${BUILD_NUMBER}" />
+ <propertyregex override="true" property="update.site.version" defaultvalue="${JOB_NAME}" input="${JOB_NAME}" regexp="jbosstools-([0-9.]+.*).aggregate" replace=": \1.${BUILD_ID}-H${BUILD_NUMBER}" />
</then>
<else>
<property name="update.site.version" value="" />
@@ -181,63 +294,64 @@
<mkdir dir="${aggegate.zips.dir}" />
<for list="${inputRepos}" delimiter=", " keepgoing="true" param="repoNum">
<sequential>
- <!-- fetch zip.list.txt file, if available -->
- <var unset="true" name="ALL_ZIPS" />
- <var unset="true" name="wget.return" />
- <!-- quieter output and return code check w/ wget instead of <get> -->
- <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return">
- <arg line="${inputRepo(a){repoNum}}/logs/zip.list.txt -q --no-clobber" />
- </exec>
- <!--get src="${inputRepo(a){repoNum}}/logs/zip.list.txt" dest="${aggegate.zips.dir}/zip.list.txt" ignoreerrors="true" /-->
+ <var name="repo" value="${inputRepo@{repoNum}}" />
<if>
- <and>
- <equals arg1="${wget.return}" arg2="0" />
- <available file="${aggegate.zips.dir}/zip.list.txt" type="file" />
- </and>
+ <contains string="${repo}" substring="composite" />
<then>
- <!-- load zip.list.txt file, get ALL_ZIPS list -->
- <var unset="true" name="ALL_ZIPS" />
- <property file="${aggegate.zips.dir}/zip.list.txt" />
- <if>
- <isset property="ALL_ZIPS" />
- <then>
- <var name="relativePath" unset="true" />
- <for list="${ALL_ZIPS}" delimiter=", " keepgoing="true" param="zipPath">
- <sequential>
- <propertyregex override="true"
- property="relativePath"
- defaultvalue=""
- input="@{zipPath}"
- regexp="(.+)/([^/]+.zip)"
- replace="\1" />
- <mkdir dir="${aggegate.zips.dir}/${relativePath}" />
- <!-- fetch zips to local dir -->
- <echo level="verbose">repoNum = @{repoNum}
-relativePath = ${relativePath}
-zipPath = @{zipPath}
-DEST = ${aggegate.zips.dir}/@{zipPath}
-</echo>
- <echo>URL = ${inputRepo@{repoNum}}/@{zipPath}
-</echo>
- <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="false">
- <arg line="${inputRepo@{repoNum}}/@{zipPath} -q --no-clobber" />
- </exec>
- <!--get src="${inputRepo@{repoNum}}/@{zipPath}" dest="${aggegate.zips.dir}/@{zipPath}" /-->
- </sequential>
- </for>
- <var name="relativePath" unset="true" />
- </then>
- </if>
- <var unset="true" name="ALL_ZIPS" />
- <delete file="${aggegate.zips.dir}/zip.list.txt" quiet="true" />
+ <fetchZipsFromMetadata repo="${repo}" />
</then>
+ <else>
+ <fetchZipsFromList repo="${repo}" />
+ </else>
</if>
</sequential>
</for>
</target>
- <target name="custom.build"
- description="aggregate update site extras"
- depends="init,check.target,add.associate.sites,add.web.content,pack.zip,collect.zips" />
+ <target name="custom.build" description="aggregate update site extras" depends="init,check.target,add.associate.sites,add.web.content,pack.zip,collect.zips" />
+ <target name="test.collect.zips.from.metadata" depends="init">
+ <property name="isTest" value="true" />
+ <antcall target="collect.zips">
+ <param name="inputRepos" value="1" />
+ <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk" />
+ </antcall>
+ </target>
+
+ <target name="test.collect.zips.from.metadata.with.errors" depends="init">
+ <property name="isTest" value="true" />
+ <antcall target="collect.zips">
+ <param name="inputRepos" value="1,2" />
+ <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/_composite_/NO_SUCH_B..." />
+ </antcall>
+ </target>
+
+ <target name="test.collect.zips.from.list" depends="init">
+ <property name="isTest" value="true" />
+ <antcall target="collect.zips">
+ <param name="inputRepos" value="1,2,3,4,5" />
+ <param name="inputRepo1" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." />
+ <param name="inputRepo2" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." />
+ <param name="inputRepo3" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." />
+ <param name="inputRepo4" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-savara-1.1..." />
+ <param name="inputRepo5" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-savara-1.1..." />
+ </antcall>
+ </target>
+
+ <target name="test.collect.zips.from.list.with.errors" depends="init">
+ <property name="isTest" value="true" />
+ <antcall target="collect.zips">
+ <param name="inputRepos" value="1,2" />
+ <param name="inputRepo2" value="http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2_trunk...." />
+ </antcall>
+ </target>
+
+ <target name="test.collect.zips" depends="test.collect.zips.from.metadata,test.collect.zips.from.list">
+ <delete dir="${aggegate.zips.dir}" quiet="true" />
+ </target>
+
+ <target name="test.collect.zips.with.error" depends="test.collect.zips.from.metadata.with.errors,test.collect.zips.from.list.with.errors">
+ <delete dir="${aggegate.zips.dir}" quiet="true" />
+ </target>
+
</project>
Modified: trunk/build/aggregate/site/pom.xml
===================================================================
--- trunk/build/aggregate/site/pom.xml 2010-12-09 20:42:34 UTC (rev 27299)
+++ trunk/build/aggregate/site/pom.xml 2010-12-09 20:42:44 UTC (rev 27300)
@@ -14,18 +14,8 @@
<packaging>eclipse-update-site</packaging>
<properties>
- <!-- add more inputRepo# here, then reference below; need variables so
- that these can be referred to in Ant script later -->
- <!-- <inputRepo1>http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta...</inputRepo1>
- <inputRepo2>http://download.jboss.org/jbosstools/builds/staging/pi4soa-3.1.x</inputRepo2>
- <inputRepo3>http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi...</inputRepo3>
- <inputRepo4>http://download.jboss.org/jbosstools/builds/staging/jbosstools-drools-5.2</inputRepo4>
- <inputRepo5>http://download.jboss.org/jbosstools/builds/staging/jbosstools-savara-1.1.x</inputRepo5>
- <inputRepo6>http://download.jboss.org/jbosstools/builds/staging/jbosstools-tests</inputRepo6>
- <inputRepo7>http://download.jboss.org/jbosstools/builds/staging/jbosstools-common</inputRepo7>
- <inputRepo8>http://download.jboss.org/jbosstools/builds/staging/jbosstools-jmx</inputRepo8>
- <inputRepos>1,2,3,4,5,6,7,8</inputRepos> -->
- <!-- use a single composite site so adding more jobs' output is easier -->
+ <!-- add more inputRepos into the composite metadata at the URL below. Therefore need not edit this file and add dozens of URLs
+ which need to be called by Ant script later -->
<inputRepo1>http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/</inputRepo1>
<inputRepos>1</inputRepos>
</properties>
@@ -44,11 +34,6 @@
<quiet>true</quiet>
<tasks>
<property name="inputRepo1" value="${inputRepo1}" />
- <!-- <property name="inputRepo2" value="${inputRepo2}" /> <property
- name="inputRepo3" value="${inputRepo3}" /> <property name="inputRepo4" value="${inputRepo4}"
- /> <property name="inputRepo5" value="${inputRepo5}" /> <property name="inputRepo6"
- value="${inputRepo6}" /> <property name="inputRepo7" value="${inputRepo7}"
- /> <property name="inputRepo8" value="${inputRepo8}" /> -->
<property name="inputRepos" value="${inputRepos}" />
<!-- called AFTER generating update site + zip to add in extra content -->
@@ -98,21 +83,6 @@
<enabled>true</enabled>
</snapshots>
</repository>
- <!-- <repository> <id>inputRepo1</id> <url>${inputRepo1}/all/repo/</url>
- <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> </repository>
- <repository> <id>inputRepo2</id> <url>${inputRepo2}/all/repo/</url> <layout>p2</layout>
- <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository>
- <id>inputRepo3</id> <url>${inputRepo3}/all/repo/</url> <layout>p2</layout>
- <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository>
- <id>inputRepo4</id> <url>${inputRepo4}/all/repo/</url> <layout>p2</layout>
- <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository>
- <id>inputRepo5</id> <url>${inputRepo5}/tools/</url> <layout>p2</layout> <snapshots>
- <enabled>true</enabled> </snapshots> </repository> <repository> <id>inputRepo6</id>
- <url>${inputRepo6}/tools/</url> <layout>p2</layout> <snapshots> <enabled>true</enabled>
- </snapshots> </repository> <repository> <id>inputRepo7</id> <url>${inputRepo7}/tools/</url>
- <layout>p2</layout> <snapshots> <enabled>true</enabled> </snapshots> </repository>
- <repository> <id>inputRepo8</id> <url>${inputRepo8}/tools/</url> <layout>p2</layout>
- <snapshots> <enabled>true</enabled> </snapshots> </repository> -->
<repository>
<id>helios</id>
<url>http://download.eclipse.org/releases/helios/</url>
14 years
JBoss Tools SVN: r27299 - trunk/build/aggregate/site.
by jbosstools-commits@lists.jboss.org
Author: nickboldt
Date: 2010-12-09 15:42:34 -0500 (Thu, 09 Dec 2010)
New Revision: 27299
Modified:
trunk/build/aggregate/site/index.html
Log:
regenerate index.html
Modified: trunk/build/aggregate/site/index.html
===================================================================
--- trunk/build/aggregate/site/index.html 2010-12-09 20:16:52 UTC (rev 27298)
+++ trunk/build/aggregate/site/index.html 2010-12-09 20:42:34 UTC (rev 27299)
@@ -1,6 +1,6 @@
<html>
<head>
-<title>JBoss Tools Nightly Build Update Site: 3.2.0.M1.2010-07-16_17-40-51-H69</title>
+<title>JBoss Tools Nightly Build Update Site</title>
<style>
@import url("../web/site.css");
</style>
@@ -21,7 +21,7 @@
<h2 class="title">JBoss Tools Nightly Build Update Site</h2>
<table width="100%">
<tr class="header">
- <td class="sub-header" width="100%"><span>Latest Build: 3.2.0.M1.2010-07-16_17-40-51-H69</span></td>
+ <td class="sub-header" width="100%"><span>Latest Build</span></td>
</tr>
<tr class="light-row" style="height: 30px">
@@ -48,7 +48,7 @@
<li><a href="http://m2eclipse.sonatype.org/sites/m2e-extras/">m2eclipse 0.10 Extras</a></li>
<li><a href="http://subclipse.tigris.org/update_1.6.x"/>Subclipse 1.6 Update Site </a></li>
<li><a href="http://dl.google.com/eclipse/plugin/3.6/">Google Plugin for Eclipse 3.6 (Helios)</a></li>
- </ul>
+ </ul>
</td>
</tr>
14 years