Rifidi App Upgrade Guide - Revision history

Matt: Protected "Rifidi App Upgrade Guide" [edit=sysop:move=sysop] [cascading]

2012-02-27T23:30:30Z

Protected "Rifidi App Upgrade Guide" [edit=sysop:move=sysop] [cascading]

Matt at 20:20, 18 January 2012

2012-01-18T20:20:27Z

Matt at 16:47, 6 January 2012

2012-01-06T16:47:54Z

Matt at 16:47, 6 January 2012

2012-01-06T16:47:31Z

Matt at 16:47, 6 January 2012

2012-01-06T16:47:01Z

Matt: New page: =Coming Soon!= This page will show you how to upgrade your Rifidi 1.2 applications for use with Rifidi 1.3.

2011-12-13T19:45:38Z

New page: =Coming Soon!= This page will show you how to upgrade your Rifidi 1.2 applications for use with Rifidi 1.3.

New page

=Coming Soon!=

This page will show you how to upgrade your Rifidi 1.2 applications for use with Rifidi 1.3.

← Older revision		Revision as of 20:20, 18 January 2012
Line 6:		Line 6:
	* 4. Other packages may have changed as well, and third party library versions may have updated. Check that everything is the correct version.		* 4. Other packages may have changed as well, and third party library versions may have updated. Check that everything is the correct version.
	* 5. You can export and deploy in the usual way.		* 5. You can export and deploy in the usual way.
		+
		+	Be sure to check the javadocs here:
		+	[http://www.rifidi.org/javadoc/edge1.3.0/ 1.3 Javadocs]

← Older revision		Revision as of 16:47, 6 January 2012
Line 1:		Line 1:
−	~~=Rifidi App Upgrade=~~
−
	Some work will need to be done to switch your RifidiApp from 1.2 to 1.3.		Some work will need to be done to switch your RifidiApp from 1.2 to 1.3.

@@ Line 3: / Line 3: @@
 Some work will need to be done to switch your RifidiApp from 1.2 to 1.3.
-. Get the new SDK and create a new workspace with your application and the SDK.
+* 1. Get the new SDK and create a new workspace with your application and the SDK.
-. After setting the target platform, look for any core rifidi packages that have been altered.  For instance, "org.rifidi.edge.core"  has changed to "org.rifidi.edge".  This must be changed in the manifest, the POJOs, and (if applicable) any spring files.  Esper has also changed, from version 3.4 to version 4.2; this must also be changed in the manifest.  POJOs can be switched over (after the manifest) by highlighting all the files and calling "organize imports" on them.
+* 2. After setting the target platform, look for any core rifidi packages that have been altered.  For instance, "org.rifidi.edge.core"  has changed to "org.rifidi.edge".  This must be changed in the manifest, the POJOs, and (if applicable) any spring files.  Esper has also changed, from version 3.4 to version 4.2; this must also be changed in the manifest.  POJOs can be switched over (after the manifest) by highlighting all the files and calling "organize imports" on them.
-. Spring has been changed from version 2.5.6 to 3.0.5.  You'll need to adjust any imported packages in your manifest, as well as changing the header of any spring XML files you might have.
+* 3. Spring has been changed from version 2.5.6 to 3.0.5.  You'll need to adjust any imported packages in your manifest, as well as changing the header of any spring XML files you might have.
-. Other packages may have changed as well, and third party library versions may have updated.  Check that everything is the correct version.
+* 4. Other packages may have changed as well, and third party library versions may have updated.  Check that everything is the correct version.
-. You can export and deploy in the usual way.
+* 5. You can export and deploy in the usual way.

← Older revision		Revision as of 16:47, 6 January 2012
Line 1:		Line 1:
−	=~~Coming Soon!~~=	+	=Rifidi App Upgrade=

−	~~This page~~ will ~~show you how~~ to ~~upgrade~~ your ~~Rifidi~~ 1.2 ~~applications for use with Rifidi~~ 1.3.	+	Some work will need to be done to switch your RifidiApp from 1.2 to 1.3.
		+
		+	1. Get the new SDK and create a new workspace with your application and the SDK.
		+	2. After setting the target platform, look for any core rifidi packages that have been altered. For instance, "org.rifidi.edge.core" has changed to "org.rifidi.edge". This must be changed in the manifest, the POJOs, and (if applicable) any spring files. Esper has also changed, from version 3.4 to version 4.2; this must also be changed in the manifest. POJOs can be switched over (after the manifest) by highlighting all the files and calling "organize imports" on them.
		+	3. Spring has been changed from version 2.5.6 to 3.0.5. You'll need to adjust any imported packages in your manifest, as well as changing the header of any spring XML files you might have.
		+	4. Other packages may have changed as well, and third party library versions may have updated. Check that everything is the correct version.
		+	5. You can export and deploy in the usual way.

← Older revision	Revision as of 23:30, 27 February 2012
(No difference)