Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Whatever you do, don't checkout /jakarta/commons as you will be checking out a copy of every tag, trunk, and branch and it will take forever and a day. *Instead*, check out individual components, or (more likely) check out "trunks-proper" or "trunks-sandbox".

...

No Format
svn co https://svn.apache.org/repos/asf/jakarta/commons/trunks-proper/ jakarta/commons/trunks-proper
svn co https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox/ jakarta/commons/trunks-sandbox

Checkout individual components* _(Don't forget to checkout commons-build!)

No Format
svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk jakarta/commons/trunks-proper/commons-build
svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/dbcp/trunk jakarta/commons/trunks-proper/dbcp
No Format
svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk jakarta/commons/trunks-sandbox/commons-build
svn co https://svn.apache.org/repos/asf/jakarta/commons/sandbox/cache/trunk jakarta/commons/trunks-sandbox/cache

...

No Format
svn ls http://svn.apache.org/repos/asf/jakarta/commons

A web browser can also be used to view the repository structure, just by entering the URL that you would use for subversion operations. Note that this shows only the latest version of everything (directories and files).

...

No Format
svn import https://svn.apache.org/repos/asf/jakarta/commons/sandbox/PROJECT_NAME/trunk

...

If the trunk versions move on, and you later want beta1 to include one of the updated files, then update what "beta1" refers to by relinking from the beta1 directory to the version you really want:

  • Wiki Markup
    removing the file (link) you no longer need from the "tag" dir
         eg  svn rm https://....../tags/..../foo.txt \[1\]

  • Wiki Markup
    copying back in (ie link to) the version you want
         eg svn cp 
              -r 100 https://..../trunk/.../foo.txt  \[2\]
              https://..../tags/.../foo.txt   \[3\]
    \\

Wiki Markup
\[1\] or if you have a working copy of the tag dir, you can 
    do svn rm and svn commit
\[2\] if you want the latest version, just omit the -r 100.
\[3\] or if you have a working copy of the tag, copy to your working
    copy then svn commit it.

...

For some other traditional uses of CVS tags, it might be better to use subversion "properties" (see svn set-prop).

Maven 1 config*

project.properties*

No Format
maven.changelog.factory=org.apache.maven.svnlib.SvnChangeLogFactory

*

project.xml_'*

No Format
  <repository>
   <connection>scm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/${pom.artifactId.substring(8)}/trunk</connection>
    <url>http://svn.apache.org/repos/asf/jakarta/commons/proper/${pom.artifactId.substring(8)}/trunk</url>
  </repository>

Commons repo

Software

If you are trying to get the latest version of subeclipse, do not use Eclipse's "search for updates of existing features", instead use "search for new features." Eclipse kept telling me that there was no version greater than 0.9.22 while this fellow was telling me he'd just released 0.9.26. Running search for new features against the subversion.tigris.org site quickly found what I was looking for. Any jakarta- commons devs who want to try subeclipse but are stuck on 0.9.22 should try this.

...

Subversion client config

Add this to your subversion client configuration file:*

Note:_' make sure the settings are merged into the appropriate section if it already exists, as duplicate section names can cause problems.

Possible locations of your subversion client configuration

  • Windows: C:\Documents and Settings\yourname\Application Data\Subversion\config
  • Linux: ~/.subversion/config

...

See: http://www.apache.org/dev/svn-eol-style.txt for the canonical list of auto-props settings.