Loading...
Helix SwarmHelix Swarm
Loading...

p4convert-svn.html

  • //
  • guest/
  • alan_petersen/
  • p4convert/
  • p4convert-svn.html #1
  • View
  • Commits
  • Open Download .zip Download (49 KB) 
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  2. <html xmlns="http://www.w3.org/1999/xhtml">
  3.   <head>
  4.     <meta http-equiv="content-type" content="application/xhtml+xml; charset=ISO-8859-1" />
  5.     <meta name="GENERATOR" content="Quanta Plus" />
  6.     <title>How to use p4convert-svn</title>
  7.     <style type="text/css" media="screen">
  8.     /* Space out the list entries a little for clarity */
  9.     li  {
  10.         padding-bottom:    10pt;
  11.     }
  12.  
  13.     h1,h2,h3,h4,h5,h6 {
  14.          font-family:   Arial, Helvetica, sans-serif;
  15.          font-weight:  bold;
  16.          color:            #333377;
  17.     }
  18.  
  19.     h1  {
  20.          font-size:           150%;
  21.          text-decoration:   underline;
  22.          text-align:            center;
  23.     }
  24.  
  25.     h2 {
  26.         font-size:          130%;
  27.         border-top:      1px solid;
  28. 		padding-top:		1em;
  29.     }
  30.  
  31.     h3 {
  32.         font-size;          115%;
  33.         font-style:         italic;
  34.     }
  35.     pre {
  36.         font-size:          90%;
  37.         border:             1px solid;
  38.         background-color:   #EEEEEE;
  39.         padding-top:    10px;
  40.     }
  41.  
  42.     #vital {
  43.         color:      red;
  44.     }
  45.  
  46.     table {
  47.         border:     1px solid;
  48.         background-color:   #EEEEEE;
  49.     }
  50.  
  51.     div.copyright {
  52. 	border-top: 1px solid;
  53. 	font-size:	small;
  54.     }
  55.  
  56.     div.ident {
  57. 	font-size:	small;
  58.     }
  59.     div.section {
  60.          width: 1000px;
  61.     }
  62.     ul.biglist {
  63.          list-style-type: none;
  64.     }
  65.     pre {
  66.           margin: 3;
  67.     }
  68.     
  69.   </style>
  70.   </head>
  71.   <body>
  72.     <h1>Users Guide to p4convert-svn</h1>
  73.     <h2>Contents</h2>
  74.     <div class="contents">
  75.       <ol>
  76.         <li><a href="#section1">Version Information</a></li>
  77.         <li><a href="#section2">What is p4convert-svn for ?</a></li>
  78.         <li><a href="#section3">Terms and Conditions</a></li>
  79.         <li><a href="#section4">System Requirements</a></li>
  80.         <li><a href="#section5">Caveats</a></li>
  81.         <li><a href="#section6">Setup and Usage</a></li>
  82.         <li><a href="#section7">Generating a Subversion Dump file</a></li>
  83.         <li><a href="#section8">General Configuration</a></li>
  84.         <li><a href="#section9">Selective and Incremental Conversion</a></li>
  85.         <li><a href="#section9.1">Filtering Subversion paths</a></li>
  86.         <li><a href="#section10">Changelist offset options</a></li>
  87.         <li><a href="#section11">Unicode Support</a></li>
  88.         <li><a href="#section12">Advanced Configuration</a></li>
  89.         <li><a href="#section13">Running 'Import Mode'</a></li>
  90.         <li><a href="#section14">Running 'Conversion Mode'</a></li>
  91.         <li><a href="#section15">Post Conversion</a></li>
  92.         <li><a href="#section17">Notes</a></li>
  93.         <li><a href="#section18">Verification</a></li>
  94.         <li><a href="#section19">Output and Logs</a></li>
  95.         <li><a href="#section20">Errors</a></li>
  96.       </ol>
  97.     </div>
  98.     <div class="section"> <a name="section1"></a>
  99.       <h2>Version Information</h2>
  100.       <p> This documentation covers p4convert-svn version 2013.1. </p>
  101.     </div>
  102.     <div class="section"> <a name="section2"></a>
  103.       <h2>What is p4convert-svn for?</h2>
  104.       The p4convert-svn conversion tool imports data from Subversion and
  105.       reconstructs the file revision history in Perforce. The Subversion data is
  106.       read from a dump file and can be imported in one of two ways:
  107.       <blockquote>
  108.         <h4>Import Mode (front door)</h4>
  109.         <p> Subversion revisions are imported into a running Perforce Server.
  110.           The Perforce Server could be new or contain existing data, but it must
  111.           be running. Subversion revisions are added sequentially; file content
  112.           is 'imported' and metadata such as file attributes, descriptions,
  113.           dates and usernames are added to the Perforce changelist.</p>
  114.         <p> The recommended use of 'Import Mode' is to start a new Perforce
  115.           server to import each Subversion revision into a Perforce changelist.
  116.           Using this method will produce a one-to-one mapping of Subversion
  117.           revision numbers to Perforce changelists. The new Perforce server can
  118.           be used in isolation to confirm the success of the migration and then
  119.           merged with an existing Perforce Server using the 'perfmerge++' tool.</p>
  120.         <h4>Convert Mode (back door)</h4>
  121.         <p> SVN revisions are converted in full, creating a Perforce journal and
  122.           set of archive files. Once replayed the resulting conversion is just
  123.           as if the changes had always been in Perforce. The results can be
  124.           merged into an existing Perforce Server using 'perfmerge++'. The
  125.           Import mode is considered to be the safest method as all files are
  126.           imported through a Perforce Client. However, the Convert mode is
  127.           significantly faster and requires less user interaction.</p>
  128.         <p>Convert mode is an advanced feature and should only be attempted by a
  129.           Perforce expert familiar with replaying and upgrading databases.
  130.           Incremental conversions are not supported using Convert mode; however
  131.           the slower Import mode can be used after the a conversion to update
  132.           the migration. </p>
  133.         <h4>Incremental Updates (front door)<br />
  134.         </h4>
  135.         <p> Incremental updates are possible only using the Import mode where
  136.           new revision from Subversion are imported into Perforce. However, no
  137.           changes should be made to the import area of the Perforce Server or
  138.           conflicts may occur.<br />
  139.         </p>
  140.       </blockquote>
  141.     </div>
  142.     <div class="section"> <a name="section3"></a>
  143.       <h2>Terms and Conditions</h2>
  144.       <p> p4convert-svn is supplied by Perforce Software in the hope that it
  145.         will be useful. It is a support utility, not a Perforce product. All use
  146.         of this software is at the user's own risk and subject to the following
  147.         terms and conditions. </p>
  148.       <pre>  	THIS SOFTWARE IS PROVIDED BY PERFORCE SOFTWARE, INC. 'AS IS' AND ANY
  149.  	EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
  150.   	WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
  151.   	DISCLAIMED. IN NO EVENT SHALL PERFORCE SOFTWARE, INC. BE LIABLE FOR ANY
  152.   	DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
  153.   	(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  154.   	LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
  155.   	ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  156.   	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
  157.   	THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  158.  
  159. </pre> </div>
  160.     <div class="section"> <a name="section4"></a>
  161.       <h2>System Requirements</h2>
  162.       <ol>
  163.         <li>An unzipped Subversion dump file of the repository to be converted
  164.           (generated without the --delta flag).</li>
  165.         <li>System must have <span style="font-weight: bold;">Java SE Runtime
  166.             1.7.</span><br />
  167.         </li>
  168.         <li>System must have the Perforce Server binaries 2010.2 or greater.<br />
  169.         </li>
  170.         <li> [Import mode] A running Perforce Server (typically empty) with no
  171.           pending changes in the conversion area. <br />
  172.         </li>
  173.         <li>[Convert mode] An empty Perforce Root directory for the generated
  174.           archive and journal files. </li>
  175.       </ol>
  176.       <blockquote>
  177.         <h4>Resource Tips:</h4>
  178.       </blockquote>
  179.       <blockquote>Running some conversions, particularly in Conversion Mode can
  180.         be very memory intensive, as we keep a mapping of revisions and
  181.         integrations in memory. For large conversions or conversions with
  182.         excessive branching, more memory will needed by the JVM.<br />
  183.         <br />
  184.         The <code>--info </code>option will scan the Subversion dump file and
  185.         report usage data to help estimate the required memory for Convert
  186.         Mode. For example:<br />
  187.         <pre>java -jar p4convert-svn.jar --info &lt;path_to_svn_dumpfile&gt;</pre>
  188.         <br />
  189.         Use the <code><i>-Xmx</i></code> flags to increase the memory allocated
  190.         to the JVM. For example, to allocate 64GB (65536MB) use:
  191.         <pre><code>java -Xmx65536M -jar p4convert-svn.jar myConfig.cfg<br /></code></pre>
  192.       </blockquote>
  193.       <ol>
  194.       </ol>
  195.     </div>
  196.     <div class="section"> <a name="section5"></a>
  197.       <h2>Caveats</h2>
  198.       <ol>
  199.         <li>The following table lists the combinations of tested operating
  200.           systems and Perforce Server versions.</li>
  201.         <ul>
  202.           <li>
  203.             <table width="430" height="130" border="1">
  204.               <tbody>
  205.                 <tr>
  206.                   <td><b>Operating System</b><br />
  207.                   </td>
  208.                   <td align="center"><b>10.2<br />
  209.                     </b></td>
  210.                   <td align="center"><b>13.1<br />
  211.                     </b></td>
  212.                 </tr>
  213.                 <tr>
  214.                   <td>Ubuntu 10.04.4<br />
  215.                   </td>
  216.                   <td align="center">supported<br />
  217.                   </td>
  218.                   <td align="center">supported</td>
  219.                 </tr>
  220.                 <tr>
  221.                   <td>Darwin 11.4.0<br />
  222.                   </td>
  223.                   <td align="center">supported</td>
  224.                   <td align="center">supported</td>
  225.                 </tr>
  226.                 <tr>
  227.                   <td>Windows 7x64<br />
  228.                   </td>
  229.                   <td align="center">supported</td>
  230.                   <td align="center">supported</td>
  231.                 </tr>
  232.                 <tr>
  233.                   <td>SunOS 5.10<br />
  234.                   </td>
  235.                   <td align="center">supported</td>
  236.                   <td align="center">supported</td>
  237.                 </tr>
  238.               </tbody>
  239.             </table>
  240.           </li>
  241.           <li>It is likely that other combinations will work, however it is not
  242.             possible to test all combinations. <br />
  243.           </li>
  244.           <li>Please contact Perforce if you have any OS or version queries. <br />
  245.           </li>
  246.         </ul>
  247.         <li>[Import mode] Symbolic links are not supported in Import mode on
  248.           Windows 7x64.</li>
  249.         <li>Perforce keyword expansions are different from the Subversion
  250.           standard and may yield different results when synced.</li>
  251.       </ol>
  252.     </div>
  253.     <div class="section"> <a name="section6"></a>
  254.       <h2>Setup and Usage</h2>
  255.       <p> Download the self-contained JAR from Perforce and check that Java SE
  256.         runtime is installed with version 1.7 or greater. </p>
  257.       For usage details, execute the jar with no options (this will generate a
  258.       default configuration file):<br />
  259.       <pre>java -jar p4convert-svn.jar<br /><br />WARNING: No configuration file specified...
  260.  
  261. Usage:
  262. 	java -jar p4convert-svn.jar &lt;config file&gt;
  263.  
  264. 	java -jar p4convert-svn.jar --version
  265. 	java -jar p4convert-svn.jar --info &lt;dump file&gt;
  266. 	java -jar p4convert-svn.jar --users &lt;dump file&gt;
  267. 	java -jar p4convert-svn.jar --extract rev.node &lt;dump file&gt;
  268.  
  269. Generating default config file 'default.cfg'...</pre>
  270.       <br />
  271.       Create a configuration file based on the generated default configuration,
  272.       then start the conversion by executing the jar with the configuration
  273.       file. For example:<br />
  274.       <pre>java -jar p4convert-svn.jar config.txt</pre>
  275.     </div>
  276.     <div class="section"> <a name="section7"></a>
  277.       <h2>Generating a Subversion Dump file</h2>
  278.       <p> Both the Import and Convert modes require a Subversion dumpfile as the
  279.         history data source. A dumpfile can be generated in several different
  280.         ways; two of which are detailed below: </p>
  281.       <dl>
  282.         <dt>Using the svnadmin command:</dt>
  283.         <dd>
  284.           <pre><code>svnadmin dump <var>local_repo_path </var> &gt; dumpfile.dmp</code></pre>
  285.         </dd>
  286.         <dd>
  287.           <p> Replace <var>local_repo_path</var> with the path to the
  288.             Subversion repo. Do not use the <code>'--delta'</code> flag option
  289.             as the results cannot be parsed by the conversion tool.</p>
  290.         </dd>
  291.         <dt>Using the remote dump command:</dt>
  292.         <dd>
  293.           <pre><code>rsvndump url &gt; dumpfile.dmp</code></pre>
  294.         </dd>
  295.         <dd>
  296.           <p> Replacing <code>url</code> with the remote Subversion server. For
  297.             example: <code>http://</code> or <code>file:///</code> or <code>svn://</code>.
  298.             Note that for large servers generating the dump file locally is
  299.             significantly faster, you might also consider creating a local copy
  300.             of the subversion depot using <a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt">svnsync</a>,
  301.             before generating the dump file.</p>
  302.         </dd>
  303.       </dl>
  304.     </div>
  305.     <div class="section"> <a name="section8"></a>
  306.       <h2>General Configuration</h2>
  307.       The java conversion requires a configuration file to setup the necessary
  308.       options. A default configuration file "default.cfg" can be generated by
  309.       running the converter without a parameter.
  310.       <pre>java -jar p4convert-svn.jar<br /><br />WARNING: No configuration file specified...
  311.  
  312. Usage:
  313. 	java -jar p4convert-svn.jar &lt;config file&gt;
  314.  
  315. 	java -jar p4convert-svn.jar --version
  316. 	java -jar p4convert-svn.jar --info &lt;dump file&gt;
  317. 	java -jar p4convert-svn.jar --users &lt;dump file&gt;
  318. 	java -jar p4convert-svn.jar --extract rev.node &lt;dump file&gt;
  319.  
  320. Generating default config file 'default.cfg'...
  321. </pre> Once you have "<code>default.cfg</code>" copy it to "<code>yourconfig.cfg</code>"
  322.       and then customize it as needed for the conversion.
  323.       <h3>General configuration options common to both conversion modes.</h3>
  324.       <ol>
  325.         <li>Local path to Subversion dump file.
  326.           <pre><code>com.p4convert.svn.dumpFile=/Users/pallen/MyDumpFile.dmp</code></pre>
  327.         </li>
  328.         <li>Conversion mode '<code>true</code>' for Import mode and '<code>false</code>'
  329.           for Conversion mode
  330.           <pre><code>com.p4convert.svn.mode=true</code></pre>
  331.         </li>
  332.         <li>Import depot path and depot to be created, e.g. <code>//import/...
  333.           </code>
  334.           <pre><code>com.p4convert.core.depotPath=import</code></pre>
  335.         </li>
  336.         <li>An optional sub path can be specified below the depot, e.g. <code>//import/sub/...</code>
  337.           (Note that the path must end with a '/' even if no path is used)
  338.           <pre><code>com.p4convert.core.subPath=sub/
  339.     (Default: com.p4convert.core.subPath=/)</code></pre>
  340.         </li>
  341.       </ol>
  342.     </div>
  343.     <div class="section"> <a name="section9"></a>
  344.       <h2>Selective and Incremental Conversions</h2>
  345.       <ol>
  346.         <li> The subversion revision ranges can be limited using the
  347.           configuration options '<code>startRevision</code>' and '<code>endRevision</code>'.
  348.           The default is to start at revision 1 and import all revisions,
  349.           defined by setting '<code>endRevision</code>' to 0.
  350.           <pre><code>  com.p4convert.svn.start=1
  351.   com.p4convert.svn.end=0
  352.  </code></pre>
  353.         </li>
  354.         <li> Incremental conversions are possible using the <b>'</b>Import
  355.           Mode'. It is important to take note of the last imported Subversion
  356.           revision and start from the next revision for the subsequent import.
  357.           For example: to import the first 100 subversion revisions, set the
  358.           config options to:
  359.           <pre><code>  com.p4convert.svn.start=1
  360.   com.p4convert.svn.end=100
  361. </code></pre> </li>
  362.         <li> At the start of the import the following summary is displayed: (In
  363.           this example only the first 100 revisions are imported out of 23000.)
  364.           <pre><code>  Importing Subversion ranges:
  365.   start: 1
  366.   end:   100
  367.   last:  23000
  368. </code></pre> </li>
  369.         <li> For the next incremental import (say another 100 revisions) set the
  370.           revision ranges to...
  371.           <pre><code>  com.p4convert.svn.start=101
  372.   com.p4convert.svn.end=200
  373. </code></pre> </li>
  374.       </ol>
  375.     </div>
  376.     <div class="section"> <a name="section9.1"></a>
  377.       <h2>Filtering Subversion paths</h2>
  378.       The default behavior is not to exclude any path in Subversion; however for
  379.       large repositories with many 'tags/' folders or situations where only part
  380.       of a Subversion repository is to be converted you may wish to exclude
  381.       certain Subversion paths. Subversion path exclusion is possible using two
  382.       map files 'exclude.map' and 'include.map'.<br />
  383.       <br />
  384.       The filtering is based on matching the Subversion path to a regular
  385.       expression in the map files. The 'exclude.map' file is processed first
  386.       and if the pattern matches part of the path then that path is skipped.
  387.       The 'include.map' file can be used to overlay the 'exclude.map' file
  388.       re-adding paths that were skipped. Before a conversion can start the
  389.       filters must be verified against the Dump file (typically this is fairly
  390.       quick and a displays a progress indicator). <br />
  391.       <br />
  392.       The verification step is to prevent the situation where an excluded path
  393.       is relied on at a later point in the history for a branch, copy or merge
  394.       action. If such a situation is found the paths are logged and the
  395.       excluded 'source path' is added to the 'issue.map' file. To resolve the
  396.       issue the exclusion should be removed from the 'exclude.map' file or a
  397.       regular expression, based on the 'issue.map' file, added to the
  398.       'include.map' file.<br />
  399.       <br />
  400.       For example; to exclude all Subversion tags in the folder 'tags/', create
  401.       an exclusion map file 'exclude.map':<br />
  402.       <pre># exclude Subversion tags:<br />^tags/.*</pre>
  403.       Then start the conversion to verify the map:<br />
  404.       <pre>pallen-mac:main$ java -jar dist/p4convert-svn.jar Config/foo.cfg 
  405. loading ChangeMap: 	changeMap.txt
  406. loading TypeMap: 	types.map
  407. importing revisions: 	1 to 20635 out of 20635
  408. exclude.map: ^tags/.*
  409. Verifying exclusion map...
  410. issue: tags/rel-1.0.14/api
  411. issue: tags/rel-1.0.14/sys
  412. issue: tags/rel-2.0.3<br />Issues found, saving issue map...
  413. Caught EXIT shutting down ...</pre>
  414.       Looking at the reported issues the tags 'rel-1.0.14' and 'rel-2.0.3' have
  415.       some actions that conflict with our exclusion, to resolve this simply add
  416.       the exclusions to the 'include.map' file:<br />
  417.       <pre># issues reported for tags/ folder<br />^tags/rel-1.0.14/.*<br />^tags/rel-2.0.3/.*<br /></pre>
  418.       <ol>
  419.       </ol>
  420.     </div>
  421.     <div class="section"> <a name="section10"></a>
  422.       <h2>Changelist Offset options</h2>
  423.       <ol>
  424.         <li> The default offset is 0 (i.e. not offsetting). Offset is currently
  425.           available for 'Convert Mode' and allows subversion revisions to be
  426.           converted into Perforce changelists by a fixed offset:
  427.           <pre><code>com.p4convert.adv.offset=0</code></pre>
  428.         </li>
  429.         <li> After the conversion a 'changeMap' file is appended locally
  430.           containing a Subversion revision number to Perforce change-list
  431.           mapping. The file name is configured by the option:
  432.           <pre><code>com.p4convert.log.changeMap=changeMap.txt</code></pre>
  433.           A changemap looks like this:
  434.           <pre><code>
  435. # &lt;Change&gt;, &lt;SVN revision&gt;	
  436. 1, 1
  437. 2, 2
  438. 3, 3
  439. ...
  440. </code></pre> </li>
  441.       </ol>
  442.     </div>
  443.     <div class="section"> <a name="section11"></a>
  444.       <h2>Unicode Support</h2>
  445.       <blockquote> The following Unicode enable options apply to Unicode support
  446.         for 'Import Mode' and 'Convert Mode'. The Charset options are only
  447.         applicable to 'Import Mode', when translating a file through the
  448.         Perforce client. In 'Convert Mode' archive files are always written in
  449.         UTF-8 for a Unicode enabled Perforce server. <br />
  450.         <br />
  451.         Defaults (for non-Unicode servers):
  452.         <pre><code>com.p4convert.p4.unicode=false
  453. com.p4convert.p4.charset=&lt;none&gt;
  454. </code></pre> A UTF8 client example: (for a full list see 'p4 help charset')
  455.         <pre><code>com.p4convert.p4.unicode=true
  456. com.p4convert.p4.charset=utf8
  457. </code></pre> For Unicode conversions set the JVM arg:
  458.         <pre><code>-Dfile.encoding=UTF-8</code></pre>
  459.         Some Solaris and Linux conversions may need the locale set:
  460.         <pre><code>export LC_ALL=en_GB.UTF-8 
  461. </code></pre> Once a Perforce server is switched to Unicode enabled mode (<code>-xi</code>),
  462.         all client workspaces need to define a character set. (For details see:
  463.         <a href="http://kb.perforce.com/article/524">http://kb.perforce.com/article/524</a>).
  464.         Note: A non-Unicode enabled Perforce Server will accept UTF16 files. </blockquote>
  465.       <blockquote>
  466.         <h4>Normalisation</h4>
  467.       </blockquote>
  468.       <blockquote>Platform Unicode normalisation is detected when the
  469.         configuration file is generated, however it can be changed by setting
  470.         the following configuration option to '<code>NFC</code>' or '<code>NFD</code>':<br />
  471.         <pre><code>com.p4convert.svn.normalisation=NFD</code></pre>
  472.         The default detection is based on the following:<br />
  473.         <table width="380" height="130" border="1">
  474.           <tbody>
  475.             <tr>
  476.               <td><b>Platform<br />
  477.                 </b> </td>
  478.               <td><b>Normalisation<br />
  479.                 </b> </td>
  480.             </tr>
  481.             <tr>
  482.               <td>Windows<br />
  483.               </td>
  484.               <td>NFC<br />
  485.               </td>
  486.             </tr>
  487.             <tr>
  488.               <td>Mac<br />
  489.               </td>
  490.               <td>NFD<br />
  491.               </td>
  492.             </tr>
  493.             <tr>
  494.               <td>*nix / *nux<br />
  495.               </td>
  496.               <td>NFC<br />
  497.               </td>
  498.             </tr>
  499.             <tr>
  500.               <td>Sun<br />
  501.               </td>
  502.               <td>NFC<br />
  503.               </td>
  504.             </tr>
  505.           </tbody>
  506.         </table>
  507.         <h4> Subversion Properties</h4>
  508.         <p>By default the converter parses Subversion properties as UTF-8
  509.           strings. The conversion uses properties such as <code>svn:log</code>,
  510.           <code>svn:author</code> for attributes in Perforce and must decode the
  511.           byte sequence to UTF-8. In some data sets Windows users may have
  512.           added high ASCII characters in one or more code pages. This release
  513.           now supports a configuration option:</p>
  514.         <pre><code>com.p4convert.svn.propTextType=UNKNOWN</code></pre>
  515.         <p>The following strings denote the supported char-sets:</p>
  516.         <table width="100%" border="1">
  517.           <tbody>
  518.             <tr>
  519.               <td>UNKNOWN</td>
  520.               <td>Big5</td>
  521.               <td>Shift_JIS</td>
  522.               <td> windows-1251</td>
  523.             </tr>
  524.             <tr>
  525.               <td>US-ASCII</td>
  526.               <td>ISO-2022-JP</td>
  527.               <td>ISO-8859-1</td>
  528.               <td>windows-1254</td>
  529.             </tr>
  530.             <tr>
  531.               <td>UTF-8</td>
  532.               <td>ISO-2022-CN</td>
  533.               <td>ISO-8859-2</td>
  534.               <td>windows-1252</td>
  535.             </tr>
  536.             <tr>
  537.               <td>UTF-16BE</td>
  538.               <td>ISO-2022-KR</td>
  539.               <td> ISO-8859-5 </td>
  540.               <td>windows-1256 </td>
  541.             </tr>
  542.             <tr>
  543.               <td>UTF-16LE</td>
  544.               <td>GB18030</td>
  545.               <td>ISO-8859-6</td>
  546.               <td>IBM424_rtl</td>
  547.             </tr>
  548.             <tr>
  549.               <td> UTF-32BE</td>
  550.               <td>EUC-JP</td>
  551.               <td> ISO-8859-7</td>
  552.               <td> IBM424_ltr</td>
  553.             </tr>
  554.             <tr>
  555.               <td>UTF-32LE</td>
  556.               <td>EUC-KR</td>
  557.               <td> ISO-8859-8</td>
  558.               <td>IBM420_rtl </td>
  559.             </tr>
  560.             <tr>
  561.               <td>BINARY</td>
  562.               <td>KOI8-R</td>
  563.               <td>ISO-8859-9</td>
  564.               <td> IBM420_ltr</td>
  565.             </tr>
  566.           </tbody>
  567.         </table>
  568.         <p>The first scan is always 'UTF-8' followed by the configuration
  569.           option. BINARY implies a skip and the string <code>&lt;binary
  570.             property&gt;</code> is inserted.</p>
  571.         <p><br />
  572.         </p>
  573.       </blockquote>
  574.     </div>
  575.     <div class="section">
  576.       <h2>Advanced Configuration</h2>
  577.       <blockquote>
  578.         <h4> Directory Properties </h4>
  579.         The following options allow Subversion Directory Properties to be stored
  580.         as versioned files in Perforce: <br />
  581.         To enable this mode set the following property to '<code>true</code>'
  582.         <pre><code>com.p4convert.svn.propEnabled=true</code></pre>
  583.         To select the property name and format (Note: only '<code>ini</code>'
  584.         mode is supported)
  585.         <pre><code>com.p4convert.svn.propEncoding=ini
  586. com.p4convert.svn.propName=.svn.properties</code></pre>
  587.         <h4>Empty changelists</h4>
  588.         The following property will attempt to skip empty changes (where the
  589.         change contains no revisions). This is typically the default behavior of
  590.         the client or 'Import Mode' so is only really used in 'Convert Mode'.
  591.         <pre><code>com.p4convert.adv.skipEmpty=false</code></pre>
  592.         <h4>Username translation</h4>
  593.         <p>A username map file ('<code>users.map</code>') can be generated using
  594.           the '<code>--users</code>' option and then the right-hand-side
  595.           modified with the new user name. The rename will only occur if the
  596.           conversion tool finds the <code>users.map</code> file in the current
  597.           working directory.</p>
  598.         <h4>Binary file detection</h4>
  599.         <p> </p>
  600.         <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;">Binary
  601.           files can be identified by adding their extensions to the type map
  602.           file 'types.map'. The format is based on Perforce typemap spec,
  603.           however it is limited to paths of the form '//....ext' (where .ext is
  604.           the binary extension). <br />
  605.         </p>
  606.         <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br />
  607.         </p>
  608.         <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;">Default
  609.           Type map (types.map):</p>
  610.         <pre style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;">TypeMap:
  611. 	binary	//....zip
  612. 	binary	//....gif
  613. 	binary	//....png
  614. 	binary	//....jpg
  615. 	binary  //....dll
  616. 	binary  //....class
  617. 	binary  //....jar
  618. 	binary  //....ecsfr</pre>
  619.         <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><br />
  620.         </p>
  621.         <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;">Modification
  622.           bits (+mxwlk) are supported and can be added using the type mapping.
  623.           Binary detection though the type map is recommended as conversion is
  624.           much faster. Binary files not identified in the type map will be
  625.           scanned by the ICU4J libraries and if no text/Unicode match is found
  626.           they are assumed to be binary. Warning: ICU4J may incorrectly
  627.           identify small binary files as text creating sync issues on Windows
  628.           clients.<br />
  629.         </p>
  630.         <p> </p>
  631.         <h4>Changelist Description Format</h4>
  632.         <p>The <code>logRevID</code> option can be used to reformat the
  633.           Subversion revision descriptions to include the revision ID using the
  634.           template: <br />
  635.         </p>
  636.         <ul>
  637.           <li><code>&lt;rev&gt;</code> substituted with the Subversion revision</li>
  638.           <li><code>&lt;description&gt;</code> substituted with the Subversion
  639.             log<br />
  640.           </li>
  641.         </ul>
  642.         <p>Default (as-is): <code>com.p4convert.svn.logRevID=&lt;description&gt;</code></p>
  643.         <h4>Case Sensitivity</h4>
  644.         <p>The platform case sensitivity is detected when generating the
  645.           configuration file. There is normally no reason to change this
  646.           behavior from the detected defaults. Conversions between different
  647.           platforms should be avoided especially when converting from a case
  648.           sensitive environment (such as Linux) to a case insensitive
  649.           environment (such as Windows). The advanced case handling options
  650.           supported are set using one of the following options:<br />
  651.         </p>
  652.         <pre><code>com.p4convert.adv.caseMode=FIRST</code></pre>
  653.         <ul>
  654.           <li><code>NONE</code> - treat all paths as case sensitive (Linux).</li>
  655.           <li><code>LOWER</code> - convert all paths to lower case</li>
  656.           <li><code>UPPER</code> - convert all paths to upper case</li>
  657.           <li><code>FIRST</code> - use the first encountered case combination
  658.             (Windows)</li>
  659.         </ul>
  660.         <p>When using the Convert mode the generated Perforce archive files are
  661.           based on the platforms case sensitivity. However on Linux platforms it
  662.           can be useful to store archives files as if on a case insensitive
  663.           server (<code>p4d -C1</code>). This can be simulated by setting the
  664.           following option to 'true': </p>
  665.         <pre><code>com.p4convert.adv.lowerCase=true</code></pre>
  666.         <b>Note</b>: that if this option is set the path to the Perforce root
  667.         directory, defined by <font color="#cc0000"><code>com.p4convert.adv.p4root</code></font>,
  668.         must be in <font color="#cc0000">lower case</font> and the case mode of
  669.         <font color="#cc0000"><code>FIRST</code></font> must be used.
  670.         <h4>RCS Keyword expansion (<code>svn:keywords</code>)</h4>
  671.         <p>By default RCS keyword expansion attributes are imported; however
  672.           setting the configuration option:</p>
  673.         <pre> <code>com.p4convert.svn.keepKeyword=true</code><code></code> </pre>
  674.         <p>Setting a value of <code>false</code> will ignore all previous
  675.           keyword attributes and import the files as normal text. See <a href="#keyword_notes">keyword
  676.             notes</a> for known issues.</p>
  677.         <h4>Merge Information (<code>svn:mergeinfo</code>)</h4>
  678.         <p>Supports SVN 1.5-1.7 merge information and calculates the
  679.           corresponding Perforce integration credit for the various actions.
  680.           The feature is not enabled by default and if required the following
  681.           configuration option must be set to true:</p>
  682.         <pre>com.p4convert.svn.mergeInfoEnabled=true</pre>
  683.       </blockquote>
  684.     </div>
  685.     <div class="section"> <a name="section13"></a>
  686.       <h2>Running 'Import Mode'</h2>
  687.       <ul>
  688.         <li>Import mode will pull in file revisions from a Subversion dump file
  689.           adding them to the Perforce Server specified by the connection details
  690.           in the configuration options. To use this mode set '<code>com.p4convert.svn.mode</code>'
  691.           to <code>true</code>.</li>
  692.         <li>Care should be taken when adding data to a pre-existing Perforce
  693.           Server that the revision actions do not conflict with revisions
  694.           already in the Perforce Server; typically, this can occur if the
  695.           Server has been in-use since the previous migration.</li>
  696.         <li>To avoid such scenarios the import should either be to a unique
  697.           depot, to avoid conflict, or the Perforce Server should be Read Only
  698.           during subsequent migrations. After a conversion is complete, it is
  699.           possible to merge the new data with an existing depot using tools like
  700.           PerfMerge++.</li>
  701.         <li>The converter will check that your Perforce Server has no pending
  702.           changes, and will abort a conversion if any are detected</li>
  703.       </ul>
  704.       <h3>Configuration options specific to 'Import Mode':</h3>
  705.       <ol>
  706.         <li>Perforce server address and port (escape the '<code>:</code>' with '<code>\:</code>')
  707.           <pre><code>com.p4convert.p4.port=localhost\:4444</code></pre>
  708.         </li>
  709.         <li>Default user and client for server connection
  710.           <pre><code>com.p4convert.p4.client=svn-client
  711. com.p4convert.p4.user=svn-user
  712. </code></pre> </li>
  713.         <li>Client workspace root used to import files into Perforce
  714.           <pre><code>com.p4convert.p4.clientRoot=/Users/pallen/ws/</code></pre>
  715.         </li>
  716.         <li>If Security is set to level 1 or greater then the 'svn-user' must
  717.           have 'admin' permissions in the Protection table and the password
  718.           supplied as a string (the default is no string after the '=' sign). <br />
  719.           <pre>com.p4convert.p4.passwd=PaSSwoRd</pre>
  720.         </li>
  721.         <li>Alternatively if the user is already logged in and there is a valid
  722.           ticket, then leave the password field unset and <strong>set</strong>
  723.           your environment for P4TICKETS (don't relay on the P4TICKETS unset
  724.           default as p4-java will not find your ticket file).</li>
  725.       </ol>
  726.     </div>
  727.     <div class="section"> <a name="section14"></a>
  728.       <h2>Running 'Convert Mode'</h2>
  729.       <ul>
  730.         <li>Convert mode is more advanced and requires knowledge of the Perforce
  731.           Journal replay and Archive file store.</li>
  732.         <li>This mode can only be used for single shot conversions and cannot be
  733.           used incrementally.</li>
  734.         <li>The performance of conversion mode is significantly better than
  735.           Import mode (x100 sometimes!).</li>
  736.         <li>After a using the 'Convert mode' the administrator will need to run
  737.           several commands to rebuild the Perforce server and upgrade the
  738.           metadata. Please refer to the <a href="#section15">'Post Conversion'</a>
  739.           section for step-by-step instructions.</li>
  740.         <li>To use this mode set <b>'</b><code>com.p4convert.svn.mode</code><b>'</b>
  741.           to <code>false</code>.</li>
  742.       </ul>
  743.       <h3>Configuration options specific to 'Conversion Mode':</h3>
  744.       <ol>
  745.         <li>Perforce server root address (path should end with a '<code>/</code>')<br />
  746.           <pre><code>com.p4convert.adv.p4root=/full/path/to/p4_root/</code></pre>
  747.         </li>
  748.         <li>Change list offset (handy for batched conversions)
  749.           <pre><code>com.p4convert.adv.offset=0</code></pre>
  750.         </li>
  751.         <li>Generated journal names (useful to increment the prefix when running
  752.           batched conversions)
  753.           <pre><code>com.p4convert.adv.jnlIndex=0
  754. com.p4convert.adv.jnlPrefix=jnl.</code></pre>
  755.         </li>
  756.         <li>Mimic the 2011.1 or greater credit behavior on rollbacks /
  757.           downgrades (to enable set value to '<code>true</code>')
  758.           <pre><code>com.p4convert.adv.downgrade=false</code></pre>
  759.         </li>
  760.         <li>Perforce normalises line-endings when storing the file on the server
  761.           and restores them based on the client workspace options and platform
  762.           type. However, in special cases it can be useful to store line-ending
  763.           in the server and use the 'share' option in the client. To disable
  764.           normal line-ending support set the following option to '<code>false</code>':
  765.           <pre><code>com.p4convert.adv.lineEnding=true</code></pre>
  766.         </li>
  767.         <li>For non Unicode servers or to simplify storage of hi-ASCII files,
  768.           setting following option to '<code>false</code>' will store the file
  769.           as '<code>binary</code>':
  770.           <pre><code>com.p4convert.p4.unicode=false</code></pre>
  771.         </li>
  772.       </ol>
  773.       <p></p>
  774.     </div>
  775.     <div class="section"> <a name="section15"></a>
  776.       <h2>Post Conversion [Conversion Mode]</h2>
  777.       To finish the conversion you will need to install p4 and p4d and run a few
  778.       Perforce commands.
  779.       <ol>
  780.         <li> [Required] Change directory to P4ROOT, check there are no db.*
  781.           files present and then replay the journal file(s):
  782.           <pre><code>$ cd p4_root
  783. $ p4d -r . -jr jnl.0
  784. Perforce db files in '.' will be created if missing...
  785. Recovering from jnl.0...
  786. Perforce server info:
  787. 	Server version 33 is replaying a version 0 journal/checkpoint.</code></pre>
  788.           Note: the Server version is set to 0 to remind the administrator that
  789.           an upgrade is required, see step 3.<br />
  790.         </li>
  791.         <li>or, for multiple journal files:
  792.           <pre><code>$ p4d -r . -jr jnl.0 jnl.1 ....</code></pre>
  793.           and with nohup:
  794.           <pre><code>nohup p4d -r . -jr jnl.0 jnl.1 .... &amp;</code></pre>
  795.         </li>
  796.         <li> [Required] Upgrade the database from 2004.2 schema. For simplicity
  797.           the conversion generates a database using an old schema, allowing you
  798.           to upgrade to a Perforce Server version of your choice. From the
  799.           P4ROOT directory run the upgrade command:
  800.           <pre><code>$ p4d -r . -xu
  801. Perforce db files in '.' will be created if missing...
  802. 2001.1: splitting db.integ into db.integed/db.resolve.
  803. 2001.1: splitting db.have into db.have and db.label.
  804. 2002.1: splitting pending db.change into db.changex.
  805. 2002.2: upgrading tempobj filetype in db.rev.
  806. 2002.2: upgrading tempobj filetype in db.working.
  807. 2003.1: initialize default depot.
  808. 2003.2: upgrading db.user.
  809. 2005.1: building db.revhx (headrev) table.
  810. 2005.1: building db.locks from db.working.
  811. 2005.2: building db.revdx (delrev) table.
  812. 2005.2: moving spec depot entries into db.revsx.
  813. 2007.3: (re)building haveMap from db.have/db.working.
  814. 2007.3: (re)building db.archmap (lazy-copy map) table.
  815. 2007.3: removing old db.archive.
  816. 2008.1: upgrading db.change.
  817. 2009.2: moving db.boddate/db.ixdate into db.bodtext/db.ixtext.
  818. 2009.2: removing db.boddate/db.ixdate.
  819. 2010.2: adding db.config.
  820. 2011.1: upgrading tiny.db.
  821. ...upgrades done</code></pre>
  822.         </li>
  823.         <li>[Optional] If the conversion was run in Unicode mode (where <code>com.p4convert.p4.unicode=true</code>)
  824.           and users are going to continue to add Unicode content then you may
  825.           wish to set the server to Unicode mode. To enable Unicode run the
  826.           following command from the P4ROOT directory:
  827.           <pre><code>$ p4d -r . -xi</code></pre>
  828.         </li>
  829.         <li>[Alternative] If you are running your Perforce Server on Linux and
  830.           your user base is predominantly Windows you may wish to force the
  831.           server to run as case insensitive (only allowing one version of case
  832.           for paths and files). The conversion option <code>com.p4convert.adv.lowerCase=true</code>
  833.           will have been used with the case mode set to <code>com.p4convert.adv.caseMode=FIRST</code>
  834.           . All p4d commands must be include the '<code>-C1</code>' flag, this
  835.           includes the earlier step 1 and step 2.<br />
  836.           <p></p>
  837.           For example:
  838.           <pre><code>$ cd p4_root
  839. $ p4d <font color="#cc0000">-C1</font> -r . -jr jnl.0
  840. $ p4d <font color="#cc0000">-C1</font> -r . -xu</code></pre>
  841.         </li>
  842.         <li>[Recommended] Some archive files may not have MD5 sum digests
  843.           (typically where Subversion did not store the digest or the digest
  844.           does not match due to the use of keyword expansion). To fill in the
  845.           metadata for MD5 sum digests and archive file sizes use the verify
  846.           command (this might be best split into depots and sub directories for
  847.           large servers):
  848.           <pre><code>$ p4 verify -u //...</code></pre>
  849.         </li>
  850.       </ol>
  851.     </div>
  852.     <div class="section"> <a name="section17"></a>
  853.       <h2>NOTES: </h2>
  854.       <h3><a name="keyword_notes"></a>Keyword Expansion Issues:</h3>
  855.       The conversion process preserves keyword file types and sets these files
  856.       in Perforce with the +k modifier. However keywords in Subversion and
  857.       Perforce are expanded differently. For example: In Subversion the keyword
  858.       <b>$Revision$ </b>expands to:
  859.       <pre><code>$Revision: 25005 $</code>		(a change number in Perforce)</pre>
  860.       Another example is the keyword <b>$Date$</b>, which in Subversion gives
  861.       you the time as well...
  862.       <pre><code>$Date: 2006-02-17 12:09:10 +0000 (Fri, 17 Feb 2006) $</code></pre>
  863.       and in Perforce...
  864.       <pre><code>$Date: 2006/02/17 $</code></pre>
  865.       Here is a list of alternatives, (based on the above example):
  866.       <pre>$Revision$	==&gt; $Change$	gives	$Change: 25005 $<br />$Date$		==&gt; $DateTime$	gives	$DateTime: 2006/02/17 12:09:10 $
  867. 	</pre>
  868.       Due to the differences in keyword expansion the MD5 sum in Subversion is
  869.       not valid for use in Perforce. This is why any keyword expanded files has
  870.       an empty MD5 sum and why the <code>p4 verify -u //...</code> command is
  871.       recommended in the 'Optional Steps' section. </div>
  872.     <div class="section"> <a name="section18"></a>
  873.       <h2>Verification</h2>
  874.       Verification can be performed using a running Subversion server and
  875.       comparing the differences in files in Perforce using the audit log. To
  876.       enable the audit log set the following option to 'true' and choose the
  877.       file name.
  878.       <pre><code>
  879. com.p4convert.log.audit.enabled=true
  880. com.p4convert.log.audit.filename=audit.log
  881. </code></pre> A sample line of the audit log:
  882.       <pre># &lt;SVN path&gt;, &lt;SVN revision&gt;, &lt;P4 change&gt;, &lt;MD5 sum&gt;
  883. trunk/src/foo.c, 1, 1, 1234567890abcdef1234567890abcdef
  884. </pre> </div>
  885.     <div class="section"> <a name="section19"></a>
  886.       <h2>Output and Logs</h2>
  887.       <h3>Console output and logging configuration options</h3>
  888.       The default SLF4J logging options can be overwritten with another
  889.       configuration file; specify the <tt>log4j.configuration</tt> option with
  890.       a local file, using the syntax <tt>file:<i>your_local_file</i></tt>.<br />
  891.       <pre><code>java -Dlog4j.configuration=file:log4j.xml -jar p4convert-svn.jar <br /></code><code>
  892. </code></pre>Please use or refer to the sample 'debug.log4j.xml' for logging
  893.       options.<br />
  894.       <h3>These options are reserved for testing or future enhancements:</h3>
  895.       <pre><code>
  896. com.p4convert.core.test
  897. com.p4convert.core.version
  898. com.p4convert.svn.emptyDirEnabled
  899. com.p4convert.svn.emptyDirName
  900. com.p4convert.adv.mimeTypes=false
  901. </code></pre>
  902.       <h3> Reading Console/Logging output<br />
  903.       </h3>
  904.       <pre>Importing Subversion ranges:
  905.  
  906. start: 1 
  907. end:   23091
  908. last:  23091
  909. 		
  910. 1.0 A:D - trunk
  911. 1.1 A:D - trunk/src
  912. 1.2 A:F - trunk/src/foo.c (UTF-8)
  913. mapping: r1 =&gt; @1
  914. 		
  915. 2.0 A:F - trunk/src/bar.png (BINARY)
  916. mapping: r2 =&gt; @2
  917. ...
  918. </pre>
  919.       <p> Explanation of output lines, for example: <code>1.2 A:F -
  920.           trunk/src/foo.c (UTF-8)</code> </p>
  921.       <p> The numbering '1.2' refers to the current Subversion revision and the
  922.         node action. ('1' Subversion revision 1 and '.2' = the third node action
  923.         as '.0' would be the first index) </p>
  924.       <p> The letters 'A:F' refers to the Subversion action and if it is a file
  925.         or directory operation. </p>
  926.       <ul>
  927.         <li>A Add</li>
  928.         <li>B Branch</li>
  929.         <li>E Edit</li>
  930.         <li>I Integrate (merge fromNode)</li>
  931.         <li>M Merge (svn:mergeinfo)</li>
  932.         <li>C Copy (svn replace action with fromNode)</li>
  933.         <li>U Update (svn replace action)</li>
  934.         <li>R Remove (delete)</li>
  935.         <li>F File</li>
  936.         <li>D Directory</li>
  937.       </ul>
  938.       <p></p>
  939.       The subversion path <code>'trunk/src/foo.c'</code> is followed by the
  940.       detected type. <br />
  941.       <blockquote>
  942.         <table width="510" height="790" border="1">
  943.           <tbody>
  944.             <tr>
  945.               <td align="center"><strong>Detected type</strong><br />
  946.               </td>
  947.               <td align="center"><strong>Perforce base type</strong><br />
  948.               </td>
  949.             </tr>
  950.             <tr>
  951.               <td>UTF-8<br />
  952.               </td>
  953.               <td>Unicode<br />
  954.               </td>
  955.             </tr>
  956.             <tr>
  957.               <td>UTF-16BE<br />
  958.               </td>
  959.               <td>utf16<br />
  960.               </td>
  961.             </tr>
  962.             <tr>
  963.               <td>UTF-16LE<br />
  964.               </td>
  965.               <td>utf16<br />
  966.               </td>
  967.             </tr>
  968.             <tr>
  969.               <td>UTF-32BE<br />
  970.               </td>
  971.               <td>Unicode<br />
  972.               </td>
  973.             </tr>
  974.             <tr>
  975.               <td>UTF-32LE<br />
  976.               </td>
  977.               <td>Unicode<br />
  978.               </td>
  979.             </tr>
  980.             <tr>
  981.               <td>Shift_JIS<br />
  982.               </td>
  983.               <td>Unicode<br />
  984.               </td>
  985.             </tr>
  986.             <tr>
  987.               <td>ISO-2022-JP<br />
  988.               </td>
  989.               <td>downgraded to binary<br />
  990.               </td>
  991.             </tr>
  992.             <tr>
  993.               <td>ISO-2022-CN<br />
  994.               </td>
  995.               <td>downgraded to binary<br />
  996.               </td>
  997.             </tr>
  998.             <tr>
  999.               <td>ISO-2022-KR<br />
  1000.               </td>
  1001.               <td>downgraded to binary<br />
  1002.               </td>
  1003.             </tr>
  1004.             <tr>
  1005.               <td>GB18030<br />
  1006.               </td>
  1007.               <td>Unicode<br />
  1008.               </td>
  1009.             </tr>
  1010.             <tr>
  1011.               <td>EUC-JP<br />
  1012.               </td>
  1013.               <td>Unicode<br />
  1014.               </td>
  1015.             </tr>
  1016.             <tr>
  1017.               <td>EUC-KR<br />
  1018.               </td>
  1019.               <td>Unicode<br />
  1020.               </td>
  1021.             </tr>
  1022.             <tr>
  1023.               <td>Big5<br />
  1024.               </td>
  1025.               <td>Unicode<br />
  1026.               </td>
  1027.             </tr>
  1028.             <tr>
  1029.               <td>ISO-8859-1<br />
  1030.               </td>
  1031.               <td>Unicode<br />
  1032.               </td>
  1033.             </tr>
  1034.             <tr>
  1035.               <td>ISO-8859-2<br />
  1036.               </td>
  1037.               <td>Unicode<br />
  1038.               </td>
  1039.             </tr>
  1040.             <tr>
  1041.               <td>ISO-8859-5<br />
  1042.               </td>
  1043.               <td>Unicode<br />
  1044.               </td>
  1045.             </tr>
  1046.             <tr>
  1047.               <td>ISO-8859-6<br />
  1048.               </td>
  1049.               <td>downgraded to binary<br />
  1050.               </td>
  1051.             </tr>
  1052.             <tr>
  1053.               <td>ISO-8859-7<br />
  1054.               </td>
  1055.               <td>Unicode<br />
  1056.               </td>
  1057.             </tr>
  1058.             <tr>
  1059.               <td>ISO-8859-8<br />
  1060.               </td>
  1061.               <td>Unicode<br />
  1062.               </td>
  1063.             </tr>
  1064.             <tr>
  1065.               <td>windows-1251<br />
  1066.               </td>
  1067.               <td>Unicode<br />
  1068.               </td>
  1069.             </tr>
  1070.             <tr>
  1071.               <td>windows-1254<br />
  1072.               </td>
  1073.               <td>Unicode<br />
  1074.               </td>
  1075.             </tr>
  1076.             <tr>
  1077.               <td>windows-1256<br />
  1078.               </td>
  1079.               <td>downgraded to binary<br />
  1080.               </td>
  1081.             </tr>
  1082.             <tr>
  1083.               <td>KOI8-R<br />
  1084.               </td>
  1085.               <td>Unicode<br />
  1086.               </td>
  1087.             </tr>
  1088.             <tr>
  1089.               <td>ISO-8859-9<br />
  1090.               </td>
  1091.               <td>Unicode<br />
  1092.               </td>
  1093.             </tr>
  1094.             <tr>
  1095.               <td>IBM424_rtl<br />
  1096.               </td>
  1097.               <td>downgraded to binary<br />
  1098.               </td>
  1099.             </tr>
  1100.             <tr>
  1101.               <td>IBM424_ltr<br />
  1102.               </td>
  1103.               <td>downgraded to binary<br />
  1104.               </td>
  1105.             </tr>
  1106.             <tr>
  1107.               <td>IBM420_rtl<br />
  1108.               </td>
  1109.               <td>downgraded to binary<br />
  1110.               </td>
  1111.             </tr>
  1112.             <tr>
  1113.               <td>IBM420_ltr<br />
  1114.               </td>
  1115.               <td>downgraded to binary<br />
  1116.               </td>
  1117.             </tr>
  1118.             <tr>
  1119.               <td>BINARY<br />
  1120.               </td>
  1121.               <td>binary<br />
  1122.               </td>
  1123.             </tr>
  1124.           </tbody>
  1125.         </table>
  1126.       </blockquote>
  1127.       Note: The detected type is based on language detection using ICU4J and not
  1128.       Subversion MIME or Perforce detection.<br />
  1129.       <p> Finally '<code>mapping: r223 =&gt; @223</code>' refers to the
  1130.         Subversion revision number ('<code>r223</code>') to the Perforce
  1131.         changelist number ('<code>@223</code>'). Typically 1:1 unless offset or
  1132.         merged against an live or pre-existing Perforce Server. </p>
  1133.     </div>
  1134.     <div class="section"> <a name="section20"></a>
  1135.       <h2>Errors</h2>
  1136.       In 'Import Mode' Perforce related 'p4-java' messages are reported as
  1137.       warnings and should be verified, for example:
  1138.       <pre><code>
  1139. 46.3 A:F - repo/trunk/my.file
  1140. WARNING: p4java: //import/repo/trunk/my.file - file(s) up-to-date.
  1141. </code></pre> In 'Conversion Mode' errors are reported as 'Panics' and an
  1142.       exception is thrown.<br />
  1143.       <br />
  1144.       Problematic Subversion dump records can be extracted and sent to Perforce
  1145.       when it is not possible to send in the whole dumpfile. The extracted
  1146.       dumpfile only contains meta-data and the file content is removed and
  1147.       replaced with a block count.<br />
  1148.       <br />
  1149.       During an exception note the Subversion revision and node ID (the example
  1150.       above has a revision number of 46 and a node number of 3).<br />
  1151.       Then run the following command to extract the problematic record, for
  1152.       example:<br />
  1153.       <pre><code>$ java -jar dist/p4convert-svn.jar --extract 46.3 mysvndump.dump 
  1154.       <br />searching for node: 46.3...
  1155. <font color="#009900">Node-path: repo/trunk/my.file
  1156. Node-kind: file
  1157. Node-action: add
  1158. Prop-content-length: 10
  1159. Text-content-length: 308
  1160. Text-content-md5: 6a339b6ccf2af72d77169ef29b98eb0b
  1161. Content-length: 318
  1162.       
  1163. <br />PROPS-END</font></code></pre>
  1164.       A file is then generated called '<code>node.46.3.dump</code>' and will
  1165.       contain the Subversion record to be sent to Perforce. (The content
  1166.       highlighted in green is the Subversion meta-data, also contained in the
  1167.       file).<br />
  1168.       <br />
  1169.     </div>
  1170.     <p> </p>
  1171.     <div class="copyright"> Copyright 2013, Perforce Software Inc. All rights
  1172.       reserved. </div>
  1173.     <p></p>
  1174.   </body>
  1175. </html>
# Change User Description Committed
#1 10152 alan_petersen Populate //guest/alan_petersen/p4convert/...
from //guest/perforce_software/p4convert/....... «		 11 years ago
//guest/perforce_software/p4convert/p4convert-svn.html
#1 9807 Paul Allen Initial import of p4-convert (from change 894340) 11 years ago