Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 21201 invoked from network); 7 Dec 2010 00:01:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Dec 2010 00:01:42 -0000 Received: (qmail 35963 invoked by uid 500); 7 Dec 2010 00:01:42 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 35920 invoked by uid 500); 7 Dec 2010 00:01:42 -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 35892 invoked by uid 99); 7 Dec 2010 00:01:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Dec 2010 00:01:42 +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; Tue, 07 Dec 2010 00:01:32 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 3B1C42388C5A; Tue, 7 Dec 2010 00:00:33 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1042869 [13/15] - in /ant/ivy/site/target/ivyde/history: 1.2.0/ 1.2.0/style/ 2.0.0.alpha1/ 2.0.0.alpha1/style/ 2.0.0.beta1/ 2.0.0.beta1/dev/ 2.0.0.beta1/style/ 2.0.0.final/ 2.0.0.final/cpc/ 2.0.0.final/dev/ 2.0.0.final/style/ 2.1.0/ 2.1.0/... Date: Tue, 07 Dec 2010 00:00:30 -0000 To: notifications@ant.apache.org From: hibou@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20101207000033.3B1C42388C5A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: ant/ivy/site/target/ivyde/history/trunk/console.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/console.html?rev=1042869&r1=1042868&r2=1042869&view=diff ============================================================================== --- ant/ivy/site/target/ivyde/history/trunk/console.html (original) +++ ant/ivy/site/target/ivyde/history/trunk/console.html Tue Dec 7 00:00:26 2010 @@ -23,7 +23,7 @@ -Ivy Console | IvyDE +Ivy Console | Apache IvyDE™ @@ -41,11 +41,11 @@ cellpadding="0" cellspacing="0" width="100%">

+ src="images/logo.png" alt="Apache IvyDE™" border="0" /> @@ -55,7 +55,7 @@

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

@@ -67,9 +67,9 @@

IvyDE

Apache IvyDE™

@@ -79,7 +79,7 @@

Ivy Console

-
The Ivy console provides the Ivy working traces that are visible in the command console. This view can be useful for understanding what Ivy and IvyDE are doing under the covers.
+
The Ivy console provides the Ivy working traces that are visible in the command console. This view can be useful for understanding what Apache Ivy and Apache IvyDE are doing under the covers.
The Ivy Console can be accessed within your Eclipse Console view, by selecting the "Ivy Console" item.

@@ -120,7 +120,13 @@ To change the level of logging in the co -

+ Copyright © 2010 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
+ Apache IvyDE, Apache Ivy, Apache Ant, IvyDE, Ivy, Ant, Apache, the Apache IvyDE logo, the Apache Ivy logo, the Apache Ant logo and the Apache feather logo are trademarks of The Apache Software Foundation.
+ Eclipse and the Eclipse logo are trademarks of Eclipse Foundation, Inc. + All other marks mentioned may be trademarks or registered trademarks of their respective owners. +

Modified: ant/ivy/site/target/ivyde/history/trunk/cp_container.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/cp_container.html?rev=1042869&r1=1042868&r2=1042869&view=diff ============================================================================== --- ant/ivy/site/target/ivyde/history/trunk/cp_container.html (original) +++ ant/ivy/site/target/ivyde/history/trunk/cp_container.html Tue Dec 7 00:00:26 2010 @@ -22,7 +22,7 @@ -Classpath Container | IvyDE +Classpath Container | Apache IvyDE™ @@ -40,11 +40,11 @@ cellpadding="0" cellspacing="0" width="100%">

+ src="images/logo.png" alt="Apache IvyDE™" border="0" /> @@ -54,7 +54,7 @@

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

@@ -66,9 +66,9 @@

IvyDE

Apache IvyDE™

@@ -78,7 +78,7 @@

Classpath Container

-
The IvyDE classpath container will help you manage the classpath of your Eclipse projects, based on the dependencies declared in Ivy files found in your projects.

Some of the tasks that can be performed on the container include: +
The IvyDE classpath container will help you manage the classpath of your Eclipse™ projects, based on the dependencies declared in Ivy files found in your projects.

Some of the tasks that can be performed on the container include:

Create a container
Edit its setup

