StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><a href="https://stackoverflow.com/users/71343/dominic-mitchell">Dominic Mitchell</a>'s comment about the URL reference being a bad idea if you want repeatable builds got me thinking...</p> <p><strong>Another solution to consider, if you are using SVN for version control, is to create an <a href="http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html" rel="nofollow noreferrer">SVN Externals Definition</a> that points to the <code>common_directive.xml</code>.</strong> </p> <p>Then, just use a relative path for your ANT import file reference.</p> <blockquote> <p><strong>Sometimes it is useful to construct a working copy that is made out of a number of different checkouts.</strong> For example, you may want different subdirectories to come from different locations in a repository or perhaps from different repositories altogether. You could certainly set up such a scenario by hand—using <code>svn checkout</code> to create the sort of nested working copy structure you are trying to achieve. But if this layout is important for everyone who uses your repository, every other user will need to perform the same checkout operations that you did.</p> <p>Fortunately, Subversion provides support for externals definitions. <strong>An externals definition is a mapping of a local directory to the URL—and ideally a particular revision—of a versioned directory.</strong> In Subversion, you declare externals definitions in groups using the <code>svn:externals</code> property. You can create or modify this property using svn propset or svn propedit (see the section called “<a href="http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html#svn.advanced.props.manip" rel="nofollow noreferrer">Manipulating Properties</a>”). It can be set on any versioned directory, and its value describes both the external repository location and the client-side directory to which that location should be checked out.</p> <p><strong>The convenience of the <code>svn:externals</code> property is that once it is set on a versioned directory, everyone who checks out a working copy with that directory also gets the benefit of the externals definition.</strong> In other words, once one person has made the effort to define the nested working copy structure, no one else has to bother—Subversion will, after checking out the original working copy, automatically also check out the external working copies.</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload