[jbpm-commits] JBoss JBPM SVN: r4613 - in jbpm4/branches/tbaeyens: hudson/jboss and 8 other directories.

Author: tom.baeyens(a)jboss.com Date: 2009-04-24 09:38:29 -0400 (Fri, 24 Apr 2009) New Revision: 4613 Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss.eula.txt jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/build.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-hsqldb-ds.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-mysql-ds.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-oracle-ds.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-postgresql-ds.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-sybase-ds.xml jbpm4/branches/tbaeyens/modules/distro/src/main/files/license.txt jbpm4/branches/tbaeyens/modules/distro/src/main/files/readme.html jbpm4/branches/tbaeyens/qa/ jbpm4/branches/tbaeyens/qa/build.xml Removed: jbpm4/branches/tbaeyens/hudson/jboss/build.xml jbpm4/branches/tbaeyens/modules/distro/src/main/resources/jboss.eula.txt jbpm4/branches/tbaeyens/modules/distro/src/main/resources/license.txt jbpm4/branches/tbaeyens/modules/distro/src/main/resources/readme.html Modified: jbpm4/branches/tbaeyens/modules/distro/pom.xml jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-distro.xml jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-jbpm-single-jar.xml Log: added ant based jboss installer Deleted: jbpm4/branches/tbaeyens/hudson/jboss/build.xml =================================================================== --- jbpm4/branches/tbaeyens/hudson/jboss/build.xml 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/hudson/jboss/build.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<project name="jbpm.jboss.install"> - - <property file="build.properties" /> - - <property name="jboss.version" value="5.0.0.GA" /> - <property name="jboss.distro" value="C:/Downloads/jboss/jboss-${jboss.version}.zip" /> - <property name="jboss.home" value="C:/Software/jboss-${jboss.version}" /> - - <target name="clean.install" - depends="delete.jboss.installation, install.jboss, install.jbpm" - description="re-installs jboss and then installs jbpm in there" /> - - <target name="delete.jboss.installation"> - <delete dir="${jboss.home}" /> - </target> - - <target name="install.jboss"> - <unzip src="${jboss.distro}" dest="${jboss.home}/.." /> - </target> - - <target name="install.jbpm"> - <copy todir="${jboss.home}"> - <fileset dir="C:/Software/jbpm-4.0.0-before/jboss-5.0.0.GA" /> - </copy> - </target> - -</project> Modified: jbpm4/branches/tbaeyens/modules/distro/pom.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/pom.xml 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/pom.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -175,12 +175,13 @@ <executions> <execution> - <id>generate-jbpm-single-jar</id> + <id>create-jbpm-single-jar</id> <phase>process-resources</phase> <goals> <goal>single</goal> </goals> <configuration> + <finalName>jbpm</finalName> <ignoreDirFormatExtensions>true</ignoreDirFormatExtensions> <appendAssemblyId>false</appendAssemblyId> <descriptors> @@ -190,12 +191,13 @@ </execution> <execution> - <id>prepare-files-for-installer</id> + <id>create-distribution-package</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> + <finalName>jbpm-${version}</finalName> <ignoreDirFormatExtensions>true</ignoreDirFormatExtensions> <appendAssemblyId>false</appendAssemblyId> <descriptors> Modified: jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-distro.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-distro.xml 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-distro.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -16,22 +16,42 @@ <!-- Dependency Sets --> <dependencySets> <!-- lib --> - <dependencySet> + <!-- dependencySet> <outputDirectory>lib</outputDirectory> <outputFileNameMapping>${artifact.artifactId}${dashClassifier?}.${artifact.extension}</outputFileNameMapping> <useStrictFiltering>true</useStrictFiltering> <scope>provided</scope> <unpack>false</unpack> - </dependencySet> + </dependencySet --> <dependencySet> <outputDirectory>lib</outputDirectory> <outputFileNameMapping>${artifact.artifactId}${dashClassifier?}.${artifact.extension}</outputFileNameMapping> <useStrictFiltering>true</useStrictFiltering> + <unpack>false</unpack> <scope>test</scope> - <unpack>false</unpack> + <excludes> + <exclude>org.jbpm.jbpm4:jbpm-api:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-log:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-test-base:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-pvm:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-jpdl:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-enterprise:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-distro:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-examples:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-gpd:zip</exclude> + <exclude>org.jbpm.jbpm4:jbpm-test-db:jar</exclude> + <exclude>org.jbpm.jbpm4:jbpm-jboss*:jar</exclude> + </excludes> </dependencySet> <dependencySet> <includes> + <include>org.jbpm.jbpm4:jbpm-jboss*:jar</include> + </includes> + <outputFileNameMapping>${artifact.artifactId}${dashClassifier?}.${artifact.extension}</outputFileNameMapping> + <outputDirectory>jboss/lib</outputDirectory> + </dependencySet> + <dependencySet> + <includes> <include>org.jbpm.jbpm4:jbpm-gpd:zip</include> </includes> <outputFileNameMapping>jbpm-gpd-site.zip</outputFileNameMapping> @@ -39,7 +59,7 @@ </dependencySet> <!-- resources --> <dependencySet> - <outputDirectory>resources/jbpm-enterprise-config</outputDirectory> + <outputDirectory>jboss/jbpm-enterprise-config</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <includes> <include>*:jbpm-enterprise:jar:config</include> @@ -47,7 +67,7 @@ <unpack>true</unpack> </dependencySet> <dependencySet> - <outputDirectory>resources/jbpm-spi-config</outputDirectory> + <outputDirectory>jboss/jbpm-spi-config</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <includes> <include>*:jbpm-spi:jar:config</include> @@ -55,7 +75,7 @@ <unpack>true</unpack> </dependencySet> <dependencySet> - <outputDirectory>resources/jbpm-console-config</outputDirectory> + <outputDirectory>jboss/jbpm-console-config</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <includes> <include>*:jbpm-console-integration:jar:config</include> @@ -63,7 +83,7 @@ <unpack>true</unpack> </dependencySet> <dependencySet> - <outputDirectory>resources/jbpm-jboss5-config</outputDirectory> + <outputDirectory>jboss/jbpm-jboss5-config</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <includes> <include>*:jbpm-jboss5:jar:config</include> @@ -71,7 +91,7 @@ <unpack>true</unpack> </dependencySet> <dependencySet> - <outputDirectory>resources/jbpm-jboss4-config</outputDirectory> + <outputDirectory>jboss/jbpm-jboss4-config</outputDirectory> <useStrictFiltering>true</useStrictFiltering> <includes> <include>*:jbpm-jboss4:jar:config</include> @@ -82,21 +102,23 @@ <fileSets> <fileSet> - <directory>src/main/resources</directory> + <directory>src/main/files</directory> + <outputDirectory></outputDirectory> + </fileSet> + <fileSet> + <directory>target</directory> + <outputDirectory></outputDirectory> <includes> - <include>jboss.eula.txt</include> - <include>license.txt</include> - <include>readme.html</include> + <include>jbpm.jar</include> </includes> - <outputDirectory></outputDirectory> </fileSet> <fileSet> <directory>../api/target/apidocs</directory> <outputDirectory>doc/javadocs</outputDirectory> </fileSet> <fileSet> - <directory>../api/target/schemadoc</directory> - <outputDirectory>doc/schemadoc</outputDirectory> + <directory>../api/target/schemadocs</directory> + <outputDirectory>doc/schemadocs</outputDirectory> </fileSet> <fileSet> <directory>../devguide/target/docbook/publish/en</directory> Modified: jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-jbpm-single-jar.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-jbpm-single-jar.xml 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/scripts/assembly-jbpm-single-jar.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -4,7 +4,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd"> - <id>jbpm.all.jar</id> + <id>jbpm.single.jar</id> <finalName>jbpm</finalName> <formats> @@ -49,5 +49,12 @@ <unpack>true</unpack> <outputDirectory></outputDirectory> </dependencySet> + <dependencySet> + <includes> + <include>org.jbpm.jbpm4:jbpm-enterprise</include> + </includes> + <unpack>true</unpack> + <outputDirectory></outputDirectory> + </dependencySet> </dependencySets> </assembly> Copied: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/build.xml (from rev 4607, jbpm4/branches/tbaeyens/hudson/jboss/build.xml) =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/build.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/build.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,155 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<project name="jbpm.jboss.install"> + + <!-- this allows for developer-specific configurations --> + <property file="${user.home}/.jbpm4/build.properties" /> + + <!-- the default values here should reflect the qa environment --> + <property name="tmp.dir" value="c:/temp/jbpmqa" /> + <property name="jboss.version" value="5.0.0.GA" /> + <property name="jboss.filename" value="jboss-${jboss.version}.zip" /> + <property name="jboss.distro.url" value="file:///c:/downloads/jboss/${jboss.filename}" /> + <property name="jboss.distro.local.path" value="${tmp.dir}/${jboss.filename}" /> + <property name="jboss.home" value="c:/software/jboss-${jboss.version}" /> + <property name="jboss.server.configuration" value="default" /> + <property name="jboss.server.config.dir" value="${jboss.home}/server/${jboss.server.configuration}" /> + + <property name="jbpm.version" value="4.0.0-SNAPSHOT" /> + <property name="jbpm.home" value="c:/software/jbpm-${jbpm.version}" /> + + <property name="database" value="hsqldb" /> + + <condition property="jboss.version.500"> + <equals arg1="${jboss.version}" arg2="5.0.0.GA" /> + </condition> + <condition property="database.hsqldb"> + <equals arg1="${database}" arg2="hsqldb" /> + </condition> + + + <!-- ### MAIN TARGET TO INSTALL JBPM INTO JBOSS ######################### --> + <target name="install.jbpm.into.jboss"> + <antcall target="install.jbpm.into.jboss.generics" /> + <antcall target="install.jbpm.into.jboss.500specifics" /> + <antcall target="install.jbpm.into.jboss.db.hsqldb" /> + </target> + + <!-- ### THE JBOSS GENERIC PART ######################################### --> + <target name="install.jbpm.into.jboss.generics"> + <copy todir="${jboss.server.config.dir}/lib" overwrite="true"> + <fileset dir="${jbpm.home}"> + <include name="jbpm.jar" /> + </fileset> + <fileset dir="${jbpm.home}/lib"> + <include name="gwt-console-server-integration.jar" /> + <include name="gwt-console-rpc.jar" /> + </fileset> + </copy> + + <copy todir="${jboss.server.config.dir}/deploy/jbpm" overwrite="true"> + <fileset dir="${jbpm.home}/lib"> + <include name="gwt-console.war" /> + <include name="gwt-console-server.war" /> + </fileset> + </copy> + + <copy todir="${jboss.server.config.dir}/deploy/jbpm/jbpm-service.sar" overwrite="true"> + <fileset dir="${jbpm.home}/lib"> + <include name="jbpm-console-integration.jar" /> + <include name="livetribe-jsr223.jar" /> + <include name="juel*.jar" /> + <include name="jbpm-spi.jar"/> + <include name="jbpm-jboss5.jar"/> + </fileset> + </copy> + + <copy todir="${jboss.server.config.dir}/deploy/jbpm/jbpm-service.sar/META-INF" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/jbpm-console-config"> + <include name="jboss-service.xml" /> + </fileset> + </copy> + + <copy todir="${jboss.server.config.dir}/deploy/jbpm" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/jbpm-enterprise-config"> + <include name="jbpm-destinations-service.xml"/> + </fileset> + </copy> + + <mkdir dir="${jboss.home}/docs/examples/jbpm" /> + <copy todir="${jboss.home}/docs/examples/jbpm" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/datasources" /> + </copy> + </target> + + <!-- ### THE JBOSS 5.0.0.GA SPECIFIC PART ############################### --> + <target name="install.jbpm.into.jboss.500specifics" if="jboss.version.500"> + <copy todir="${jboss.server.config.dir}/deploy/jbpm/jbpm-service.sar" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/lib"> + <include name="jbpm-jboss5.jar"/> + </fileset> + <fileset dir="${jbpm.home}/lib"> + <include name="jbpm-spi.jar"/> + </fileset> + <fileset dir="${jbpm.home}/jboss/jbpm-jboss5-config"> + <include name="jbpm-service-jboss-beans.xml"/> + </fileset> + </copy> + </target> + + <!-- ### THE HSQLDB SPECIFIC PART ####################################### --> + <target name="install.jbpm.into.jboss.db.hsqldb" if="database.hsqldb"> + <copy todir="${jboss.server.config.dir}/deploy/jbpm" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/datasources"> + <include name="jbpm-hsqldb-ds.xml"/> + </fileset> + </copy> + </target> + + <!-- ### THE MYSQL SPECIFIC PART ####################################### --> + <target name="install.jbpm.into.jboss.db.mysql" if="database.mysql"> + <copy todir="${jboss.server.config.dir}/deploy/jbpm" overwrite="true"> + <fileset dir="${jbpm.home}/jboss/datasources"> + <!-- TODO define jdbc property filters --> + <include name="jbpm-mysql-ds.xml"/> + </fileset> + </copy> + <copy todir="${jboss.server.config.dir}/deploy/jbpm/jbpm-service.sar" overwrite="true"> + <fileset dir="${jbpm.home}/lib"> + <include name="mysql-connector-java.jar"/> + </fileset> + </copy> + </target> + + <!-- ### THE ORACLE SPECIFIC PART ####################################### --> + <target name="install.jbpm.into.jboss.db.oracle" if="database.oracle"> + <copy todir="${jboss.server.config.dir}/deploy/jbpm" overwrite="true"> + <!-- TODO define jdbc property filters --> + <fileset dir="${jbpm.home}/jboss/datasources"> + <include name="jbpm-oracle-ds.xml"/> + </fileset> + </copy> + </target> + + + <!-- ### JBOSS INSTALLATION TARGETS ##################################### --> + <target name="reinstall.jboss" + depends="delete.jboss.installation, install.jboss" + description="re-installs jboss and then installs jbpm in there" /> + + <target name="delete.jboss.installation"> + <delete dir="${jboss.home}" /> + </target> + + <target name="install.jboss"> + <available file="${jboss.distro.local.path}" property="jboss.available.locally" /> + <antcall target="get.jboss" /> + <unzip src="${jboss.distro.local.path}" dest="${jboss.home}/.." /> + </target> + + <target name="get.jboss" unless="jboss.available.locally"> + <mkdir dir="${tmp.dir}" /> + <get src="${jboss.distro.url}" dest="${jboss.distro.local.path}" /> + </target> + +</project> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/build.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-hsqldb-ds.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-hsqldb-ds.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-hsqldb-ds.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,37 @@ +<?xml version="1.0" encoding="UTF-8"?> +<datasources> + + <local-tx-datasource> + <jndi-name>JbpmDS</jndi-name> + + <connection-url>jdbc:hsqldb:hsql://localhost/jbpm4DB</connection-url> + <driver-class>org.hsqldb.jdbcDriver</driver-class> + <user-name>sa</user-name> + <password></password> + + <!-- connection pool parameters --> + <min-pool-size>1</min-pool-size> + <max-pool-size>5</max-pool-size> + + <!-- disable idle connection removal, hsqldb does not reap threads on closed connections --> + <idle-timeout-minutes>0</idle-timeout-minutes> + <!-- check all statements are closed when the connection is returned to the pool --> + <track-statements /> + <!-- hsqldb benefits from prepared statement caching --> + <prepared-statement-cache-size>32</prepared-statement-cache-size> + + <!-- corresponding type-mapping in conf/standardjbosscmp-jdbc.xml --> + <metadata> + <type-mapping>Hypersonic SQL</type-mapping> + </metadata> + + <!-- ensure the datasource is not initialized before the database itself --> + <depends>jboss:service=Hypersonic,database=jbpm4DB</depends> + </local-tx-datasource> + + <mbean code="org.jboss.jdbc.HypersonicDatabase" name="jboss:service=Hypersonic,database=jbpm4DB"> + <attribute name="Database">jbpm4DB</attribute> + <attribute name="InProcessMode">false</attribute> + </mbean> + +</datasources> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-hsqldb-ds.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-mysql-ds.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-mysql-ds.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-mysql-ds.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,35 @@ +<?xml version="1.0" encoding="UTF-8"?> +<datasources> + + <xa-datasource> + <jndi-name>JbpmDS</jndi-name> + + <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class> + <xa-datasource-property name=&quot;ServerName&quot;&gt;@jdbc.mysql.server(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;PortNumber&quot;&gt;@jdbc.mysql.port(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;DatabaseName&quot;&gt;@jdbc.mysql.database(a)&lt;/xa-datasource-property&gt; + <user-name&gt;@jdbc.mysql.username(a)&lt;/user-name&gt; + <password&gt;@jdbc.mysql.password(a)&lt;/password&gt; + + <!-- reduce isolation from the default level (repeatable read) --> + <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> + <!-- separate connections used with and without JTA transaction --> + <no-tx-separate-pools /> + <!-- disable transaction interleaving --> + <track-connection-by-tx /> + + <!-- leverage mysql integration features --> + <exception-sorter-class-name> + com.mysql.jdbc.integration.jboss.ExtendedMysqlExceptionSorter + </exception-sorter-class-name> + <valid-connection-checker-class-name> + com.mysql.jdbc.integration.jboss.MysqlValidConnectionChecker + </valid-connection-checker-class-name> + + <!-- corresponding type-mapping in conf/standardjbosscmp-jdbc.xml --> + <metadata> + <type-mapping>mySQL</type-mapping> + </metadata> + </xa-datasource> + +</datasources> \ No newline at end of file Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-mysql-ds.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-oracle-ds.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-oracle-ds.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-oracle-ds.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,43 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<!-- ===================================================================== --> +<!-- --> +<!-- JBoss Server Configuration --> +<!-- --> +<!-- ===================================================================== --> + +<!-- $Id: jbpm-oracle-ds.xml 4458 2009-04-06 14:36:41Z heiko.braun(a)jboss.com $ --> + +<!-- ===================================================================== --> +<!-- ATTENTION: DO NOT FORGET TO SET Pad=true IN transaction-service.xml --> +<!-- ===================================================================== --> + +<datasources> + <xa-datasource> + <jndi-name>JbpmDS</jndi-name> + <track-connection-by-tx/> + <!-- uncomment to enable interleaving <interleaving/> --> + <isSameRM-override-value>false</isSameRM-override-value> + <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> + <xa-datasource-property name="URL">jdbc:oracle:thin:@jdbc.oracle.username@/@jdbc.oracle.password@@@jdbc.oracle.server@:@jdbc.oracle.port@:@jdbc.oracle.database@</xa-datasource-property> + <xa-datasource-property name=&quot;User&quot;&gt;@jdbc.oracle.username(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;Password&quot;&gt;@jdbc.oracle.password(a)&lt;/xa-datasource-property&gt; + <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool --> + <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name--> + <!-- Checks the Oracle error codes and messages for fatal errors --> + <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name> + <!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa --> + <no-tx-separate-pools/> + + <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> + <metadata> + <type-mapping>Oracle9i</type-mapping> + </metadata> + </xa-datasource> + + <mbean code="org.jboss.resource.adapter.jdbc.vendor.OracleXAExceptionFormatter" + name="jboss.jca:service=OracleXAExceptionFormatter"> + <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends> + </mbean> + +</datasources> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-oracle-ds.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-postgresql-ds.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-postgresql-ds.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-postgresql-ds.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="UTF-8"?> +<datasources> + + <xa-datasource> + <jndi-name>JbpmDS</jndi-name> + + <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class> + <xa-datasource-property name=&quot;ServerName&quot;&gt;@jdbc.postgresql.server(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;PortNumber&quot;&gt;@jdbc.postgresql.port(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;DatabaseName&quot;&gt;@jdbc.postgresql.database(a)&lt;/xa-datasource-property&gt; + <user-name&gt;@jdbc.postgresql.username(a)&lt;/user-name&gt; + <password&gt;@jdbc.postgresql.password(a)&lt;/password&gt; + + <!-- disable transaction interleaving --> + <track-connection-by-tx /> + + <!-- corresponding type-mapping in conf/standardjbosscmp-jdbc.xml --> + <metadata> + <type-mapping>PostgreSQL 8.0</type-mapping> + </metadata> + </xa-datasource> + +</datasources> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-postgresql-ds.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-sybase-ds.xml =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-sybase-ds.xml (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-sybase-ds.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,28 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<datasources> + + <xa-datasource> + <jndi-name>JbpmDS</jndi-name> + + <xa-datasource-class&gt;@jdbc.sybase.datasource(a)&lt;/xa-datasource-class&gt; + <xa-datasource-property name=&quot;ServerName&quot;&gt;@jdbc.sybase.server(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;PortNumber&quot;&gt;@jdbc.sybase.port(a)&lt;/xa-datasource-property&gt; + <xa-datasource-property name=&quot;DatabaseName&quot;&gt;@jdbc.sybase.database(a)&lt;/xa-datasource-property&gt; + <user-name&gt;@jdbc.sybase.username(a)&lt;/user-name&gt; + <password&gt;@jdbc.sybase.password(a)&lt;/password&gt; + + <!-- disable transaction interleaving --> + <track-connection-by-tx /> + + <exception-sorter-class-name> + org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter + </exception-sorter-class-name> + + <!-- corresponding type-mapping in conf/standardjbosscmp-jdbc.xml --> + <metadata> + <type-mapping>Sybase</type-mapping> + </metadata> + </xa-datasource> + +</datasources> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss/datasources/jbpm-sybase-ds.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Copied: jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss.eula.txt (from rev 4603, jbpm4/branches/tbaeyens/modules/distro/src/main/resources/jboss.eula.txt) =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss.eula.txt (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/jboss.eula.txt 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,107 @@ +LICENSE AGREEMENT +JBOSS(r) + +This License Agreement governs the use of the Software Packages and any updates to the Software +Packages, regardless of the delivery mechanism. Each Software Package is a collective work +under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to +the user ("Client") a license to the applicable collective work(s) pursuant to the +GNU Lesser General Public License v. 2.1 except for the following Software Packages: +(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the +GNU General Public License v.2; + +(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0; + +(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the +(open source) Sleepycat License (if Client does not wish to use the open source version of this database, +it may purchase a license from Sleepycat Software); + +and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1, +and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various +royalty-free patent licenses. + +Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php. + +1. The Software. "Software Packages" refer to the various software modules that are created and made available +for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages +may be comprised of hundreds of software components. The end user license agreement for each component is located in +the component's source code. With the exception of certain image files identified in Section 2 below, +the license terms for the components permit Client to copy, modify, and redistribute the component, +in both source code and binary code forms. This agreement does not limit Client's rights under, +or grant Client rights that supersede, the license terms of any particular component. + +2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright +and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall +remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the +individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates +in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages +using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's +trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by +these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified. +If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at +http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted. +Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages. + +3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular +component, to the maximum extent permitted under applicable law, the Software Packages and the +components are provided and licensed "as is" without warranty of any kind, expressed or implied, +including the implied warranties of merchantability, non-infringement or fitness for a particular purpose. +Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in +materials and manufacture under normal use for a period of 30 days from the date of delivery to Client. +Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements +or that the operation of the Software Packages will be entirely error free or appear precisely as described +in the accompanying documentation. This warranty extends only to the party that purchases the Services +pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor. + +4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies +described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's +exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of +delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or +refund the money paid by Client for the Software. To the maximum extent permitted by applicable law, +Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential +damages, including lost profits or lost savings arising out of the use or inability to use the Software, +even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall +Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this +Agreement during the twelve months preceding the action. + +5. Export Control. As required by U.S. law, Client represents and warrants that it: +(a) understands that the Software Packages are subject to export controls under the +U.S. Commerce Department's Export Administration Regulations ("EAR"); + +(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations +(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); + +(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity, +or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; + +(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or +biological weapons, or missile technology end-uses unless authorized by the U.S. Government by +regulation or specific license; + +(e) understands and agrees that if it is in the United States and exports or transfers the Software +Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual +reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and +address (including country) of each transferee; + +and (f) understands that countries other than the United States may restrict the import, use, or +export of encryption products and that it shall be solely responsible for compliance with any such +import, use, or export restrictions. + +6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages +that are not part of the Software Packages and which Client must install separately. These third party +programs are subject to their own license terms. The license terms either accompany the programs or +can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable +license terms for such programs, then Client may not install them. If Client wishes to install the programs +on more than one system or transfer the programs to another party, then Client must contact the licensor +of the programs. + +7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the +enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the +State of North Carolina and of the United States, without regard to any conflict of laws provisions, +except that the United Nations Convention on the International Sale of Goods shall not apply. + +Copyright 2006 Red Hat, Inc. All rights reserved. +"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc. +All other trademarks are the property of their respective owners. + + Page 1 of 1 18 October 2006 + Copied: jbpm4/branches/tbaeyens/modules/distro/src/main/files/license.txt (from rev 4603, jbpm4/branches/tbaeyens/modules/distro/src/main/resources/license.txt) =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/license.txt (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/license.txt 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,504 @@ + GNU LESSER GENERAL PUBLIC LICENSE + Version 2.1, February 1999 + + Copyright (C) 1991, 1999 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts + as the successor of the GNU Library Public License, version 2, hence + the version number 2.1.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + + To protect your rights, we need to make restrictions that forbid +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. + + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. + + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. + + GNU LESSER GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties with +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + <one line to give the library's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + <signature of Ty Coon>, 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! + + Copied: jbpm4/branches/tbaeyens/modules/distro/src/main/files/readme.html (from rev 4603, jbpm4/branches/tbaeyens/modules/distro/src/main/resources/readme.html) =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/files/readme.html (rev 0) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/files/readme.html 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,143 @@ +<html> + <head> + <title>jBPM 4 Readme and Release Notes</title> + </head> + <body> + <h1>Readme</h1> + + <p>Currently the userguide and devguide only show well in <a href="http://www.mozilla.com/firefox">firefox</a>;. + We'll fix this in one of the next versions. + See <a href="https://jira.jboss.org/jira/browse/JBPM-1895">JBPM-189...;. + </p> + + <table> + <tr> + <th>Link</th> + <th>Description</th> + </tr> + <tr> + <td valign="top" style="white-space:nowrap;"><a href="doc/userguide/html_single/index.html">User guide</a></td> + <td>Userguide docs describing the stable and supported ways of how to work with jBPM.</td> + </tr> + <tr> + <td valign="top" style="white-space:nowrap;"><a href="doc/javadocs/index.html">Javadocs</a></td> + <td>Javadocs describing the stable and supported API</td> + </tr> + <tr> + <td valign="top" style="white-space:nowrap;"><a href="doc/schemadocs/index.html">Schemadocs</a></td> + <td>Javadoc-like documentation of the jPDL XML schema and the jBPM configuration file XML schema</td> + </tr> + <tr> + <td valign="top" style="white-space:nowrap;"><a href="doc/devguide/html_single/index.html">Developers guide</a></td> + <td>Describes more configuration, usage and tweaking options. + Unleash all the flexibility in jBPM. But beware, the parts documented in this dev + guide are not guaranteed to be forward compatible.</td> + </tr> + </table> + + <h1>Release notes for jBPM 4.0.0.Alpha2</h1> + +<h2> Bug +</h2> +<ul> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1980'>JBPM-1980&...>] - Failed to initialze ScriptEngineManager on JDK 1.5 +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1981'>JBPM-1981&...>] - Example tests fail +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2049'>JBPM-2049&...>] - hbm2ddl.auto doesn't work within AS +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2072'>JBPM-2072&...>] - ConnectionManager deadlock running XA transaction on AS 4 +</li> +</ul> + +<h2> Feature Request +</h2> +<ul> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1946'>JBPM-1946&...>] - IzPack installer for jBPM4 that supports JBoss +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1993'>JBPM-1993&...>] - Interface with the JBoss identity component +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1998'>JBPM-1998&...>] - Dinstinction between candiadate-groups and candidate-users in Task API and model +</li> +</ul> + +<h2> Task +</h2> +<ul> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1246'>JBPM-1246&...>] - document build +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1280'>JBPM-1280&...>] - build out job executor basic test coverage +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1411'>JBPM-1411&...>] - migrate enterprise into separate module +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1753'>JBPM-1753&...>] - review event names +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1759'>JBPM-1759&...>] - cleanup excluded tests +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1861'>JBPM-1861&...>] - complete taskservice api +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1967'>JBPM-1967&...>] - rename flow to transition +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1971'>JBPM-1971&...>] - fix test-load hudson job in qa lab +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1972'>JBPM-1972&...>] - introduce process definition attachments +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1973'>JBPM-1973&...>] - finish programmatic process definition creation +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1974'>JBPM-1974&...>] - rename node to activity +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1977'>JBPM-1977&...>] - Provide process management through the GWT console on jbpm4 +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1978'>JBPM-1978&...>] - configure pvm2 user for hudson job jbpm4-load +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1983'>JBPM-1983&...>] - rename context environment to transaction +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1986'>JBPM-1986&...>] - rename ExecutionService.startExecutionXxx methods to startProcessInstanceXxx +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1997'>JBPM-1997&...>] - API package refactoring +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2003'>JBPM-2003&...>] - document release procedure in a wiki page +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2020'>JBPM-2020&...>] - fix timer mapping +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2032'>JBPM-2032&...>] - verify blob caching +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2039'>JBPM-2039&...>] - initial history infrastructure +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2041'>JBPM-2041&...>] - move task mgmt into pvm module +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2044'>JBPM-2044&...>] - Distribute GPD through the installer +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2063'>JBPM-2063&...>] - examples hibernate configuration file +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2064'>JBPM-2064&...>] - re-introduce schema sql scripts in distro +</li> +</ul> + +<h2> Sub-task +</h2> +<ul> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2011'>JBPM-2011&...>] - Move non public classes to **/internal +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2012'>JBPM-2012&...>] - Split jars into *-api.jar and *-impl.jar +</li> +</ul> + +<h2> Task +</h2> +<ul> +<li>[<a href='https://jira.jboss.org/jira/browse/GPD-281'>GPD-281</a>] - Release jBPM Designer 4.0.0 Alpha2 +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/GPD-283'>GPD-283</a>] - Implement a tree structured details view for graphical entities +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/GPD-287'>GPD-287</a>] - XML preservation +</li> +<li>[<a href='https://jira.jboss.org/jira/browse/GPD-294'>GPD-294</a>] - Update to new icons +</li> +</ul> + + + <h1>Release notes for jBPM 4.0.0.Alpha1</h1> + <p>Finally.. phew !</p> + </body> +</html> Property changes on: jbpm4/branches/tbaeyens/modules/distro/src/main/files/readme.html ___________________________________________________________________ Name: svn:mergeinfo + Deleted: jbpm4/branches/tbaeyens/modules/distro/src/main/resources/jboss.eula.txt =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/resources/jboss.eula.txt 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/resources/jboss.eula.txt 2009-04-24 13:38:29 UTC (rev 4613) @@ -1,107 +0,0 @@ -LICENSE AGREEMENT -JBOSS(r) - -This License Agreement governs the use of the Software Packages and any updates to the Software -Packages, regardless of the delivery mechanism. Each Software Package is a collective work -under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to -the user ("Client") a license to the applicable collective work(s) pursuant to the -GNU Lesser General Public License v. 2.1 except for the following Software Packages: -(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the -GNU General Public License v.2; - -(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0; - -(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the -(open source) Sleepycat License (if Client does not wish to use the open source version of this database, -it may purchase a license from Sleepycat Software); - -and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1, -and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various -royalty-free patent licenses. - -Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php. - -1. The Software. "Software Packages" refer to the various software modules that are created and made available -for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages -may be comprised of hundreds of software components. The end user license agreement for each component is located in -the component's source code. With the exception of certain image files identified in Section 2 below, -the license terms for the components permit Client to copy, modify, and redistribute the component, -in both source code and binary code forms. This agreement does not limit Client's rights under, -or grant Client rights that supersede, the license terms of any particular component. - -2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright -and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall -remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the -individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates -in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages -using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's -trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by -these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified. -If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at -http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted. -Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages. - -3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular -component, to the maximum extent permitted under applicable law, the Software Packages and the -components are provided and licensed "as is" without warranty of any kind, expressed or implied, -including the implied warranties of merchantability, non-infringement or fitness for a particular purpose. -Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in -materials and manufacture under normal use for a period of 30 days from the date of delivery to Client. -Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements -or that the operation of the Software Packages will be entirely error free or appear precisely as described -in the accompanying documentation. This warranty extends only to the party that purchases the Services -pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor. - -4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies -described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's -exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of -delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or -refund the money paid by Client for the Software. To the maximum extent permitted by applicable law, -Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential -damages, including lost profits or lost savings arising out of the use or inability to use the Software, -even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall -Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this -Agreement during the twelve months preceding the action. - -5. Export Control. As required by U.S. law, Client represents and warrants that it: -(a) understands that the Software Packages are subject to export controls under the -U.S. Commerce Department's Export Administration Regulations ("EAR"); - -(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations -(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); - -(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity, -or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; - -(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or -biological weapons, or missile technology end-uses unless authorized by the U.S. Government by -regulation or specific license; - -(e) understands and agrees that if it is in the United States and exports or transfers the Software -Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual -reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and -address (including country) of each transferee; - -and (f) understands that countries other than the United States may restrict the import, use, or -export of encryption products and that it shall be solely responsible for compliance with any such -import, use, or export restrictions. - -6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages -that are not part of the Software Packages and which Client must install separately. These third party -programs are subject to their own license terms. The license terms either accompany the programs or -can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable -license terms for such programs, then Client may not install them. If Client wishes to install the programs -on more than one system or transfer the programs to another party, then Client must contact the licensor -of the programs. - -7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the -enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the -State of North Carolina and of the United States, without regard to any conflict of laws provisions, -except that the United Nations Convention on the International Sale of Goods shall not apply. - -Copyright 2006 Red Hat, Inc. All rights reserved. -"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc. -All other trademarks are the property of their respective owners. - - Page 1 of 1 18 October 2006 - Deleted: jbpm4/branches/tbaeyens/modules/distro/src/main/resources/license.txt =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/resources/license.txt 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/resources/license.txt 2009-04-24 13:38:29 UTC (rev 4613) @@ -1,504 +0,0 @@ - GNU LESSER GENERAL PUBLIC LICENSE - Version 2.1, February 1999 - - Copyright (C) 1991, 1999 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - -[This is the first released version of the Lesser GPL. It also counts - as the successor of the GNU Library Public License, version 2, hence - the version number 2.1.] - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -Licenses are intended to guarantee your freedom to share and change -free software--to make sure the software is free for all its users. - - This license, the Lesser General Public License, applies to some -specially designated software packages--typically libraries--of the -Free Software Foundation and other authors who decide to use it. You -can use it too, but we suggest you first think carefully about whether -this license or the ordinary General Public License is the better -strategy to use in any particular case, based on the explanations below. - - When we speak of free software, we are referring to freedom of use, -not price. Our General Public Licenses are designed to make sure that -you have the freedom to distribute copies of free software (and charge -for this service if you wish); that you receive source code or can get -it if you want it; that you can change the software and use pieces of -it in new free programs; and that you are informed that you can do -these things. - - To protect your rights, we need to make restrictions that forbid -distributors to deny you these rights or to ask you to surrender these -rights. These restrictions translate to certain responsibilities for -you if you distribute copies of the library or if you modify it. - - For example, if you distribute copies of the library, whether gratis -or for a fee, you must give the recipients all the rights that we gave -you. You must make sure that they, too, receive or can get the source -code. If you link other code with the library, you must provide -complete object files to the recipients, so that they can relink them -with the library after making changes to the library and recompiling -it. And you must show them these terms so they know their rights. - - We protect your rights with a two-step method: (1) we copyright the -library, and (2) we offer you this license, which gives you legal -permission to copy, distribute and/or modify the library. - - To protect each distributor, we want to make it very clear that -there is no warranty for the free library. Also, if the library is -modified by someone else and passed on, the recipients should know -that what they have is not the original version, so that the original -author's reputation will not be affected by problems that might be -introduced by others. - - Finally, software patents pose a constant threat to the existence of -any free program. We wish to make sure that a company cannot -effectively restrict the users of a free program by obtaining a -restrictive license from a patent holder. Therefore, we insist that -any patent license obtained for a version of the library must be -consistent with the full freedom of use specified in this license. - - Most GNU software, including some libraries, is covered by the -ordinary GNU General Public License. This license, the GNU Lesser -General Public License, applies to certain designated libraries, and -is quite different from the ordinary General Public License. We use -this license for certain libraries in order to permit linking those -libraries into non-free programs. - - When a program is linked with a library, whether statically or using -a shared library, the combination of the two is legally speaking a -combined work, a derivative of the original library. The ordinary -General Public License therefore permits such linking only if the -entire combination fits its criteria of freedom. The Lesser General -Public License permits more lax criteria for linking other code with -the library. - - We call this license the "Lesser" General Public License because it -does Less to protect the user's freedom than the ordinary General -Public License. It also provides other free software developers Less -of an advantage over competing non-free programs. These disadvantages -are the reason we use the ordinary General Public License for many -libraries. However, the Lesser license provides advantages in certain -special circumstances. - - For example, on rare occasions, there may be a special need to -encourage the widest possible use of a certain library, so that it becomes -a de-facto standard. To achieve this, non-free programs must be -allowed to use the library. A more frequent case is that a free -library does the same job as widely used non-free libraries. In this -case, there is little to gain by limiting the free library to free -software only, so we use the Lesser General Public License. - - In other cases, permission to use a particular library in non-free -programs enables a greater number of people to use a large body of -free software. For example, permission to use the GNU C Library in -non-free programs enables many more people to use the whole GNU -operating system, as well as its variant, the GNU/Linux operating -system. - - Although the Lesser General Public License is Less protective of the -users' freedom, it does ensure that the user of a program that is -linked with the Library has the freedom and the wherewithal to run -that program using a modified version of the Library. - - The precise terms and conditions for copying, distribution and -modification follow. Pay close attention to the difference between a -"work based on the library" and a "work that uses the library". The -former contains code derived from the library, whereas the latter must -be combined with the library in order to run. - - GNU LESSER GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License Agreement applies to any software library or other -program which contains a notice placed by the copyright holder or -other authorized party saying it may be distributed under the terms of -this Lesser General Public License (also called "this License"). -Each licensee is addressed as "you". - - A "library" means a collection of software functions and/or data -prepared so as to be conveniently linked with application programs -(which use some of those functions and data) to form executables. - - The "Library", below, refers to any such software library or work -which has been distributed under these terms. A "work based on the -Library" means either the Library or any derivative work under -copyright law: that is to say, a work containing the Library or a -portion of it, either verbatim or with modifications and/or translated -straightforwardly into another language. (Hereinafter, translation is -included without limitation in the term "modification".) - - "Source code" for a work means the preferred form of the work for -making modifications to it. For a library, complete source code means -all the source code for all modules it contains, plus any associated -interface definition files, plus the scripts used to control compilation -and installation of the library. - - Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running a program using the Library is not restricted, and output from -such a program is covered only if its contents constitute a work based -on the Library (independent of the use of the Library in a tool for -writing it). Whether that is true depends on what the Library does -and what the program that uses the Library does. - - 1. You may copy and distribute verbatim copies of the Library's -complete source code as you receive it, in any medium, provided that -you conspicuously and appropriately publish on each copy an -appropriate copyright notice and disclaimer of warranty; keep intact -all the notices that refer to this License and to the absence of any -warranty; and distribute a copy of this License along with the -Library. - - You may charge a fee for the physical act of transferring a copy, -and you may at your option offer warranty protection in exchange for a -fee. - - 2. You may modify your copy or copies of the Library or any portion -of it, thus forming a work based on the Library, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) The modified work must itself be a software library. - - b) You must cause the files modified to carry prominent notices - stating that you changed the files and the date of any change. - - c) You must cause the whole of the work to be licensed at no - charge to all third parties under the terms of this License. - - d) If a facility in the modified Library refers to a function or a - table of data to be supplied by an application program that uses - the facility, other than as an argument passed when the facility - is invoked, then you must make a good faith effort to ensure that, - in the event an application does not supply such function or - table, the facility still operates, and performs whatever part of - its purpose remains meaningful. - - (For example, a function in a library to compute square roots has - a purpose that is entirely well-defined independent of the - application. Therefore, Subsection 2d requires that any - application-supplied function or table used by this function must - be optional: if the application does not supply it, the square - root function must still compute square roots.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Library, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Library, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote -it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Library. - -In addition, mere aggregation of another work not based on the Library -with the Library (or with a work based on the Library) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may opt to apply the terms of the ordinary GNU General Public -License instead of this License to a given copy of the Library. To do -this, you must alter all the notices that refer to this License, so -that they refer to the ordinary GNU General Public License, version 2, -instead of to this License. (If a newer version than version 2 of the -ordinary GNU General Public License has appeared, then you can specify -that version instead if you wish.) Do not make any other change in -these notices. - - Once this change is made in a given copy, it is irreversible for -that copy, so the ordinary GNU General Public License applies to all -subsequent copies and derivative works made from that copy. - - This option is useful when you wish to copy part of the code of -the Library into a program that is not a library. - - 4. You may copy and distribute the Library (or a portion or -derivative of it, under Section 2) in object code or executable form -under the terms of Sections 1 and 2 above provided that you accompany -it with the complete corresponding machine-readable source code, which -must be distributed under the terms of Sections 1 and 2 above on a -medium customarily used for software interchange. - - If distribution of object code is made by offering access to copy -from a designated place, then offering equivalent access to copy the -source code from the same place satisfies the requirement to -distribute the source code, even though third parties are not -compelled to copy the source along with the object code. - - 5. A program that contains no derivative of any portion of the -Library, but is designed to work with the Library by being compiled or -linked with it, is called a "work that uses the Library". Such a -work, in isolation, is not a derivative work of the Library, and -therefore falls outside the scope of this License. - - However, linking a "work that uses the Library" with the Library -creates an executable that is a derivative of the Library (because it -contains portions of the Library), rather than a "work that uses the -library". The executable is therefore covered by this License. -Section 6 states terms for distribution of such executables. - - When a "work that uses the Library" uses material from a header file -that is part of the Library, the object code for the work may be a -derivative work of the Library even though the source code is not. -Whether this is true is especially significant if the work can be -linked without the Library, or if the work is itself a library. The -threshold for this to be true is not precisely defined by law. - - If such an object file uses only numerical parameters, data -structure layouts and accessors, and small macros and small inline -functions (ten lines or less in length), then the use of the object -file is unrestricted, regardless of whether it is legally a derivative -work. (Executables containing this object code plus portions of the -Library will still fall under Section 6.) - - Otherwise, if the work is a derivative of the Library, you may -distribute the object code for the work under the terms of Section 6. -Any executables containing that work also fall under Section 6, -whether or not they are linked directly with the Library itself. - - 6. As an exception to the Sections above, you may also combine or -link a "work that uses the Library" with the Library to produce a -work containing portions of the Library, and distribute that work -under terms of your choice, provided that the terms permit -modification of the work for the customer's own use and reverse -engineering for debugging such modifications. - - You must give prominent notice with each copy of the work that the -Library is used in it and that the Library and its use are covered by -this License. You must supply a copy of this License. If the work -during execution displays copyright notices, you must include the -copyright notice for the Library among them, as well as a reference -directing the user to the copy of this License. Also, you must do one -of these things: - - a) Accompany the work with the complete corresponding - machine-readable source code for the Library including whatever - changes were used in the work (which must be distributed under - Sections 1 and 2 above); and, if the work is an executable linked - with the Library, with the complete machine-readable "work that - uses the Library", as object code and/or source code, so that the - user can modify the Library and then relink to produce a modified - executable containing the modified Library. (It is understood - that the user who changes the contents of definitions files in the - Library will not necessarily be able to recompile the application - to use the modified definitions.) - - b) Use a suitable shared library mechanism for linking with the - Library. A suitable mechanism is one that (1) uses at run time a - copy of the library already present on the user's computer system, - rather than copying library functions into the executable, and (2) - will operate properly with a modified version of the library, if - the user installs one, as long as the modified version is - interface-compatible with the version that the work was made with. - - c) Accompany the work with a written offer, valid for at - least three years, to give the same user the materials - specified in Subsection 6a, above, for a charge no more - than the cost of performing this distribution. - - d) If distribution of the work is made by offering access to copy - from a designated place, offer equivalent access to copy the above - specified materials from the same place. - - e) Verify that the user has already received a copy of these - materials or that you have already sent this user a copy. - - For an executable, the required form of the "work that uses the -Library" must include any data and utility programs needed for -reproducing the executable from it. However, as a special exception, -the materials to be distributed need not include anything that is -normally distributed (in either source or binary form) with the major -components (compiler, kernel, and so on) of the operating system on -which the executable runs, unless that component itself accompanies -the executable. - - It may happen that this requirement contradicts the license -restrictions of other proprietary libraries that do not normally -accompany the operating system. Such a contradiction means you cannot -use both them and the Library together in an executable that you -distribute. - - 7. You may place library facilities that are a work based on the -Library side-by-side in a single library together with other library -facilities not covered by this License, and distribute such a combined -library, provided that the separate distribution of the work based on -the Library and of the other library facilities is otherwise -permitted, and provided that you do these two things: - - a) Accompany the combined library with a copy of the same work - based on the Library, uncombined with any other library - facilities. This must be distributed under the terms of the - Sections above. - - b) Give prominent notice with the combined library of the fact - that part of it is a work based on the Library, and explaining - where to find the accompanying uncombined form of the same work. - - 8. You may not copy, modify, sublicense, link with, or distribute -the Library except as expressly provided under this License. Any -attempt otherwise to copy, modify, sublicense, link with, or -distribute the Library is void, and will automatically terminate your -rights under this License. However, parties who have received copies, -or rights, from you under this License will not have their licenses -terminated so long as such parties remain in full compliance. - - 9. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Library or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Library (or any work based on the -Library), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Library or works based on it. - - 10. Each time you redistribute the Library (or any work based on the -Library), the recipient automatically receives a license from the -original licensor to copy, distribute, link with or modify the Library -subject to these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties with -this License. - - 11. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Library at all. For example, if a patent -license would not permit royalty-free redistribution of the Library by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Library. - -If any portion of this section is held invalid or unenforceable under any -particular circumstance, the balance of the section is intended to apply, -and the section as a whole is intended to apply in other circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 12. If the distribution and/or use of the Library is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Library under this License may add -an explicit geographical distribution limitation excluding those countries, -so that distribution is permitted only in or among countries not thus -excluded. In such case, this License incorporates the limitation as if -written in the body of this License. - - 13. The Free Software Foundation may publish revised and/or new -versions of the Lesser General Public License from time to time. -Such new versions will be similar in spirit to the present version, -but may differ in detail to address new problems or concerns. - -Each version is given a distinguishing version number. If the Library -specifies a version number of this License which applies to it and -"any later version", you have the option of following the terms and -conditions either of that version or of any later version published by -the Free Software Foundation. If the Library does not specify a -license version number, you may choose any version ever published by -the Free Software Foundation. - - 14. If you wish to incorporate parts of the Library into other free -programs whose distribution conditions are incompatible with these, -write to the author to ask for permission. For software which is -copyrighted by the Free Software Foundation, write to the Free -Software Foundation; we sometimes make exceptions for this. Our -decision will be guided by the two goals of preserving the free status -of all derivatives of our free software and of promoting the sharing -and reuse of software generally. - - NO WARRANTY - - 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO -WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. -EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR -OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY -KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE -LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME -THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH -DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Libraries - - If you develop a new library, and you want it to be of the greatest -possible use to the public, we recommend making it free software that -everyone can redistribute and change. You can do so by permitting -redistribution under these terms (or, alternatively, under the terms of the -ordinary General Public License). - - To apply these terms, attach the following notices to the library. It is -safest to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least the -"copyright" line and a pointer to where the full notice is found. - - <one line to give the library's name and a brief idea of what it does.> - Copyright (C) <year> <name of author> - - This library is free software; you can redistribute it and/or - modify it under the terms of the GNU Lesser General Public - License as published by the Free Software Foundation; either - version 2.1 of the License, or (at your option) any later version. - - This library is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - Lesser General Public License for more details. - - You should have received a copy of the GNU Lesser General Public - License along with this library; if not, write to the Free Software - Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - -Also add information on how to contact you by electronic and paper mail. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the library, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the - library `Frob' (a library for tweaking knobs) written by James Random Hacker. - - <signature of Ty Coon>, 1 April 1990 - Ty Coon, President of Vice - -That's all there is to it! - - Deleted: jbpm4/branches/tbaeyens/modules/distro/src/main/resources/readme.html =================================================================== --- jbpm4/branches/tbaeyens/modules/distro/src/main/resources/readme.html 2009-04-24 12:43:17 UTC (rev 4612) +++ jbpm4/branches/tbaeyens/modules/distro/src/main/resources/readme.html 2009-04-24 13:38:29 UTC (rev 4613) @@ -1,143 +0,0 @@ -<html> - <head> - <title>jBPM 4 Readme and Release Notes</title> - </head> - <body> - <h1>Readme</h1> - - <p>Currently the userguide and devguide only show well in <a href="http://www.mozilla.com/firefox">firefox</a>;. - We'll fix this in one of the next versions. - See <a href="https://jira.jboss.org/jira/browse/JBPM-1895">JBPM-189...;. - </p> - - <table> - <tr> - <th>Link</th> - <th>Description</th> - </tr> - <tr> - <td valign="top" style="white-space:nowrap;"><a href="doc/userguide/html_single/index.html">User guide</a></td> - <td>Userguide docs describing the stable and supported ways of how to work with jBPM.</td> - </tr> - <tr> - <td valign="top" style="white-space:nowrap;"><a href="doc/javadocs/index.html">Javadocs</a></td> - <td>Javadocs describing the stable and supported API</td> - </tr> - <tr> - <td valign="top" style="white-space:nowrap;"><a href="doc/schemadocs/index.html">Schemadocs</a></td> - <td>Javadoc-like documentation of the jPDL XML schema and the jBPM configuration file XML schema</td> - </tr> - <tr> - <td valign="top" style="white-space:nowrap;"><a href="doc/devguide/html_single/index.html">Developers guide</a></td> - <td>Describes more configuration, usage and tweaking options. - Unleash all the flexibility in jBPM. But beware, the parts documented in this dev - guide are not guaranteed to be forward compatible.</td> - </tr> - </table> - - <h1>Release notes for jBPM 4.0.0.Alpha2</h1> - -<h2> Bug -</h2> -<ul> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1980'>JBPM-1980&...>] - Failed to initialze ScriptEngineManager on JDK 1.5 -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1981'>JBPM-1981&...>] - Example tests fail -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2049'>JBPM-2049&...>] - hbm2ddl.auto doesn't work within AS -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2072'>JBPM-2072&...>] - ConnectionManager deadlock running XA transaction on AS 4 -</li> -</ul> - -<h2> Feature Request -</h2> -<ul> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1946'>JBPM-1946&...>] - IzPack installer for jBPM4 that supports JBoss -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1993'>JBPM-1993&...>] - Interface with the JBoss identity component -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1998'>JBPM-1998&...>] - Dinstinction between candiadate-groups and candidate-users in Task API and model -</li> -</ul> - -<h2> Task -</h2> -<ul> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1246'>JBPM-1246&...>] - document build -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1280'>JBPM-1280&...>] - build out job executor basic test coverage -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1411'>JBPM-1411&...>] - migrate enterprise into separate module -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1753'>JBPM-1753&...>] - review event names -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1759'>JBPM-1759&...>] - cleanup excluded tests -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1861'>JBPM-1861&...>] - complete taskservice api -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1967'>JBPM-1967&...>] - rename flow to transition -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1971'>JBPM-1971&...>] - fix test-load hudson job in qa lab -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1972'>JBPM-1972&...>] - introduce process definition attachments -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1973'>JBPM-1973&...>] - finish programmatic process definition creation -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1974'>JBPM-1974&...>] - rename node to activity -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1977'>JBPM-1977&...>] - Provide process management through the GWT console on jbpm4 -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1978'>JBPM-1978&...>] - configure pvm2 user for hudson job jbpm4-load -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1983'>JBPM-1983&...>] - rename context environment to transaction -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1986'>JBPM-1986&...>] - rename ExecutionService.startExecutionXxx methods to startProcessInstanceXxx -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-1997'>JBPM-1997&...>] - API package refactoring -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2003'>JBPM-2003&...>] - document release procedure in a wiki page -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2020'>JBPM-2020&...>] - fix timer mapping -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2032'>JBPM-2032&...>] - verify blob caching -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2039'>JBPM-2039&...>] - initial history infrastructure -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2041'>JBPM-2041&...>] - move task mgmt into pvm module -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2044'>JBPM-2044&...>] - Distribute GPD through the installer -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2063'>JBPM-2063&...>] - examples hibernate configuration file -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2064'>JBPM-2064&...>] - re-introduce schema sql scripts in distro -</li> -</ul> - -<h2> Sub-task -</h2> -<ul> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2011'>JBPM-2011&...>] - Move non public classes to **/internal -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/JBPM-2012'>JBPM-2012&...>] - Split jars into *-api.jar and *-impl.jar -</li> -</ul> - -<h2> Task -</h2> -<ul> -<li>[<a href='https://jira.jboss.org/jira/browse/GPD-281'>GPD-281</a>] - Release jBPM Designer 4.0.0 Alpha2 -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/GPD-283'>GPD-283</a>] - Implement a tree structured details view for graphical entities -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/GPD-287'>GPD-287</a>] - XML preservation -</li> -<li>[<a href='https://jira.jboss.org/jira/browse/GPD-294'>GPD-294</a>] - Update to new icons -</li> -</ul> - - - <h1>Release notes for jBPM 4.0.0.Alpha1</h1> - <p>Finally.. phew !</p> - </body> -</html> Added: jbpm4/branches/tbaeyens/qa/build.xml =================================================================== --- jbpm4/branches/tbaeyens/qa/build.xml (rev 0) +++ jbpm4/branches/tbaeyens/qa/build.xml 2009-04-24 13:38:29 UTC (rev 4613) @@ -0,0 +1,32 @@ +<?xml version="1.0" encoding="UTF-8"?> + +<project name="jbpm.install"> + + <!-- this allows for developer-specific configurations --> + <property file="${user.home}/.jbpm4/build.properties" /> + + <!-- the default values here should reflect the qa environment --> + <property name="maven.repository" value="file:///c:/Documents and Settings/tom/.m2/repository" /> + <property name="jbpm.version" value="4.0.0-SNAPSHOT" /> + <property name="jbpm.filename" value="jbpm-distro-${jbpm.version}.zip" /> + <property name="jbpm.distro.url" value="${maven.repository}/org/jbpm/jbpm4/jbpm-distro/${jbpm.version}/${jbpm.filename}" /> + <property name="tmp.dir" value="c:/temp/jbpmqa" /> + <property name="jbpm.home" value="c:/software/jbpm-${jbpm.version}" /> + + <target name="check.jbpm.home" unless="jbpm.home"> + <fail message="specify jbpm.home like this: ant -Djbpm.home=... targetname" /> + </target> + + <target name="delete.jbpm.installation" depends="check.jbpm.home"> + <delete dir="${jbpm.home}" /> + </target> + + <target name="install.jbpm" depends="check.jbpm.home"> + <mkdir dir="${tmp.dir}" /> + <get src="${jbpm.distro.url}" dest="${tmp.dir}/${jbpm.filename}" /> + <unzip src="${tmp.dir}/${jbpm.filename}" dest="${jbpm.home}/.." /> + </target> + + <target name="reinstall.jbpm" depends="delete.jbpm.installation, install.jbpm" /> + +</project> Property changes on: jbpm4/branches/tbaeyens/qa/build.xml ___________________________________________________________________ Name: svn:mime-type + text/plain