Modified: ant/ivy/site/target/ivyde/history/trunk/cpc/cleancache.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/cpc/cleancache.html?rev=1042869&r1=1042868&r2=1042869&view=diff ============================================================================== --- ant/ivy/site/target/ivyde/history/trunk/cpc/cleancache.html (original) +++ ant/ivy/site/target/ivyde/history/trunk/cpc/cleancache.html Tue Dec 7 00:00:26 2010 @@ -22,7 +22,7 @@ -Clean the caches | IvyDE +Clean the caches | Apache IvyDE™ @@ -40,11 +40,11 @@ cellpadding="0" cellspacing="0" width="100%">

+ src="../images/logo.png" alt="Apache IvyDE™" border="0" /> @@ -54,7 +54,7 @@

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

@@ -66,9 +66,9 @@

IvyDE

Apache IvyDE™

@@ -78,7 +78,7 @@

Clean the caches

-
IvyDE has the ability to clean the various types of Ivy caches.

On a configured IvyDE classpath container, open the context menu and select the Clean Ivy cache entry. A menu of configured caches will be shown.
+
Apache IvyDE has the ability to clean the various types of Ivy caches.

On a configured IvyDE classpath container, open the context menu and select the Clean Ivy cache entry. A menu of configured caches will be shown.

All: will clean every cache
Resolution cache: will clean only the cache of the resolution report

Modified: ant/ivy/site/target/ivyde/history/trunk/cpc/create.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/trunk/cpc/create.html?rev=1042869&r1=1042868&r2=1042869&view=diff ============================================================================== --- ant/ivy/site/target/ivyde/history/trunk/cpc/create.html (original) +++ ant/ivy/site/target/ivyde/history/trunk/cpc/create.html Tue Dec 7 00:00:26 2010 @@ -22,7 +22,7 @@ -Create a container | IvyDE +Create a container | Apache IvyDE™ @@ -40,11 +40,11 @@ cellpadding="0" cellspacing="0" width="100%">

+ src="../images/logo.png" alt="Apache IvyDE™" border="0" /> @@ -54,7 +54,7 @@

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

@@ -66,9 +66,9 @@

IvyDE

Apache IvyDE™

@@ -82,7 +82,7 @@ For most of the projects, the ivy.xml file (or the pom.xml) is in the java project. So you can just right click on the ivy.xml and select "Add Ivy Library..." and you can directly access the prefilled setup of the IvyDE classpath container

Standard creation

-The standard way to add the IvyDE classpath container is to manipulate the Eclipse's "Build Path": +The standard way to add the IvyDE classpath container is to manipulate the Eclipse™'s "Build Path":

Select the project in which you want to create an IvyDE classpath container and open the "Add Libraries" form of Eclipse (in package Explorer, in the context menu of your project choose : [Build Path]/[Add Libraries]).
Select the "IvyDE Managed Dependencies" item.

Edit the classpath | IvyDE

Edit the classpath | Apache IvyDE™

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

IvyDE

Apache IvyDE™

Edit the classpath

-
During the life of your project, you can change the ivy.xml file or maven pom.xml and change its configuration.

These properties can be accessed by he context menu of the IvyDE classpath container:

+
During the life of your project, you can change the ivy.xml file or maven pom.xml and change its configuration.

These properties can be accessed by the context menu of the IvyDE classpath container:

You can also edit it via the build path configuration. Open the build path configuration dialog, select the "Libraries" panel and select the IvyDE classpath container. Then click on the "Edit" button: the IvyDE classpath container configuration dialog will pop up.
This is particularly useful when Eclipse hides the empty classpath containers (since Eclipse 3.3). When the container is empty, this is the only way to trigger a resolve on this project.

@@ -107,7 +107,13 @@ You can also edit it via the build path -

Jar mapping | Apache IvyDE™

+ + + + + + + + + + + + + + + + + + + + + +

+ +

Jar mapping

+
Apache IvyDE will resolve the dependencies and artifacts you are requiring. Then with the pool of resolved artifacts, it has to decide which is a binary jar, which contains sources, and which contains javadocs. And also how to bind one on each other.

Finding jars types

+ +There are three types of jars handled by Eclipse™: +

