Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 10234 invoked from network); 6 Oct 2010 21:26:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Oct 2010 21:26:55 -0000 Received: (qmail 50319 invoked by uid 500); 6 Oct 2010 21:26:55 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 50281 invoked by uid 500); 6 Oct 2010 21:26:55 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 50274 invoked by uid 99); 6 Oct 2010 21:26:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Oct 2010 21:26:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Oct 2010 21:26:51 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 8806E2388C9E; Wed, 6 Oct 2010 21:25:38 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1005260 [31/45] - in /ant/ivy/site/target/history/2.2.0: ./ configuration/ configuration/caches/ configuration/macrodef/ configuration/namespace/ dev/ images/ ivyfile/ js/ resolver/ samples/ settings/ settings/caches/ settings/macrodef/ se... Date: Wed, 06 Oct 2010 21:25:35 -0000 To: notifications@ant.apache.org From: maartenc@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20101006212538.8806E2388C9E@eris.apache.org> Added: ant/ivy/site/target/history/2.2.0/settings/signers.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/signers.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/signers.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/signers.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,180 @@ + + + + + + + +signers | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

signers

+
Tag: signers
since 2.2 + +Defines a list of detached signature generators usable in ivy. Each generator is identified by its name, given as an attribute.
The child tags used to configure the signature generator must be equal to the name of a signature generator type (either built-in or added with the typedef tag). + +Ivy supports the following signature generator out of the box: +
    +
  • pgp
    • generates an OpenPGP compatible ASCII armored detached signature. +
+ + +

Child elements

+ + + + + + + + +
ElementDescriptionCardinality
any signature generatoradds a signature generator to the list of registered generators1..n
+ +

Built-in Generators

+ +

PGP

+ +This generator is capable of generating an OpenPGP compatible ASCII armored detached signature.

Remark: This generator uses the BouncyCastle OpenPGP library. Before this generator can be used, these libraries must be available on Ivy's classpath.

+ + + + + + + + + + + + + + + + + + +
AttributeDescriptionRequired
nameThe name of the signature generator.Yes
secringThe location of the secret keyring.No, defaults to ${user.home}/.gnupg/secring.gpg
keyIdThe identifier of the key to use. The keyword 'auto' can be used to indicate a key will be selected automatically.No, defaults to 'auto'.
passwordThe password of the private key.Yes
+ +

Examples

+
+<signers>
    <pgp name="mypgp" password="my-password" />
</signers>
+
+Defines a detached signature generator with name 'mypgp' which uses the secret key ring on the default location and automatically selects a private key.
+
+<signers>
    <pgp name="mypgp" password="my-password" keyId="123ABC45"/>
</signers>
+
+Same as before, but this time the key '123ABC45' is used to generate the detached signature.
+
+
+ + + + + + + + + + + + +
+ + Added: ant/ivy/site/target/history/2.2.0/settings/status.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/status.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/status.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/status.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,140 @@ + + + + + + + +status | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

status

+
Tag: status

Define one available module status. + +See statuses page for details about how statuses are defined.

Attributes

+ + + + + + + + + + +
AttributeDescriptionRequired
namename of status definedYes
integrationtrue if this is an integration status, false otherwiseNo, defaults to false
+ +
+
+ + + + + + + + + + + + +
+ + Added: ant/ivy/site/target/history/2.2.0/settings/statuses.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/statuses.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/statuses.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/statuses.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,152 @@ + + + + + + + +statuses | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

statuses

+
Tag: statuses

Defines the list of available statuses. since 1.4 + +By default, ivy has 3 statuses: release, milestone and integration. By adding a statuses section to your ivysettings file, you define the statuses you want to use. Note that in this case if you still want to have ivy default statuses you will have to declare them.

The integration property on each status is only used for recursive delivery, an integration dependency being delivered if the caller is not in integration state itself.

The default status is the one used when none is defined in a module descriptor. If not specified, it defaults to the last defined status.

The statuses order is important, the first is considered the more mature, the last the less mature. This is used to know if a status is compatible with a latest.<status> version matcher.

Attributes

+ + + + + + + + +
AttributeDescriptionRequired
defaultthe name of the status to use when none is declared in an ivy fileNo, defaults to the last status declared
+

Child elements

+ + + + + + + + +
ElementDescriptionCardinality
statusdefines a new status0..n
+

Examples

+
+<statuses default="bronze">
  <status name="gold" integration="false"/>
  <status name="silver" integration="false"/>
  <status name="bronze" integration="true"/>
</statuses> 
+
+Defines 3 statuses, gold, silver and bronze. The default status used when none is declared in an ivy file will be bronze.
It is also considered as an integration status, and thus doesn't trigger any recrusive delivery.
+
+
+ + + + + + + + + + + + +
+ +