Note that there are some explanatory texts on larger screens.

plurals
  1. POApache Ivy settings task and ivysettings.xml file
    primarykey
    data
    text
    <p>According to <a href="http://ant.apache.org/ivy/history/2.1.0/use/settings.html" rel="nofollow noreferrer">this</a> page, I need to declare an <code>&lt;ivy:settings&gt;</code> task inside my Ant build that helps Ant locate where the <code>ivysettings.xml</code> file is located. This setting file is where the definitions for all of my repositories can be found, as well as additional info.</p> <p>What's confusing me is this: according to that page (link provided above), the following attributes are possible for the <code>&lt;ivy:settings&gt;</code> task:</p> <ul> <li><code>id</code></li> <li><code>file</code></li> <li><code>url</code></li> <li><code>host</code></li> <li><code>realm</code></li> <li><code>username</code></li> <li><code>passwd</code></li> </ul> <p>The description for <code>url</code> is:</p> <blockquote> <p>url of the settings file to use</p> </blockquote> <p>Implying that the <code>ivysettings.xml</code> file can actually be stored on a different machine, perhaps even <em>inside the repository itself?!?</em>.</p> <p>But then the descriptions for the last for attributes (<code>host</code>, <code>realm</code>, <code>username</code>, <code>passwd</code>) are all of the variety:</p> <blockquote> <p>http authentication (host|realm|username|passwd)</p> </blockquote> <p><strong>To me, these descriptions, combined with the one for <code>url</code>, indicate that the <code>host</code>, <code>realm</code>, <code>username</code> and <code>passwd</code> attributes are connection credentials for locating and retreiving the <code>ivysettings.xml</code> file; and that they are <em>not</em> connection credentials for connecting to a remote repository.</strong></p> <p>This is further evidenced by the fact that Ivy allows you to define multiple repositories inside <code>ivysettings.xml</code>, including multiple <code>url-resolvers</code>, which could be different repositories located on different servers with different access credentials. Seeing that the <code>&lt;ivy:settings&gt;</code> task only allows you to specify one set of credentials with these attributes, again it seems to imply that these attributes are merely for finding and pulling down the <code>ivysettings.xml</code> file, and not for communicating with 1+ repos.</p> <p>So, I ask:</p> <ul> <li>Are these 4 attributes for connecting to a <code>url</code> where <code>ivysettings.xml</code> lives, or are they for connecting to a remote repository that is defined inside <code>ivysettings.xml</code>?</li> <li>If the answer to the question above is that they are credentials for locating <code>ivysettings.xml</code> at a remote <code>url</code>, then where do I place the credentials for communicating with the web server where my actual repo lives (as the server where <code>ivysettings.xml</code> lives and the server where my repo lives may be two different machines)?</li> <li>Is my suspicion that you can store <code>ivysettings.xml</code> at a remote <code>url</code> (remote server) correct? If so, how do I tell Ivy to look at <code>Server A</code> with <code>Loging Credentials A</code> to find my <code>ivysettings.xml</code> file, but to find my repository at <code>Server B</code> with <code>Login Credentials B</code>?</li> </ul> <p><strong>Please note</strong>, some of you may also find <a href="https://stackoverflow.com/questions/1195393/where-do-you-put-ivysettings-xml">this</a> question and think that my question here is a duplicate of it. I argue that the referenced question above is simply the question "where do I put the <code>ivysettings.xml</code> file?" My question is <em>kind of</em> similar, however, at its core, its really about understanding the intention of the <code>&lt;ivy:settings&gt;</code> attributes, and what they're trying to find: the settings file, or the repo(s) defined inside the settings file. Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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