the binary jars: they will be added to the classpath in oder to compile and run; they contain the .class files.
the source jars/zip: they will be bound to the binary one to browse dependency sources; they are basically a zip of .java files
the javadoc jars/zip: they will be bound to the binary one to browse the API documentation of the dependencies of your project; they are a zip of .html files respectin a layout produced by javadoc.

+ +To find the binary jars, Apache IvyDE is relying on the "Accepted types" preference field you can find in the container configuration panel, or in the global one. If the artifact has a type listed here, it is then added to the classpath.

For the sources, it is relying on the "Sources types".

For the javadocs, it is relying on the "Javadocs types".

Binding the jars

+ +The second step is to bind a source artifact with a binary one. Apache IvyDE has the folowing algorithm: +

first if a binary jar has the same artifact name than a source one, there are bound together.
if none matched, then IvyDE search for sources which have one of the suffix specified in "Sources suffixes".

+ +For instance, searching for the sources of mylib.jar (type=jar), with the default value of "Sources suffixes" ("-source,-sources,-src"), IvyDE will look to bind it to the first one existing of: +

mylib.jar (type=source)
mylib-source.jar (type=source)
mylib-sources.jar (type=source)
mylib-src.jar (type=source)

+ +Note that Apache IvyDE don't care about the extension, it can be .zip too.

Same apply for javadocs with respectively "Javadocs suffixes". +

+ Printer Friendly +

+ + + + + + + + + +

+ + +

Launch configuration | IvyDE

Launch configuration | Apache IvyDE™

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

IvyDE

Apache IvyDE™

Use with maven poms | IvyDE

Use with maven poms | Apache IvyDE™

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >

IvyDE

Apache IvyDE™

Use with maven poms

-
If you want to use a maven pom.xml instead of an ivy.xml file, you can select a pom file in the configuration options of the IvyDE classpath.

When a maven pom is selected, the configurations list is updated with all maven scopes.

Both examples below are a good illustration of the simplicity of using maven poms in IvyDE: +
If you want to use a Apache Maven™ pom.xml instead of an ivy.xml file, you can select a pom file in the configuration options of the IvyDE classpath.

When a maven pom is selected, the configurations list is updated with all maven scopes.

Both examples below are a good illustration of the simplicity of using maven poms in Apache IvyDE:

Maven1 sample
Maven2 sample

Maven1 Sample

- Download the commons httpclient sources

- Unzip this file (c:/tmp/commons-httpclient/)

- Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)

+This sample presents a simple use case involving a maven pom and the IvyDE classpath container. We are going to create an Eclipse™ project on commons-httpclient sources.

- Download the commons httpclient sources

- Unzip this file (c:/tmp/commons-httpclient/)

- Create a new Eclipse java project based on the unzipped sources (c:/tmp/commons-httpclient/)

Note: your project willnot compile: some imports cannot be resolved.
@@ -101,11 +101,11 @@ This sample presents a simple use case i

Maven2 Sample

-This sample demonstrates how the IvyDE classpath container on a Maven2 pom can handle transitive dependencies.

- Create a new empty java project in Eclipse.

- In your project, create an ivysettings.xml file:
+This sample demonstrates how the IvyDE classpath container on a Apache Maven 2 pom can handle transitive dependencies.

- Create a new empty java project in Eclipse.

- In your project, create an ivysettings.xml file:

<ivysettings>
	<conf defaultResolver="ibiblio"/>
	<resolvers>
		<ibiblio name="ibiblio" />
	</resolvers>
</ivysettings>

-Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.

- In your project, create a pom.xml file:
+Using the m2compatible attribute, you can benefit from Apache Maven 2 repository compatibility.

- In your project, create a pom.xml file:

 <project>
	<modelVersion>4.0.0</modelVersion>
	<groupId>com.mycompany</groupId>
	<artifactId>myproject</artifactId>
	<version>1.0-SNAPSHOT</version>
	<dependencies>
		<dependency>
			<groupId>commons-httpclient</groupId>
			<artifactId>commons-httpclient</artifactId>
			<version>3.0</version>
		</dependency>
	</dependencies>
</project>

@@ -153,7 +153,13 @@ Using the m2compatible attribute, you ca -

Reload settings | IvyDE

Reload settings | Apache IvyDE™

- Apache Ant > Ivy > IvyDE > History > + Apache™ > Apache Ant™ > Apache Ivy™ > Apache IvyDE™ > History >