Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 62108 invoked from network); 18 Aug 2010 17:50:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Aug 2010 17:50:20 -0000 Received: (qmail 32257 invoked by uid 500); 18 Aug 2010 17:50:19 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 32204 invoked by uid 500); 18 Aug 2010 17:50:19 -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 32197 invoked by uid 99); 18 Aug 2010 17:50:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 17:50:19 +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, 18 Aug 2010 17:50:15 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 525072388A44; Wed, 18 Aug 2010 17:48:58 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r986820 [3/14] - in /ant/ivy/site/target/ivyde: ./ history/2.1.0/ history/2.1.0/cpc/ history/2.1.0/dev/ history/2.1.0/images/ history/2.1.0/js/ history/2.1.0/style/ history/latest-milestone/ history/latest-milestone/cpc/ history/latest-mile... Date: Wed, 18 Aug 2010 17:48:56 -0000 To: notifications@ant.apache.org From: hibou@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20100818174858.525072388A44@eris.apache.org> Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cp_container.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cp_container.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cp_container.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,118 @@ + + + + + + + +Clean the caches | IvyDE + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ + +
+ + + + + + + +
+
+ +

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.
+
    +
  • All: will clean every cache
    • +
  • Resolution cache: will clean only the cache of the resolution report
    • +
  • Every repository cache: will clean every cache dedicated to the artifacts
    • +
  • Cache 'xxxxxx': will clean only the cache with the specified name
    • +
+ +
+
+ Printer Friendly +
+
+ + + + + + + + + + + + +
+ + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/cleancache.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,124 @@ + + + + + + + +Create a container | IvyDE + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ + +
+ + + + + + + +
+
+ +

Create a container

+
First, locate an ivy.xml file or a maven pom.xml ready to be used to build a classpath. Also, if necessary, locate a supporting ivysettings.xml.

Fast creation

+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": +
    +
  • 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.



    • +
  • Select an ivy.xml file or a maven pom.xml and the desired configurations.



    • +
+
  • You then might want to use specific settings for your project, a configuration different from the global one. Click on the "Enable project specific settings" check box. For additional configuration options, see the documentation about Eclipse variables.

    • +Now your classpath is set and you can see all dependencies in one unique folder of the package explorer (folder name = ivy-file-name[conf1,conf2]).


    + + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/create.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,115 @@ + + + + + + + +Edit the classpath | 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:

    + +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.


    +
    +
    + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/edit.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,130 @@ + + + + + + + + +Launch configuration | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Launch configuration

    +
    The IvyDE classpath container can also be used in the launch configuration, run or debug.

    Default behavior

    + +By default, the container will be used because it is included in the default classpath of you project. This is the configuration that you implicitly have when you do a "Run As..." on a Java class. The container you see in the launch classpath is the same as the one you have in your project in the package explorer.

    + +Launching with the default the compile classpath might not be appropriate for some situations. For example, you may have additional libraries included in the container under a configuration intended to support unit testing but that may cause some instability in the runtime application.

    Managing the classpath manually

    + +When you do need to have finer-grained control over which configurations are visible to the runtime classpath, it is possible to edit the runtime classpath manually.

    By creating a launch configuration, you will get the default classpath as described above. So the first step is to remove it. Most likely, you will want to re-add your project in the user entries. Then to add an IvyDE container, choose "Advanced":

    + +Choose "Add Library":

    + +Choose "IvyDE Managed dependencies":

    + +Select the absolute path to your ivy.xml and select the proper configurations:

    + +Note: in the launch configuration it is not possible to edit or launch a resolve manually on the container you are creating. But it is possible to launch a resolve before each launch. It is recommended to do so if the resolve process is not too long. Otherwise you will have to recreate the container each time you change something in the ivy.xml for instance.

    To enable the resolve before each launch, go into the "Advanced" tab and select "Resolve before launch".

    + +Click "Finish" and see the result:

    + + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/launch.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,161 @@ + + + + + + + +Use with maven poms | 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: + + +

    Maven1 Sample

    + +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.
    + + - Add a new classpath container based on the "project.xml" pom and select "default" configuration (maven scope)

    + +
    + + - Finished. The project compiles!

    + +
    + + +

    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:
    +
    <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:
    +
    +<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>
