Modified: jclouds/site-content/start/concepts/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/start/concepts/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/start/concepts/index.html (original) +++ jclouds/site-content/start/concepts/index.html Mon Feb 10 07:25:53 2025 @@ -150,51 +150,49 @@ <h1>Core Concepts</h1> </div> <ol> -<li><a href="#views">Views or "portable abstractions"</a></li> -<li><a href="#apis">APIs</a></li> -<li><a href="#providers">Providers</a></li> -<li><a href="#contexts">Contexts</a></li> + <li><a href="#views">Views or âportable abstractionsâ</a></li> + <li><a href="#apis">APIs</a></li> + <li><a href="#providers">Providers</a></li> + <li><a href="#contexts">Contexts</a></li> </ol> - -<h2><a id="views"></a>Views</h2> +<h2 id="views"><a id="views"></a>Views</h2> <p><a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/View.html";><strong>Views</strong></a> are portable abstractions that are designed to allow you to write code that uses cloud services without tying yourself to a specific vendor. Take <a href="https://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/index.html";>JDBC</a> as an example: rather than writing code directly for a specific type of database, you can make generic database requests, and the JDBC specification and drivers translate these into specific commands and statements for a certain type of database.</p> <p>Views generally make sense only once a reasonably broad set of functionality is supported by multiple vendors. In the cloud space, jclouds currently supports three such views:</p> <ul> -<li><a href="/start/blobstore/">BlobStore</a></li> -<li><a href="/start/compute/">ComputeService</a></li> -<li><a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/loadbalancer/LoadBalancerService.html";>LoadBalancerService</a></li> + <li><a href="/start/blobstore/">BlobStore</a></li> + <li><a href="/start/compute/">ComputeService</a></li> + <li><a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/loadbalancer/LoadBalancerService.html";>LoadBalancerService</a></li> </ul> +<h2 id="apis"><a id="apis"></a>APIs</h2> -<h2><a id="apis"></a>APIs</h2> - -<p>An <strong>API</strong> in jclouds describes the actual calls (often, but not always, HTTP requests) that can be executed against a specific cloud service to "do stuff". In the case of popular APIs, such as the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ec2/EC2Api.html";>EC2 compute API</a>, or the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/s3/S3Client.html";>S3 storage API</a>, there may be multiple vendors with cloud services that support that particular API. For example, EC2 is supported by <a href="/guides/aws-ec2/">Amazon</a> and <a href="/guides/openstack/">OpenStack</a>, amongst others.</p> +<p>An <strong>API</strong> in jclouds describes the actual calls (often, but not always, HTTP requests) that can be executed against a specific cloud service to âdo stuffâ. In the case of popular APIs, such as the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ec2/EC2Api.html";>EC2 compute API</a>, or the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/s3/S3Client.html";>S3 storage API</a>, there may be multiple vendors with cloud services that support that particular API. For example, EC2 is supported by <a href="/guides/aws-ec2/">Amazon</a> and <a href="/guides/openstack/">OpenStack</a>, amongst others.</p> -<p>A vendor may also support an API in multiple geographic locations. For example, <a href="/guides/rackspace/">Rackspace</a>'s Cloud Servers API is available both in the <a href="/reference/providers/#compute-providers">US</a> and the <a href="/reference/providers/#compute-providers">UK</a>.</p> +<p>A vendor may also support an API in multiple geographic locations. For example, <a href="/guides/rackspace/">Rackspace</a>âs Cloud Servers API is available both in the <a href="/reference/providers/#compute-providers">US</a> and the <a href="/reference/providers/#compute-providers">UK</a>.</p> -<h2><a id="providers"></a>Providers</h2> +<h2 id="providers"><a id="providers"></a>Providers</h2> -<p>A <strong>provider</strong> in jclouds represents a particular vendor cloud service that supports one or more APIs. For example, Amazon offers EC2 through the <a href="/guides/aws-ec2/"><code>aws-ec2</code> provider</a>, and Rackspace's Cloud Servers instance in the UK is available via the <a href="/reference/providers/#compute-providers"><code>rackspace-cloudservers-uk</code> provider</a>.</p> +<p>A <strong>provider</strong> in jclouds represents a particular vendor cloud service that supports one or more APIs. For example, Amazon offers EC2 through the <a href="/guides/aws-ec2/"><code class="language-plaintext highlighter-rouge">aws-ec2</code> provider</a>, and Rackspaceâs Cloud Servers instance in the UK is available via the <a href="/reference/providers/#compute-providers"><code class="language-plaintext highlighter-rouge">rackspace-cloudservers-uk</code> provider</a>.</p> -<p>Often, a jclouds provider is simply the appropriate <a href="#apis">API</a> together with service-specific instantiation values, such as the endpoint URL. In some cases, the vendor offers additional functionality that goes <em>beyond</em> the API. For example, AWS EC2 supports various calls and options that are not offered by other providers implementing the ''standard'' EC2 API.</p> +<p>Often, a jclouds provider is simply the appropriate <a href="#apis">API</a> together with service-specific instantiation values, such as the endpoint URL. In some cases, the vendor offers additional functionality that goes <em>beyond</em> the API. For example, AWS EC2 supports various calls and options that are not offered by other providers implementing the ââstandardââ EC2 API.</p> <p><a href="#views">Views</a>, <a href="#apis">APIs</a> and <a href="#providers">providers</a> work together in jclouds in the following way:</p> -<h4>APIs describe the calls that can be executed against a particular type of cloud service</h4> +<h4 id="apis-describe-the-calls-that-can-be-executed-against-a-particular-type-of-cloud-service">APIs describe the calls that can be executed against a particular type of cloud service</h4> <p>By looking at the API defintion in jclouds, you can see the actual calls that are available if you talk directly to this API.</p> -<h4>APIs support views</h4> +<h4 id="apis-support-views">APIs support views</h4> <p>Depending on the functionality provided by a particular API, it can be used to implement a particular jclouds view. For instance, EC2 provides the right functionality to support the <a href="/start/compute/">ComputeService</a> view, but is not useful for the <a href="/start/blobstore/">BlobStore</a> or LoadBalancer views.</p> <p>For some cloud services, one API can support multiple views.</p> -<h4>Providers implement APIs, and describe calls that can be executed against a specific vendor cloud service</h4> +<h4 id="providers-implement-apis-and-describe-calls-that-can-be-executed-against-a-specific-vendor-cloud-service">Providers implement APIs, and describe calls that can be executed against a specific vendor cloud service</h4> <p>Each provider in jclouds implements one or more APIs, which is why the provider classes generally extend the API classes. As discussed <a href="#providers">above</a>, some providers support calls in addition to those offered by the API.</p> @@ -202,33 +200,33 @@ <p>By implementing APIs, providers also support views. For instance, AWS EC2 supports the ComputeService view because it implements the EC2 API.</p> -<h3>What does this mean for you?</h3> +<h3 id="what-does-this-mean-for-you">What does this mean for you?</h3> -<h4>You can write highly portable code</h4> +<h4 id="you-can-write-highly-portable-code">You can write highly portable code</h4> -<p>If you code only using views, you will be able to run the same application against a large variety of different clouds, each with potentially a different API. For example, if you're using only the ComputeService, you could switch from AWS EC2 to <a href="/guides/vcloud">vCloud</a> without changing your code.</p> +<p>If you code only using views, you will be able to run the same application against a large variety of different clouds, each with potentially a different API. For example, if youâre using only the ComputeService, you could switch from AWS EC2 to <a href="/guides/vcloud">vCloud</a> without changing your code.</p> -<p>It's like writing your database layer purely against the JDBC specification: you should be able to move from PostgreSQL to MariaDB without code changes.</p> +<p>Itâs like writing your database layer purely against the JDBC specification: you should be able to move from PostgreSQL to MariaDB without code changes.</p> -<h4>You can use API-specific calls where needed</h4> +<h4 id="you-can-use-api-specific-calls-where-needed">You can use API-specific calls where needed</h4> -<p>If the particular views you are working with do not allow you to do exactly what you want, but the API supports the desired functionality, you can <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/View.html#unwrap()">"unwrap"</a> the view to access the underlying API. This reduces the portability of your code, but you can still move between providers that support this API.</p> +<p>If the particular views you are working with do not allow you to do exactly what you want, but the API supports the desired functionality, you can <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/View.html#unwrap(\)">âunwrapâ</a> the view to access the underlying API. This reduces the portability of your code, but you can still move between providers that support this API.</p> <p>For example, if you unwrap the EC2 API from a ComputeService view and talk directly to EC2, you will not be able move to vCloud without code changes any more. You will still be able to switch to a different provider that also supports the EC2 API, however.</p> -<h4>You can use provider-specific calls if you really have to</h4> +<h4 id="you-can-use-provider-specific-calls-if-you-really-have-to">You can use provider-specific calls if you really have to</h4> <p>If you really need to use calls or options offered only by a certain <em>provider</em>, you can even unwrap the view to access the provider itself. Some of the features of AWS EC2, for example, are <em>only</em> available on AWS EC2 and are not supported by other providers that implement the standard EC2 API.</p> <p>Obviously, this means your code is now tied to that specific provider, but that may be an acceptable tradeoff in your situation.</p> -<p>Finally, we have...</p> +<p>Finally, we haveâ¦</p> -<h2><a id="contexts"></a>Contexts</h2> +<h2 id="contexts"><a id="contexts"></a>Contexts</h2> <p>A context represents a specific connection to a particular provider. From the perspective of our database analogy, this would be broadly similar to a database connection against a specific DB.</p> -<p>Once you have created a context via the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ContextBuilder.html";>ContextBuilder</a> and are "connected" to a particular cloud service, you can either get any of the views that are supported by that provider, or go straight to the API or even to the provider level.</p> +<p>Once you have created a context via the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ContextBuilder.html";>ContextBuilder</a> and are âconnectedâ to a particular cloud service, you can either get any of the views that are supported by that provider, or go straight to the API or even to the provider level.</p> <p>Creating a context is an expensive operation, so in general it is a good idea to create one context per credential and target cloud when the application starts and close it when it terminates. Contexts are thread-safe, so can be shared across your application.</p>
Modified: jclouds/site-content/start/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/start/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/start/index.html (original) +++ jclouds/site-content/start/index.html Mon Feb 10 07:25:53 2025 @@ -184,7 +184,6 @@ </tbody> </table> - <div class="row clearfix"> <div id="footer" class="col-md-12 column"> <div id="footer"> Modified: jclouds/site-content/start/install/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/start/install/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/start/install/index.html (original) +++ jclouds/site-content/start/install/index.html Mon Feb 10 07:25:53 2025 @@ -156,14 +156,12 @@ <li><a href="#ant" data-toggle="tab">Ant</a></li> </ul> - - - <div class="tab-content"> <div class="tab-pane fade in active" id="download"> -<h2>Download the last version</h2> + +<h2 id="download-the-last-version">Download the last version</h2> <p><strong>Apache jclouds 2.5.0</strong> is now available. See the <a href="/releasenotes/2.5.0">release notes</a> for more information on the list of changes in this release.</p> @@ -182,43 +180,40 @@ <tbody> <tr> <td><a href="https://www.apache.org/dyn/closer.lua/jclouds/2.5.0/jclouds-2.5.0-source-release.tar.gz";>jclouds-2.5.0.tar.gz</a></td> - <td><a href="https://www.apache.org/dist/jclouds/2.5.0/jclouds-2.5.0-source-release.tar.gz.sha512";>SHA 512 checksum</td> - <td><a href="https://www.apache.org/dist/jclouds/2.5.0/jclouds-2.5.0-source-release.tar.gz.asc";>PGP signature</td> -</tr> -</tbody> -</table> + <td><a href="https://www.apache.org/dist/jclouds/2.5.0/jclouds-2.5.0-source-release.tar.gz.sha512";>SHA 512 checksum</td> + <td><a href="https://www.apache.org/dist/jclouds/2.5.0/jclouds-2.5.0-source-release.tar.gz.asc";>PGP signature</td> +</tr> +</tbody> +</table> +## Verify the integrity -<h2>Verify the integrity</h2> +It is essential that you verify the integrity of the downloaded files using the `PGP` signatures and `SHA` checksums. Please read [Verifying Apache Releases](https://www.apache.org/info/verification.html) for more information on why you should verify our releases and how to do it. -<p>It is essential that you verify the integrity of the downloaded files using the <code>PGP</code> signatures and <code>SHA</code> checksums. Please read <a href="https://www.apache.org/info/verification.html";>Verifying Apache Releases</a> for more information on why you should verify our releases and how to do it.</p> +The [KEYS](https://www.apache.org/dist/jclouds/KEYS) file contains the public PGP keys used by Apache jclodus developers to sign releases. -<p>The <a href="https://www.apache.org/dist/jclouds/KEYS";>KEYS</a> file contains the public PGP keys used by Apache jclodus developers to sign releases.</p> +## Other versions +Downloads for all versions are hosted (and mirrored) in: -<h2>Other versions</h2> +* [Apache's release mirrors](https://www.apache.org/dyn/closer.cgi/jclouds/). +* [Archive repository](https://archive.apache.org/dist/jclouds/). -<p>Downloads for all versions are hosted (and mirrored) in:</p> - -<ul> -<li><a href="https://www.apache.org/dyn/closer.cgi/jclouds/";>Apache's release mirrors</a>.</li> -<li><a href="https://archive.apache.org/dist/jclouds/";>Archive repository</a>.</li> -</ul> - - -<p>You can also read the changelogs for <a href="/releasenotes">all versions</a>.</p> +You can also read the changelogs for [all versions](/releasenotes). +</a></td></a></td></tr></tbody></table> </div> <div class="tab-pane fade" id="maven"> -<h2>Maven configuration</h2> -<p>It is very easy to install jclouds using Apache Maven. If you're new to Maven, read <a href="https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html";>Maven in 5 Minutes</a>.</p> +<h2 id="maven-configuration">Maven configuration</h2> + +<p>It is very easy to install jclouds using Apache Maven. If youâre new to Maven, read <a href="https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html";>Maven in 5 Minutes</a>.</p> <p>If you do not have a <em>pom.xml</em> file, you can copy and paste the one below. If your project already has a <em>pom.xml</em> file, just add the dependency section below into it.</p> -<div class="highlight"><pre><code class="xml"><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span> -<span class="nt"><project</span> <span class="na">xmlns=</span><span class="s">"http://maven.apache.org/POM/4.0.0"</span> <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance"</span> <span class="na">xsi:schemaLocation=</span><span class="s">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span><span class="nt">></span> +<figure class="highlight"><pre><code class="language-xml" data-lang="xml"><span class="cp"><?xml version="1.0" encoding="UTF-8"?></span> +<span class="nt"><project</span> <span class="na">xmlns=</span><span class="s">"http://maven.apache.org/POM/4.0.0";</span> <span class="na">xmlns:xsi=</span><span class="s">"http://www.w3.org/2001/XMLSchema-instance";</span> <span class="na">xsi:schemaLocation=</span><span class="s">"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";</span><span class="nt">></span> <span class="nt"><modelVersion></span>4.0.0<span class="nt"></modelVersion></span> <span class="nt"><properties></span> <span class="nt"><jclouds.version></span>2.5.0<span class="nt"></jclouds.version></span> @@ -233,123 +228,106 @@ <span class="nt"><version></span>${jclouds.version}<span class="nt"></version></span> <span class="nt"></dependency></span> <span class="nt"></dependencies></span> -<span class="nt"></project></span> -</code></pre></div> - +<span class="nt"></project></span></code></pre></figure> -<h3>Download the binaries</h3> +<h3 id="download-the-binaries">Download the binaries</h3> <ul> -<li>Create a <em>pom.xml</em> file like the one in the <a href="#maven">Maven Configuration</a> section above.</li> -<li>Execute <code>mvn dependency:copy-dependencies</code>.</li> -<li>You'll notice a new directory <strong>target/dependency</strong> with all the jars you need.</li> + <li>Create a <em>pom.xml</em> file like the one in the <a href="#maven">Maven Configuration</a> section above.</li> + <li>Execute <code class="language-plaintext highlighter-rouge">mvn dependency:copy-dependencies</code>.</li> + <li>Youâll notice a new directory <strong>target/dependency</strong> with all the jars you need.</li> </ul> - </div> <div class="tab-pane fade" id="lein"> -<h2>Configuring Lein</h2> -<p>You can add jclouds to your <em>project.clj</em> like below, supporting clojure 1.2 and 1.3:</p> +<h2 id="configuring-lein">Configuring Lein</h2> -<div class="highlight"><pre><code class="clojure"><span class="ss">:dependencies</span> <span class="p">[[</span><span class="nv">org.clojure/clojure</span> <span class="s">"1.3.0"</span><span class="p">]</span> - <span class="p">[</span><span class="nv">org.clojure/core.incubator</span> <span class="s">"0.1.0"</span><span class="p">]</span> - <span class="p">[</span><span class="nv">org.clojure/tools.logging</span> <span class="s">"0.2.3"</span><span class="p">]</span> - <span class="p">[</span><span class="nv">org.apache.jclouds/jclouds-all</span> <span class="s">"2.5.0"</span><span class="p">]]</span> -</code></pre></div> +<p>You can add jclouds to your <em>project.clj</em> like below, supporting clojure 1.2 and 1.3:</p> +<figure class="highlight"><pre><code class="language-clojure" data-lang="clojure"><span class="no">:dependencies</span><span class="w"> </span><span class="p">[[</span><span class="n">org.clojure/clojure</span><span class="w"> </span><span class="s">"1.3.0"</span><span class="p">]</span><span class="w"> + </span><span class="p">[</span><span class="n">org.clojure/core.incubator</span><span class="w"> </span><span class="s">"0.1.0"</span><span class="p">]</span><span class="w"> + </span><span class="p">[</span><span class="n">org.clojure/tools.logging</span><span class="w"> </span><span class="s">"0.2.3"</span><span class="p">]</span><span class="w"> + </span><span class="p">[</span><span class="n">org.apache.jclouds/jclouds-all</span><span class="w"> </span><span class="s">"2.5.0"</span><span class="p">]]</span></code></pre></figure> -<h3> Download the binaries</h3> +<p>### Download the binaries</p> <ul> -<li>Download <a href="https://github.com/technomancy/leiningen/raw/stable/bin/lein";>lein</a> and make it executable.</li> -<li>Create a <em>project.clj</em> file with the below contents.</li> + <li>Download <a href="https://github.com/technomancy/leiningen/raw/stable/bin/lein";>lein</a> and make it executable.</li> + <li>Create a <em>project.clj</em> file with the below contents.</li> </ul> - -<div class="highlight"><pre><code class="clojure"><span class="p">(</span><span class="kd">defproject </span><span class="nv">deps</span> <span class="s">"1"</span> <span class="ss">:dependencies</span> <span class="p">[[</span><span class="nv">org.apache.jclouds/jclouds-all</span> <span class="s">"2.5.0"</span><span class="p">]</span> <span class="p">[</span><span class="nv">org.apache.jclouds.driver/jclouds-sshj</span> <span class="s">"2.5.0"</span><span class="p">]])</span> -</code></pre></div> - +<figure class="highlight"><pre><code class="language-clojure" data-lang="clojure"><span class="p">(</span><span class="nf">defproject</span><span class="w"> </span><span class="n">deps</span><span class="w"> </span><span class="s">"1"</span><span class="w"> </span><span class="no">:dependencies</span><span class="w"> </span><span class="p">[[</span><span class="n">org.apache.jclouds/jclouds-all</span><span class="w"> </span><span class="s">"2.5.0"</span><span class="p">]</span><span class="w"> </span><span class="p">[</span><span class="n">org.apache.jclouds.driver/jclouds-sshj</span><span class="w"> </span><span class="s">"2.5.0"</span><span class="p">]])</span></code></pre></figure> <ul> -<li>Execute <code>lein pom</code>, then <code>mvn dependency:copy-dependencies</code> which will fill <strong>target/dependency</strong> with all the jclouds jars.</li> + <li>Execute <code class="language-plaintext highlighter-rouge">lein pom</code>, then <code class="language-plaintext highlighter-rouge">mvn dependency:copy-dependencies</code> which will fill <strong>target/dependency</strong> with all the jclouds jars.</li> </ul> - <p>Replace the <em>provider</em> and <em>api</em> in the above directory paths to the ones you want to use in your project.</p> </div> <div class="tab-pane fade" id="ant"> -<h2>Ant configuration</h2> + +<h2 id="ant-configuration">Ant configuration</h2> <p>You will need to install <a href="https://maven.apache.org/ant-tasks/index.html";>maven ant tasks</a>. Then, add jclouds to your <em>build.xml</em> as shown below:</p> -<div class="highlight"><pre><code class="xml"><span class="nt"><artifact:dependencies</span> <span class="na">pathId=</span><span class="s">"jclouds.classpath"</span><span class="nt">></span> - <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span><span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> -<span class="nt"></artifact:dependencies></span> -</code></pre></div> +<figure class="highlight"><pre><code class="language-xml" data-lang="xml"><span class="nt"><artifact:dependencies</span> <span class="na">pathId=</span><span class="s">"jclouds.classpath"</span><span class="nt">></span> + <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span><span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> +<span class="nt"></artifact:dependencies></span></code></pre></figure> - -<h3>Download the binaries</h3> +<h3 id="download-the-binaries">Download the binaries</h3> <p>If you want to automate fetching the jclouds binaries, you can use the following Ant script.</p> -<p>Install <a href="https://ant.apache.org/";>ant</a>, copy the following into a <em>build.xml</em> file, tweaking things like 'provider' and 'driver' as necessary. The following example uses <strong>jclouds-all</strong>, <strong>jclouds-sshj</strong> as a driver, and includes the logback jars for a logging implementation.</p> +<p>Install <a href="https://ant.apache.org/";>ant</a>, copy the following into a <em>build.xml</em> file, tweaking things like âproviderâ and âdriverâ as necessary. The following example uses <strong>jclouds-all</strong>, <strong>jclouds-sshj</strong> as a driver, and includes the logback jars for a logging implementation.</p> <p>When you run this script with <em>ant</em>, it will build a <em>lib</em> directory full of jars you can later copy into your own project.</p> -<div class="highlight"><pre><code class="xml"><span class="nt"><project</span> <span class="na">default=</span><span class="s">"sync-lib"</span> <span class="na">xmlns:artifact=</span><span class="s">"urn:maven-artifact-ant"</span> <span class="nt">></span> - <span class="nt"><target</span> <span class="na">name=</span><span class="s">"sync-lib"</span> <span class="na">depends=</span><span class="s">"initmvn"</span><span class="nt">></span> - <span class="nt"><delete</span> <span class="na">dir=</span><span class="s">"lib"</span> <span class="nt">/></span> - <span class="nt"><mkdir</span> <span class="na">dir=</span><span class="s">"lib"</span> <span class="nt">/></span> - <span class="nt"><artifact:dependencies</span> <span class="na">filesetId=</span><span class="s">"jclouds.fileset"</span> <span class="na">versionsId=</span><span class="s">"dependency.versions"</span><span class="nt">></span> - <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span> <span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> - <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds.driver"</span> <span class="na">artifactId=</span><span class="s">"jclouds-sshj"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> - <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"ch.qos.logback"</span> <span class="na">artifactId=</span><span class="s">"logback-classic"</span> <span class="na">version=</span><span class="s">"[1.0.9,)"</span> <span class="nt">/></span> +<figure class="highlight"><pre><code class="language-xml" data-lang="xml"><span class="nt"><project</span> <span class="na">default=</span><span class="s">"sync-lib"</span> <span class="na">xmlns:artifact=</span><span class="s">"urn:maven-artifact-ant"</span> <span class="nt">></span> + <span class="nt"><target</span> <span class="na">name=</span><span class="s">"sync-lib"</span> <span class="na">depends=</span><span class="s">"initmvn"</span><span class="nt">></span> + <span class="nt"><delete</span> <span class="na">dir=</span><span class="s">"lib"</span> <span class="nt">/></span> + <span class="nt"><mkdir</span> <span class="na">dir=</span><span class="s">"lib"</span> <span class="nt">/></span> + <span class="nt"><artifact:dependencies</span> <span class="na">filesetId=</span><span class="s">"jclouds.fileset"</span> <span class="na">versionsId=</span><span class="s">"dependency.versions"</span><span class="nt">></span> + <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span> <span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> + <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds.driver"</span> <span class="na">artifactId=</span><span class="s">"jclouds-sshj"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> + <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"ch.qos.logback"</span> <span class="na">artifactId=</span><span class="s">"logback-classic"</span> <span class="na">version=</span><span class="s">"[1.0.9,)"</span> <span class="nt">/></span> <span class="nt"></artifact:dependencies></span> - <span class="nt"><copy</span> <span class="na">todir=</span><span class="s">"lib"</span> <span class="na">verbose=</span><span class="s">"true"</span><span class="nt">></span> - <span class="nt"><fileset</span> <span class="na">refid=</span><span class="s">"jclouds.fileset"</span><span class="nt">/></span> - <span class="nt"><mapper</span> <span class="na">type=</span><span class="s">"flatten"</span> <span class="nt">/></span> + <span class="nt"><copy</span> <span class="na">todir=</span><span class="s">"lib"</span> <span class="na">verbose=</span><span class="s">"true"</span><span class="nt">></span> + <span class="nt"><fileset</span> <span class="na">refid=</span><span class="s">"jclouds.fileset"</span><span class="nt">/></span> + <span class="nt"><mapper</span> <span class="na">type=</span><span class="s">"flatten"</span> <span class="nt">/></span> <span class="nt"></copy></span> <span class="nt"></target></span> - <span class="nt"><get</span> <span class="na">src=</span><span class="s">"https://search.maven.org/remotecontent?filepath=org/apache/maven/maven-ant-tasks/2.1.3/maven-ant-tasks-2.1.3.jar"</span> - <span class="na">dest=</span><span class="s">"maven-ant-tasks.jar"</span><span class="nt">/></span> + <span class="nt"><get</span> <span class="na">src=</span><span class="s">"https://search.maven.org/remotecontent?filepath=org/apache/maven/maven-ant-tasks/2.1.3/maven-ant-tasks-2.1.3.jar";</span> + <span class="na">dest=</span><span class="s">"maven-ant-tasks.jar"</span><span class="nt">/></span> - <span class="nt"><target</span> <span class="na">name=</span><span class="s">"initmvn"</span><span class="nt">></span> - <span class="nt"><path</span> <span class="na">id=</span><span class="s">"maven-ant-tasks.classpath"</span> <span class="na">path=</span><span class="s">"maven-ant-tasks.jar"</span><span class="nt">/></span> - <span class="nt"><typedef</span> <span class="na">resource=</span><span class="s">"org/apache/maven/artifact/ant/antlib.xml"</span> - <span class="na">uri=</span><span class="s">"urn:maven-artifact-ant"</span> - <span class="na">classpathref=</span><span class="s">"maven-ant-tasks.classpath"</span><span class="nt">/></span> + <span class="nt"><target</span> <span class="na">name=</span><span class="s">"initmvn"</span><span class="nt">></span> + <span class="nt"><path</span> <span class="na">id=</span><span class="s">"maven-ant-tasks.classpath"</span> <span class="na">path=</span><span class="s">"maven-ant-tasks.jar"</span><span class="nt">/></span> + <span class="nt"><typedef</span> <span class="na">resource=</span><span class="s">"org/apache/maven/artifact/ant/antlib.xml"</span> + <span class="na">uri=</span><span class="s">"urn:maven-artifact-ant"</span> + <span class="na">classpathref=</span><span class="s">"maven-ant-tasks.classpath"</span><span class="nt">/></span> <span class="nt"></target></span> -<span class="nt"></project></span> -</code></pre></div> - +<span class="nt"></project></span></code></pre></figure> <p>To only fetch the jars for a particular provider replace</p> -<div class="highlight"><pre><code class="xml"> <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span> <span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> -</code></pre></div> - +<figure class="highlight"><pre><code class="language-xml" data-lang="xml"> <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds"</span> <span class="na">artifactId=</span><span class="s">"jclouds-all"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span></code></pre></figure> <p>with</p> -<div class="highlight"><pre><code class="xml"> <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds.provider"</span> <span class="na">artifactId=</span><span class="s">"the-provider-id"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span> -</code></pre></div> - - +<figure class="highlight"><pre><code class="language-xml" data-lang="xml"> <span class="nt"><dependency</span> <span class="na">groupId=</span><span class="s">"org.apache.jclouds.provider"</span> <span class="na">artifactId=</span><span class="s">"the-provider-id"</span> <span class="na">version=</span><span class="s">"2.5.0"</span> <span class="nt">/></span></code></pre></figure> </div> </div> - <div class="row clearfix"> <div id="footer" class="col-md-12 column"> <div id="footer"> Modified: jclouds/site-content/start/what-is-jclouds/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/start/what-is-jclouds/index.html?rev=1923693&r1=1923692&r2=1923693&view=diff ============================================================================== --- jclouds/site-content/start/what-is-jclouds/index.html (original) +++ jclouds/site-content/start/what-is-jclouds/index.html Mon Feb 10 07:25:53 2025 @@ -149,7 +149,7 @@ <div class="page-header"> <h1>What is jclouds?</h1> </div> - <p>Apache jclouds® is an open source library that helps you get started in the cloud and utilizes your <a href="https://www.oracle.com/technetwork/java/index.html";>Java</a> + <p>Apache jclouds® is an open source library that helps you get started in the cloud and utilizes your <a href="https://www.oracle.com/technetwork/java/index.html";>Java</a> or <a href="https://clojure.org";>Clojure</a> development skills. The jclouds API gives you the freedom to use portable abstractions or cloud-specific features.</p> <p>jclouds tests support of 30 cloud providers and cloud software stacks including Amazon, Azure, GoGrid, OpenStack, Rackspace, and Google. Please see the @@ -174,8 +174,7 @@ complete list of <a href="/reference/pro </tbody> </table> - -<h1>Why should I use jclouds?</h1> +<h1 id="why-should-i-use-jclouds">Why should I use jclouds?</h1> <p>Programming against cloud environments can be challenging. jclouds focuses on the following areas so that you can get started in the cloud sooner.</p> @@ -219,7 +218,6 @@ complete list of <a href="/reference/pro </tbody> </table> - <div class="row clearfix"> <div id="footer" class="col-md-12 column"> <div id="footer">
