Changes between Version 2 and Version 3 of Obsolete/Download/SCDB/Upgrade

Timestamp:

Oct 3, 2008, 2:30:21 PM (17 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Obsolete/Download/SCDB/Upgrade

@@ -14 +14 @@
 SCDB tools is a set of utilities, underlying products and ant tasks used to manage SCDB and produce/maintain some templates. They are all maintained separately from the QWG templates and their source is in [source:SCDB SCDB branch] of QWG repository. There are 3 separate branches related to SCDB tools:
 
- * [source:SDBD/trunk trunk]: where the new contributions go first. You should not expect this to be stable or ready for production at each revision and this is not recommended to use it in production.
+ * [source:SCBD/trunk trunk]: where the new contributions go first. You should not expect this to be stable or ready for production at each revision and this is not recommended to use it in production.
  * [source:SCDB/branches branches]: there is one branch for each major version of SCDB. Current version is [source:SCDB/branches/v2 v2]. Material in this branch is sort of beta releases: not everything has been thoroughly tested but it is supposed to work.
- * [source:SCDB/tags tags]: there is one branch for each released version of SCDB. Look at release notes for new version announcements and numbers. This is the production-ready released. One of them is flagged as [source:SCDB/tags/pro pro] and is the current recommended production version.
+ * [source:SCDB/tags tags]: there is one branch for each released version of SCDB. Look at [wiki:ReleaseNotes/SCDB release notes] for new version announcements and numbers. This is the production-ready released. One of them is flagged as [source:SCDB/tags/pro pro] and is the current recommended production version.
 
-To update from one SCDB version to another, the easiest is to check out the SCDB version you want with a SVN client and then copy to your production SCDB the contents of all directory from the reference version. You can use directory-sync to help with this operation. As SCDB tools are part of SCDB, changes made can be reviewed and/or reverted with usual SVN commands.
+To update from one SCDB version to another, the easiest is to check out the SCDB version you want with a SVN client and then copy to your production SCDB the contents of all directory from the reference version. You can use [wiki:Development/Templates/RepUpdate#MergingchangefromaproductionSCDB directory-sync] to help with this operation. As SCDB tools are part of SCDB, changes made can be reviewed and/or reverted with usual SVN commands.
 
-
+For the [source:SCDB/trunk/external external] directory in SCDB tools, which contains all external tools used by SCDB, you can use a ''SVN external reference'' rather than having them directly inside your production SCDB. Look at how this is configured in [source:SCDB/trunk/external SCDB distribution] for an example. This has the advantage of smoother and easier upgrade of this part of SCDB tools at the cost of requiring a working connection with QWG repository to be able to deploy a configuration change.
 
 === Updating with Eclipse ===
 
+In fact, there is not much to say about this. All SCDB tools are contained inside SCDB. Whether you are using Eclipse or not is not relevant but this is probably easier to update SCDB tools with command line tools on a Unix system than with a GUI. The basic operation is the same: check out the new version, copy the files it provides to your production SCDB.
+
+If SCDB tools has been update from outside Eclipse, getting the new tools under Eclipse is just the matter of a "SVN update'. Depending on your Eclipse Java VM configuration, you may have to restart Eclipse to successfully update `panc` and use the new version (if you use the same Java VM for Eclipse and SCDB, which is generally recommended).
 
 == Updating AII ==