diff --git a/CHANGES.txt b/CHANGES.txt
index 895cea79..5bfad407 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -62,6 +62,7 @@ for detailed view of each issue, please consult http://issues.apache.org/jira/br
- NEW: Add a task/code to create M2 POM files from Ivy configurations (IVY-416)
- NEW: [Build] Publish the ivy sources (IVY-646) (thanks to Nicolas Lalevée)
+- IMPROVEMENT: Ease performance auditing (IVY-655)
- IMPROVEMENT: Maven Dependency Management is not used to determine artifact version (IVY-616) (thanks to Jim Bonanno)
- IMPROVEMENT: split the cache into an downloaded artifacts cache and a metadata cache (IVY-628)
- IMPROVEMENT: add publish triggers to event system (IVY-650) (thanks to Jason Trump)
diff --git a/doc/configuration/triggers.html b/doc/configuration/triggers.html
index 9f69a30b..4a19bb82 100644
--- a/doc/configuration/triggers.html
+++ b/doc/configuration/triggers.html
@@ -50,30 +50,33 @@ The event available in Ivy are the following ones:
confcomma separated list of configurations which will be resolved
- Fired before a module dependencies will be resolved |
+ Fired at the beginning of the resolve process, before a module dependencies and transitive dependencies are resolved. |
| pre-resolve-dependency |
- organisation
the organisation of the dependency resolved
- module
the name of the dependency resolved
- - revision
the revision asked for the dependency
+ - req-revision
the requested revision for the dependency since 2.0 (provided for consistency with post-resolve-dependency)
+ - revision
the requested revision for the dependency
- resolver
the name of the resolver used to resolve the dependency
|
- Fired before each dependency is resolved in a single resolve call |
+ Fired before each dependency is resolved. In this case resolved means resolving the actual revision if the requested revision is a version constraint and not a static version, and downloading all necessary metadata information. |
| post-resolve-dependency |
- organisation
the organisation of the dependency resolved
- module
the name of the dependency resolved
- - revision
the revision of the dependency resolved, or the revision asked if the resolution was not successful
+ - req-revision
the requested revision for the dependency since 2.0
+ - revision
the revision of the dependency resolved, or the requested revision if the resolution was not successful
- resolved
true if the resolution was successful, false otherwise
+ - duration
the time elapsed to resolve the dependency (in ms) since 2.0
- resolver
the name of the resolver used to resolve the dependency
|
- Fired after each dependency resolved in a single resolve call |
+ Fired after each dependency is resolved |
| post-resolve |
@@ -82,9 +85,15 @@ The event available in Ivy are the following ones:
modulethe name of the module for which the dependencies have been resolved
revisionthe revision of the module for which the dependencies have been resolved
confcomma separated list of configurations resolved
+ resolve-idthe identifier of the resolution process since 2.0
+ nb-dependenciestotal number of dependencies, including transitive and evicted ones since 2.0
+ nb-artifactstotal number of artifacts resolved, excluding metadata artifacts since 2.0
+ resolve-durationthe time (in ms) elapsed to resolve dependencies, before dowloading artifacts since 2.0
+ download-durationthe time (in ms) elapsed to download all artifacts, excluding metadata artifacts downloaded during the first phase of the resolution process since 2.0
+ download-sizethe total size (in bytes) of all downloaded artifacts, excluding metadata artifacts. Only artifacts actually downloaded (not in cache or used from their original location) are considered since 2.0
|
- Fired after a module dependencies has been resolved |
+ Fired at the end of the resolve process, when all module dependencies have been resolved |
| pre-download-artifact |
@@ -95,6 +104,7 @@ The event available in Ivy are the following ones:
artifactthe name of the the artifact which is about to be downloaded
typethe type of the the artifact which is about to be downloaded
extthe extension of the the artifact which is about to be downloaded
+ metadatatrue if the artifact to be downloaded is a metadata artifact, false for published artifacts since 2.0
resolverthe name of the resolver used to download the artifact
originthe origin location from which it will be downloaded
localtrue if it's a local artifact, false otherwise
@@ -111,15 +121,47 @@ The event available in Ivy are the following ones:
artifactthe name of the the artifact which was just downloaded
typethe type of the the artifact which was just downloaded
extthe extension of the the artifact which was just downloaded
+ metadatatrue if the downloaded artifact is a metadata artifact, false for published artifacts since 2.0
resolverthe name of the resolver used to download the artifact
originthe origin location from which it was downloaded
localtrue if it's a local artifact, false otherwise
sizethe size in bytes of the downloaded artifact
+ durationthe time elapsed to download the artifact (in ms) since 2.0
filethe file to which it has been downloaded
|
Fired after an artifact has been downloaded from a repository to the cache |
+ pre-retrieve since 2.0 |
+
+
+ - organisation
the organisation of the module for which the dependencies will be retrieved
+ - module
the name of the module for which the dependencies will be retrieved
+ - revision
the revision of the module for which the dependencies will be retrieved
+ - conf
comma separated list of configurations which will be retrieved
+ - symlink
true if Ivy will use symbolic links instead of copies on supported platforms, false otherwise
+ - sync
true if the retrieve process will be performed in sync mode, false otherwise
+
+ |
+ Fired at the beginning of the retrieve process. |
+
+ post-retrieve since 2.0 |
+
+
+ - organisation
the organisation of the module for which the dependencies have been retrieved
+ - module
the name of the module for which the dependencies will be retrieved
+ - revision
the revision of the module for which the dependencies have been retrieved
+ - conf
comma separated list of configurations which have been retrieved
+ - symlink
true if Ivy used symbolic links instead of copies on supported platforms, false otherwise
+ - sync
true if the retrieve process has been performed in sync mode, false otherwise
+ - duration
the time elapsed in ms during the retrieve process
+ - size
the total size of artifacts which have actually been copied (or symlinked)
+ - nbCopied
the number of artifacts copied or symlinked
+ - nbUptodate
the number of artifacts which were already present and up to date at the destination location
+
+ |
+ Fired at the end of the retrieve process. |
+
pre-publish-artifact since 2.0 |
@@ -182,6 +224,7 @@ Ivy comes with two built-in triggers:
| ant-build | Triggers an ant build. |
| ant-call | Calls a target in the current ant build. |
+| log | Logs a message on the console or in a log file. |
@@ -247,7 +290,17 @@ Here is how the target can look like:
-
+
+
+
+
+
+
+Logs any successful artifact download, with information on the source and destination, and details on download size and duration.
+
+The file attribute is optional, the log trigger will output messages to console if it isn't provided.
|