[jbpm-commits] JBoss JBPM SVN: r5508 - in projects/instance-migration/trunk/jbpm-instance-migrator: src/site/apt and 1 other directory.

do-not-reply at jboss.org do-not-reply at jboss.org
Sun Aug 23 16:17:23 EDT 2009


Author: caleb.powell
Date: 2009-08-23 16:17:23 -0400 (Sun, 23 Aug 2009)
New Revision: 5508

Modified:
   projects/instance-migration/trunk/jbpm-instance-migrator/
   projects/instance-migration/trunk/jbpm-instance-migrator/pom.xml
   projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/cookbook.apt
   projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/index.apt
Log:
CP: Initial import. Some minor modificaitons to the pom.xml file.


Property changes on: projects/instance-migration/trunk/jbpm-instance-migrator
___________________________________________________________________
Name: svn:ignore
   - target

   + target
.classpath
.settings


Modified: projects/instance-migration/trunk/jbpm-instance-migrator/pom.xml
===================================================================
--- projects/instance-migration/trunk/jbpm-instance-migrator/pom.xml	2009-08-23 10:03:47 UTC (rev 5507)
+++ projects/instance-migration/trunk/jbpm-instance-migrator/pom.xml	2009-08-23 20:17:23 UTC (rev 5508)
@@ -4,13 +4,13 @@
   <groupId>jbpm</groupId>
   <artifactId>jbpm-instance-migration</artifactId>
   <name>jBPM Instance Migrator</name>
-  <version>1.2-SNAPSHOT</version>
+  <version>0.1-SNAPSHOT</version>
   <description />
   
   <scm>
-	<connection>scm:cvs:pserver:cvs:cvs at shroma:/data/cvsroot:jpbm-migrator</connection>
-	<developerConnection>scm:cvs:pserver:cvs:cvs at shroma:/data/cvsroot:jbpm-migrator</developerConnection>
-	<url>scm:cvs:pserver:cvs:cvs at shroma:/data/cvsroot:jpbm-migrator</url>
+	<connection>scm:svn:https://svn.jboss.org/repos/jbpm/projects/instance-migration</connection>
+	<developerConnection>scm:svn:https://svn.jboss.org/repos/jbpm/projects/instance-migration</developerConnection>
+	<url>scm:svn:https://svn.jboss.org/repos/jbpm/projects/instance-migration</url>
   </scm>
   
   <build>
@@ -31,19 +31,14 @@
 		        <artifactId>maven-release-plugin</artifactId>
 		        <version>2.0-beta-8</version>
 		        <configuration>
-		          <tagBase>scm:cvs:pserver:cvs:cvs at shroma:/data/cvsroot:${project.artifactId}</tagBase>
+		          <tagBase>scm:svn:https://svn.jboss.org/repos/jbpm/projects/instance-migration/trunk:${project.artifactId}</tagBase>
 		        </configuration>
 		      </plugin>
 		   </plugins>
 	  </pluginManagement>
   </build>
 
-  <!-- 
   <distributionManagement>
-        <site>
-        	<id>intranet.intelliware.ca</id>
-        	<url>dav:http://intranet/internal/intelliware/hwng-projects/jbpm-migrator</url>
-        </site>
 		<repository>
 			<id>intelliwareReleases</id>
 			<name>Intelliware Releases</name>
@@ -56,7 +51,6 @@
             <uniqueVersion>false</uniqueVersion>
 		</snapshotRepository>
   </distributionManagement>    
-   -->
    	
   <dependencies>
 	<dependency>

Modified: projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/cookbook.apt
===================================================================
--- projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/cookbook.apt	2009-08-23 10:03:47 UTC (rev 5507)
+++ projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/cookbook.apt	2009-08-23 20:17:23 UTC (rev 5508)
@@ -13,9 +13,9 @@
 	For projects that require long-lived processes, this option is not as appealing. For example, new process definitions may contain graph changes 
 	that resolve a bug, or new requirements. Alternatively, old process definitions may reference deprecated or non-existent Actions. The risks 
 	become more pronounced the older the process instance is. In light of these risks, the ability to migrate older process instances is very 
-	desirable. The jbpm-migrator project was created to address this.
+	desirable. The jbpm-instance-migrator project was created to address this.
 	
-	Given an old process instance (that is, a process instance whose process definition is not the current version), the jbpm-migrator is capable of 
+	Given an old process instance (that is, a process instance whose process definition is not the current version), the jbpm-instance-migrator is capable of 
 	migrating the process instance to the latest process instance. A migration performs the following actions:
 
 		[[1]] Checks to determine whether the ProcessInstance actual requires migration. If the process instance refers to the current Process definition, it will not perform a migration and will exit and return the current process instance (the one passed into the migrate method).

Modified: projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/index.apt
===================================================================
--- projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/index.apt	2009-08-23 10:03:47 UTC (rev 5507)
+++ projects/instance-migration/trunk/jbpm-instance-migrator/src/site/apt/index.apt	2009-08-23 20:17:23 UTC (rev 5508)
@@ -1,7 +1,7 @@
 ~~see http://maven.apache.org/doxia/format.html for info on the APT format
 Jbpm-Migrator
  
-  The jbpm-migrator project is used to migrate jbpm process instances dynamically at runtime. 
+  The jbpm-instance-migrator project is used to migrate jbpm process instances dynamically at runtime. 
   
   	* {{{cookbook.html}Cookbook}}
  



More information about the jbpm-commits mailing list