+
    + + - On the pom.xml file, open the context menu and click on "Add Ivy Library...":

    - Select the configurations compile and runtime

    + +
    + + - Go into the "Settings" tab, select "Enable project specific settings" and click on the "Workspace..." button

    + +
    + + - Choose the ivysettings.xml file in your project

    + +
    + + - click "Finish"

    + +
    + + - That's all! Your IvyDE classpath container resolves all dependencies including those that were transitive to the commons-httpclient module!

    + +
    + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/maven.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,118 @@ + + + + + + + +Reload settings | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Reload settings

    +
    In case you have selected the "Reload the settings only on demand" option in the preferences, you can manually reload the settings via the context menu on the classpath container.

    + +Notes: +
      +
    • Reloading the settings will automatically launch a resolve
      • +
    • Reloading the settings in a project will not make other projects reload their settings even if they use the same settings file
      • +
    + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/reload_settings.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,123 @@ + + + + + + + +Launching resolve | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Launching resolve

    +
    You can explicitly ask for Ivy dependency resolution from your classpath container.

    This command will invoke the "resolve" ivy task and update your classpath container.

    There is also a "refresh" action: this action is similar to the resolve one, but does not perform a full resolve if a report already exists in the cache. This is particularly useful if you work with Ant and a command line so that you avoid two full resolves. It is also the default action performed on classpath containers when the Eclipse workspace is opened (Windows > Preferences > Ivy), in effect restoring the classpath container to its state prior to the last closing of the workspace if no other action is performed against the ivy.xml in the meantime.


    + +You can also trigger a resolve (not a refresh!) of every IvyDE classpath container in the workspace via the button in the tool bar of Eclipse.


    + +And to launch a resolve on a specified selection of projects: +
      +
    • Select the projects you want to resolve in the package view,
      • +
    • Open the context menu with a right click
      • +
    • Choose Ivy > Resolve
      • +
    + +

    + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/resolve.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,112 @@ + + + + + + + +Retrieve dependencies | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Retrieve dependencies

    +
    It is possible to make IvyDE copy resolved dependencies into your project: a retrieve of the dependencies can be triggered on each resolve of the classpath container.

    To enable this behavior, enter the classpath container configuration panel, and select the second tab, "Retrieve".

    + +The Retrieve pattern specifies the location where the dependencies should be copied relative to the containing project.

    The Delete old retrieved artifacts check box will cause IvyDE to clean the output directory before each retrieve. Note that any other artifacts other than those previously retrieved by IvyDE in this container will be deleted as well if this option is selected.

    Finally, you can select which Configurations should be resolved and you can select which Types of artifacts should actually be retrieved. In both fields, * means all.

    +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/retrieve.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,135 @@ + + + + + + + +Resolve in workspace | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Resolve in workspace

    +
    Some projects are composed of mulpliple modules. Often, these modules have dependencies between them, dependencies managed by Ivy (of course!).

    Eclipse is capable of calculating the workspace's build order according to dependencies between projects. To leverage this advantage, IvyDE has the ability to add a project reference to a dependency located in the workspace in place of downloading its published artifact(s) from the repository. In this way, developers can develop multi-module applications, and test the interaction between these modules, before building and publishing artifacts to the repository.

    Consider a multi-module application with a considerable amount of code in each of several projects. Many developers have experienced the delays involved in waiting for Eclipse to build code across all of these projects even though development is only bei ng conducted in one isolated part of the application (maybe just one or two projects). If the latest published artifact in the Ivy repository has the same source code as a module that the developer is not currently working on, simply closing that project in the Eclipse workspace and resolving dependencies on dependent projects that would resolve that artifact speeds the compilation process considerably.

    First, each application module should be separate a project in Eclipse, and each of these projects should have a configured IvyDE classpath container.

    To enable resolution in the workspace, go to the advanced configuration panel of the classpath container and select Resolve dependencies in workspace.

    + +Important notes: to make the resolve in workspace work correctly the info in the ivy.xml should be properly set: +
      +
    • The org and name
      • +
    • If there is a rev specified, dependencies should specify the appropriate range
      • +
    • If there is no rev specified, only dependencies with lastest will match
      • +
    • The status should match the required one: a dependency with latest.integration will only match if there is status="interation" in the info of the dependant module
      • +
    + +Having two projects "A" and "B" configured to use IvyDE and the workspace resolver, here is the expected resolved dependencies:
    + + + + + + + + + + + + +
    A dependency on BB declared revisionresult
    latest.integration1.2B wired on A
    1.21.2B wired on A
    [1.2,1.3)1.2B wired on A
    1.01.2no project wiring
    latest.integrationnoneB wired on A
    1.2noneB wired on A
    [1.2,1.3)noneB wired on A
    latest.integration$versionno project wiring
    1.2$versionno project wiring
    [1.2,1.3)$versionno project wiring
    + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/workspace.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html?rev=986820&view=auto ============================================================================== --- ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html (added) +++ ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html Wed Aug 18 17:48:51 2010 @@ -0,0 +1,123 @@ + + + + + + + +WTP integration | IvyDE + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    WTP integration

    +
    WTP refers to the Web Tools Platform project from the Eclipse foundation which allows Eclipse users to easily develop, launch and debug web applications. IvyDE works with WTP 2.0+ (Eclipse 3.3+).

    In the properties of your project configured to use WTP, there is a section titled "Java EE Module Dependencies". In this section you will find the IvyDE classpath container listed, usually with the name "ivy.xml [*]". Select it and dependencies found in the IvyDE classpath container will be deployed as well.

    + +This has been successfully tested with Eclipse 3.3/WTP 2.0, and Eclipse 3.4/WTP 3.0.

    IBM Rational Application Developer (RAD) 7.5.3+

    + +Users of RAD 7.5.3 will notice that the classpath container is not listed in the table. RAD prevents the deployment of classpath containers by default. To allow this behavior, selection Windows > Preferences > Java EE. Check "Allow loose classpath module dependencies". RAD will present you with a warning message. To enable the behavior, you need to check the option again in the popup and click Yes.

    +
    +Note: due to a bug in RAD 7.5.3, this IBM specific property is not persisted when we close the workbench and reopen it. To work around this: +
      +
    • Export RSA preferences ( File > Export > General > Preferences)
      • +
    • Open the exported .epf file and replace
      /instance/org.eclipse.jst.j2ee/org.eclipse.jst.j2ee.preferences.allowClasspathDep=false
      with
      /instance/org.eclipse.jst.j2ee/org.eclipse.jst.j2ee.preferences.allowClasspathDep=true
      • +
    • Load the modified .epf
      • +
    + + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/ivy/site/target/ivyde/history/2.1.0/cpc/wtp.html ------------------------------------------------------------------------------ svn:mime-type = text/html