Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EAD49D67F for ; Fri, 31 Aug 2012 15:17:02 +0000 (UTC) Received: (qmail 50775 invoked by uid 500); 31 Aug 2012 15:17:02 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 50745 invoked by uid 500); 31 Aug 2012 15:17:02 -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 50737 invoked by uid 99); 31 Aug 2012 15:17:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2012 15:17:02 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.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; Fri, 31 Aug 2012 15:16:59 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id ACDB723888E4 for ; Fri, 31 Aug 2012 15:16:16 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1379475 - in /ant/site/ivyde/production/history/trunk: book.html compatibility.html cpc/workspace.html dev/dev-env-setup.html dev/updatesite.html preferences.html release-notes.html Date: Fri, 31 Aug 2012 15:16:16 -0000 To: notifications@ant.apache.org From: hibou@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120831151616.ACDB723888E4@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: hibou Date: Fri Aug 31 15:16:15 2012 New Revision: 1379475 URL: http://svn.apache.org/viewvc?rev=1379475&view=rev Log: Update the trunk version Added: ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html (with props) Modified: ant/site/ivyde/production/history/trunk/book.html ant/site/ivyde/production/history/trunk/compatibility.html ant/site/ivyde/production/history/trunk/cpc/workspace.html ant/site/ivyde/production/history/trunk/dev/updatesite.html ant/site/ivyde/production/history/trunk/preferences.html ant/site/ivyde/production/history/trunk/release-notes.html Modified: ant/site/ivyde/production/history/trunk/book.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/book.html?rev=1379475&r1=1379474&r2=1379475&view=diff ============================================================================== --- ant/site/ivyde/production/history/trunk/book.html (original) +++ ant/site/ivyde/production/history/trunk/book.html Fri Aug 31 15:16:15 2012 @@ -74,11 +74,11 @@ The Apache IvyDE project is pleased to a Apache IvyDE is the Eclipse plugin which integrates Apache Ivy's dependency management into Eclipse™.

Apache IvyDE lets you manage your dependencies declared in an ivy.xml in your Java Eclipse projects, or any other kind of project which needs dependency management. Apache IvyDE will contribute to the classpath of your Java project or you can make it retrieve your dependencies directly into your project. Last but not least Apache IvyDE offer editors of ivy.xml and ivysettings.xml files with completion. Get some preview here: http://ant.apache.org/ivy/ivyde/screenshots.html.

Status of this release

-This release contains sevral major improvements along with some bug fixes. The major
improvements are about the resolve scheduler and how retrieved artifact are handled.
Thus this release is considered as a beta one.

Major Changes in this Release

+This release contains sevral major improvements along with some bug fixes. The major improvements are about the resolve scheduler and how retrieved artifact are handled.
Thus this release is considered as a beta one.

Major Changes in this Release

-As for this release and the next ones, Apache IvyDE now expects to be installed in Eclipse 3.4 or superior.

Apache IvyDE has now a synchronous job to launch resolve of dependencies on the projets. So
IvyDE will be able to order the resolve of the projects in the correct order regarding
their inter dependencies. And the immediate effect is that Eclipse get notified only
one time of a classpath change, and thus triggerin only one wrokspace build.

Apache IvyDE is now capable of having a classpath based on retrieved artifact rather than
on the cached ones.

The existing retrieve configuration are now considered "standonale" ones, as they
are independant of the classpath container. They can even now be part of non Java
project.

Committers and Contributors for this Release

+As for this release and the next ones, Apache IvyDE now expects to be installed in Eclipse 3.4 or superior.

Apache IvyDE has now a synchronous job to launch resolve of dependencies on the projets. So IvyDE will be able to order the resolve of the projects in the correct order regarding their inter dependencies. And the immediate effect is that Eclipse get notified only one time of a classpath change, and thus triggerin only one wrokspace build.

Apache IvyDE is now capable of having a classpath based on retrieved artifact rather than on the cached ones.

The existing retrieve configuration are now considered "standonale" ones, as they are independant of the classpath container. They can even now be part of non Java project.

Committers and Contributors

-Here is the list of people who have contributed source code and documentation
to this release. Many thanks to all of them, and also to the whole IvyDE community
contributing ideas and feedback, and promoting the use of Apache IvyDE. The list would be too
long, but Apache IvyDE couldn't be what it is without you!
+Here is the list of people who have contributed source code and documentation up to this release. Many thanks to all of them, and also to the whole IvyDE community contributing ideas and feedback, and promoting the use of Apache IvyDE !
    Committers
  • Maarten Coene
  • Xavier Hanin
    • @@ -87,28 +87,71 @@ Here is the list of people who have cont
  • Gilles Scokart
    Contributors: +
  • Daniel Becheanu
    • +
  • Peter Blstak
  • Clint Burghduff
    • +
  • Peter Chanthamynavong
  • Gregory Fernandez
    • +
  • Thomas Friol
    • +
  • Troy Gaines
    • +
  • Eugene Goldfarb
    • +
  • Matt Goldspink
    • +
  • Will Gorman
    • +
  • Miguel Griffa
    • +
  • Adam Karl
    • +
  • Ivica Loncar
  • Jeffrey M. Metcalf
    • +
  • Sébastien Moran
    • +
  • Marko Niemi
    • +
  • Peter Oxenham
    • +
  • Joe Sortelli
    • +
  • Phillip Webb
    • +
  • James Wilkins

List of Changes in this Release

List of changes since Apache IvyDE 2.2.0 beta1:
    - +
  • NEW: Support Accepted Types: * (IVYDE-306)
    • +
  • NEW: Support Workspace/Filesystem/Variables for "Ivy File" setting (IVYDE-304)
    • +
  • NEW: Retrieve list does not resolve workspace projects (IVYDE-308) (thanks to Peter Oxenham)
    • +
  • NEW: Allow to set the Ivy user directory globally or project by project (IVYDE-311)
    • +
  • NEW: Add support for the OSGi access rules
    • +
  • NEW: Source and Javadoc attachements can now be edited jar by jar
- -Most of our changes are logged in our JIRA, where you can find comments and links to our subversion:
https://issues.apache.org/jira/browse/ivyde

License
Compatibility

Upgrading/Downgrading

+
    +
  • IMPROVE: The properties file paths can now be edited
    • +
  • IMPROVE: ivy.xml and ivysettings.xml files are not better detected as such, so they can be open with the Ivy editors
    • +
+
    +
  • FIX: org.eclipse.swt.SWTException: Invalid thread access with Eclipse Juno (IVYDE-313)
    • +
  • FIX: Divide by zero during IvyDE resolve (IVYDE-312) (thanks to Joe Sortelli)
    • +
  • FIX: Ivy report view stopped working on Linux (IVYDE-292)
    • +
  • FIX: Ivy settings URL is constructed incorrectly from environment variable (IVYDE-314)
    • +
  • FIX: Incomplete variable substitution for ivysettings.xml (IVYDE-318)
    • +
  • FIX: In case of a multi-resolve, one fail make them all fail (IVYDE-316)
    • +
  • FIX: Cannot change retrieve pattern at the workspace level (IVYDE-301)
    • +
  • FIX: Resolution failure when workspace has project & artifact sub-element exists (IVYDE-296, IVYDE-319)
    • +
  • FIX: IvyDE classpath containers become empty on eclipse/MyEclipse startup (IVYDE-317)
    • +
+

Most of our changes are logged in our JIRA, where you can find comments and links to our subversion:
https://issues.apache.org/jira/browse/ivyde

License
Compatibility

Upgrading/Downgrading

This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of Apache IvyDE should work without any worries.

The reverse is not true, downgrading is not supported and may break your configuration.

Dependency on Apache Ivy

-Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy.

Eclipse™ integration

+Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy. In order to use some OSGi features, an Ivy 2.3 or superior is needed.

Eclipse™ integration

-Apache IvyDE has been maintained to be compatible with Eclipse 3.4, 3.5, 3.6 and 3.7.

JVM compability

+Apache IvyDE has been maintained to be compatible with Eclipse 3.4 to 3.7, and 4.2.

JVM compability

Apache IvyDE has been kept compatible with Java 1.4.

Installation

Install the last release via Internet

@@ -270,7 +313,7 @@ In some setup, if you want to mix some r
  • see the resolveMode attribute of module in the ivysettings.
    • -

    WTP support

    +Also note that if any of the resolver defined in your ivysettings.xml have the force attribute set to true, the workspace resolver may won't properly bind projects between them, as the forced resolver will take precedence.

    WTP support

    Note that WTP doesn't support IvyDE's workspace resolver. See the details in the page dedicated to WTP integration.

    Launch configuration

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

    Default behavior

    @@ -466,7 +509,7 @@ Completion comes with contextual help. T

    Resolve dependencies in workpace:

    Apache IvyDE allows Ivy dependencies between projects in the workspace to be realized through project references rather than jars from the repository. See the documentation for further information on this feature.

    Accepted types:

    -

    A comma separated list of extensions which will make IvyDE add the artifact to the classpath

    +

    A comma separated list of extensions which will make IvyDE add the artifact to the classpath. Setting * will make very kind of type accepted. Note that a type specified as a source or javadoc type won't be accepted in any manner.

    Order of the classpath entries:

    By default, the classpath container entries are ordered by order of declaration in the ivy.xml. When there are many entries, it can be useful to have them ordered lexically for enhanced readability.

    Build the classpath with:

    @@ -485,6 +528,8 @@ Completion comes with contextual help. T

    By default, Apache IvyDE will parse the ivy settings file each times it is needed (each resolve, refresh, clean cache or completion in the ivy editor). For remote ivysettings this can slow the UI dramatically, so it is possible to make IvyDE keep the settings in a cache and only reload them via the context menu on the container).

    Ivy settings path:

    The path to your ivy settings file. Leave it blank to use Ivy default resolvers. See also the documentation about Eclipse variables.

    +

    Ivy user dir:

    +

    The path to the default Ivy user directory, where Ivy have its default cache location

    Property files:

    This is a list of Java properties files to load before loading the ivysettings.xml. Specify in this files properties which you expect to use in the ivysettings.xml

    @@ -767,7 +812,7 @@ For an IvyDE release:

    Note: from now on in the present doc, ${VERSION} references the renamed version.

    Now the binary files need to be signed. +Now the binary files need to be signed.
    • For an Ivy release:
    • ./signArtifacts.sh ivy-${VERSION}
    • @@ -816,7 +861,48 @@ NB: adding or removing lines in vers 
      ant build-main-p2-repo
      -And now commit every modification in dist/release.

      +And now commit every modification in dist/release.

      Development Environment Setup

      This page describe how to setup an environment to develop IvyDE.

      Requirement

      + +

      Eclipse plugins

      + +
        +You need some plugins installed in your Eclipse: +
      • the PDE plugins
        • +
      • the Zest plugins if you want to work with the IvyDE resolve visualizer
        • +
      + +If you have a "Classic" Eclipse, the PDE plugins are already installed. Otherwise you should find them in the Eclipse update site "The Eclipse Project Updates". Under the section "Eclipse Platform SDK", the feature to install is called "Eclipse Platform SDK".

      The Zest plugins can be found in the Eclipse updatesite of your Eclipse distribution (Indigo, Juno, etc...). Under the section "Modeling", the feature to install is called "Graphical Editing Framework Zest Visualization Toolkit SDK".

      Ivy

      + +You will also need Ivy as it is a dependency of IvyDE. Either you will work against a release version of Ivy, or work against an- build form the source in your Eclipse. Note that even when working against a released version, you will still be able to run in debug mode, see the sources and put break points in Ivy code. You just won't be able to modify the sources.

      Running against a released version is the simpler. Just install it from the IvyDE updatesite in you Eclipse.

      Otherwise you will need to setup a project for Ivy in your workspace, see next section.

      Setup

      + +

      Import Ivy

      + +If you want to run against an Ivy from source in your workspace, you must import the Ivy project in your workspace. Otherwise, you can skip this section.

      The Ivy sources already contains the Eclipse metadata. Just "Import" from "Existing Project into Workspace".

      Import IvyDE

      + +Once the required plugins are installed, you can import the IvyDE plugins and features into your workspace. Just do a regular "Import" from "Existing Project into Workspace".

      If you just have to fix a bug or add a little feature to IvyDE, just import the "org.apache.ivyde.eclipse" plugin.
      If you intend to work on the resolve visualizer, you should import the plugin "org.apache.ivyde.eclipse.resolvevisualizer".

      Launch

      + +You will have to create you "Launch configuration".
      +
        +
      • In the Debug menu, select "Debug Configuration...".
        • +
      • On the section "Eclipse Application", right click and select "New".
        • +
      • Give a better name to your configuration: "IvyDE".
        • +
      • You may want to give a better location to the workspace in which the forked eclipse will run: for instance "${workspace_loc}/_eclipse/runtime-IvyDE"
        • +
      + +Now you can launch and so some happy debugging !

      Advanced tips

      + +

      Console log

      + +For old version of Eclipse only, in recent ones the option is automatically added.

      By default the logs of the forked Eclipse just goes in the Error log of the forked Eclipse. It is not ideal when browsing a stack trace since you will have to switch between the 2 Eclipse.
      Just add "-consoleLog" in the "Program Arguments" of the launch configuration so that errors of the forked Eclipse will go in the console of the host one.

      Slow fork

      + +Your hosting Eclipse may have a lot of plugins installed. By default, forking an Eclipse will launch with the same plugins. So forking may take some time and can be painful while developing.

      In the launch configuration, you can tune what plugins should be loaded in the "Plug-ins" tab. Select "plug-ins selected below only". Then it is quite tedious to know which one should be selected. The button "Add Required Plug-ins" will help you not missing one. +
        Basically you will need: +
      • org.eclipse.ivyde (in your workspace)
        • +
      • org.eclipse.ivy (in your workspace if you have one)
        • +
      • org.eclipse.sdk
        • +
      • org.eclipse.jdt.*
        • +
      +
    @@ -114,9 +115,9 @@ This version is compatible with every earlier Apache release (since 2.0.0.alpha1). Any upgrade of Apache IvyDE should work without any worries.

    The reverse is not true, downgrading is not supported and may break your configuration.

    Dependency on Apache Ivy

    -Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy.

    Eclipse™ integration

    +Apache IvyDE expects to be used with a version 2.1 or superior of Apache Ivy. In order to use some OSGi features, an Ivy 2.3 or superior is needed.

    Eclipse™ integration

    -Apache IvyDE has been maintained to be compatible with Eclipse 3.4, 3.5, 3.6 and 3.7.

    JVM compability

    +Apache IvyDE has been maintained to be compatible with Eclipse 3.4 to 3.7, and 4.2.

    JVM compability

    Apache IvyDE has been kept compatible with Java 1.4.

    Modified: ant/site/ivyde/production/history/trunk/cpc/workspace.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/cpc/workspace.html?rev=1379475&r1=1379474&r2=1379475&view=diff ============================================================================== --- ant/site/ivyde/production/history/trunk/cpc/workspace.html (original) +++ ant/site/ivyde/production/history/trunk/cpc/workspace.html Fri Aug 31 15:16:15 2012 @@ -96,6 +96,7 @@ @@ -140,7 +141,7 @@ In some setup, if you want to mix some r
  • see the resolveMode attribute of module in the ivysettings.
    • -

    WTP support

    +Also note that if any of the resolver defined in your ivysettings.xml have the force attribute set to true, the workspace resolver may won't properly bind projects between them, as the forced resolver will take precedence.

    WTP support

    Note that WTP doesn't support IvyDE's workspace resolver. See the details in the page dedicated to WTP integration.

    Added: ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html?rev=1379475&view=auto ============================================================================== --- ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html (added) +++ ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html Fri Aug 31 15:16:15 2012 @@ -0,0 +1,190 @@ + + + + + + + + +Development Environment Setup | Apache IvyDE™ + + + + + + + + + + +
    + + + + + + + + + + + + + +
    + + +
    + + + + + + + +
    +
    + +

    Development Environment Setup

    +
    This page describe how to setup an environment to develop IvyDE.

    Requirement

    + +

    Eclipse plugins

    + +
      +You need some plugins installed in your Eclipse: +
    • the PDE plugins
      • +
    • the Zest plugins if you want to work with the IvyDE resolve visualizer
      • +
    + +If you have a "Classic" Eclipse, the PDE plugins are already installed. Otherwise you should find them in the Eclipse update site "The Eclipse Project Updates". Under the section "Eclipse Platform SDK", the feature to install is called "Eclipse Platform SDK".

    The Zest plugins can be found in the Eclipse updatesite of your Eclipse distribution (Indigo, Juno, etc...). Under the section "Modeling", the feature to install is called "Graphical Editing Framework Zest Visualization Toolkit SDK".

    Ivy

    + +You will also need Ivy as it is a dependency of IvyDE. Either you will work against a release version of Ivy, or work against an- build form the source in your Eclipse. Note that even when working against a released version, you will still be able to run in debug mode, see the sources and put break points in Ivy code. You just won't be able to modify the sources.

    Running against a released version is the simpler. Just install it from the IvyDE updatesite in you Eclipse.

    Otherwise you will need to setup a project for Ivy in your workspace, see next section.

    Setup

    + +

    Import Ivy

    + +If you want to run against an Ivy from source in your workspace, you must import the Ivy project in your workspace. Otherwise, you can skip this section.

    The Ivy sources already contains the Eclipse metadata. Just "Import" from "Existing Project into Workspace".

    Import IvyDE

    + +Once the required plugins are installed, you can import the IvyDE plugins and features into your workspace. Just do a regular "Import" from "Existing Project into Workspace".

    If you just have to fix a bug or add a little feature to IvyDE, just import the "org.apache.ivyde.eclipse" plugin.
    If you intend to work on the resolve visualizer, you should import the plugin "org.apache.ivyde.eclipse.resolvevisualizer".

    Launch

    + +You will have to create you "Launch configuration".
    +
      +
    • In the Debug menu, select "Debug Configuration...".
      • +
    • On the section "Eclipse Application", right click and select "New".
      • +
    • Give a better name to your configuration: "IvyDE".
      • +
    • You may want to give a better location to the workspace in which the forked eclipse will run: for instance "${workspace_loc}/_eclipse/runtime-IvyDE"
      • +
    + +Now you can launch and so some happy debugging !

    Advanced tips

    + +

    Console log

    + +For old version of Eclipse only, in recent ones the option is automatically added.

    By default the logs of the forked Eclipse just goes in the Error log of the forked Eclipse. It is not ideal when browsing a stack trace since you will have to switch between the 2 Eclipse.
    Just add "-consoleLog" in the "Program Arguments" of the launch configuration so that errors of the forked Eclipse will go in the console of the host one.

    Slow fork

    + +Your hosting Eclipse may have a lot of plugins installed. By default, forking an Eclipse will launch with the same plugins. So forking may take some time and can be painful while developing.

    In the launch configuration, you can tune what plugins should be loaded in the "Plug-ins" tab. Select "plug-ins selected below only". Then it is quite tedious to know which one should be selected. The button "Add Required Plug-ins" will help you not missing one. +
      Basically you will need: +
    • org.eclipse.ivyde (in your workspace)
      • +
    • org.eclipse.ivy (in your workspace if you have one)
      • +
    • org.eclipse.sdk
      • +
    • org.eclipse.jdt.*
      • +
    + +
    + Printer Friendly +
    +
    + + + + + + + + + + + + +
    + + Propchange: ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html ------------------------------------------------------------------------------ svn:eol-style = native Propchange: ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html ------------------------------------------------------------------------------ svn:keywords = Date Revision Author HeadURL Id Propchange: ant/site/ivyde/production/history/trunk/dev/dev-env-setup.html ------------------------------------------------------------------------------ svn:mime-type = text/html Modified: ant/site/ivyde/production/history/trunk/dev/updatesite.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/dev/updatesite.html?rev=1379475&r1=1379474&r2=1379475&view=diff ============================================================================== --- ant/site/ivyde/production/history/trunk/dev/updatesite.html (original) +++ ant/site/ivyde/production/history/trunk/dev/updatesite.html Fri Aug 31 15:16:15 2012 @@ -97,6 +97,7 @@ @@ -121,7 +122,7 @@ For an IvyDE release:

    Note: from now on in the present doc, ${VERSION} references the renamed version.

    Now the binary files need to be signed. +Now the binary files need to be signed.
    • For an Ivy release:
    • ./signArtifacts.sh ivy-${VERSION}
    • Modified: ant/site/ivyde/production/history/trunk/preferences.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/preferences.html?rev=1379475&r1=1379474&r2=1379475&view=diff ============================================================================== --- ant/site/ivyde/production/history/trunk/preferences.html (original) +++ ant/site/ivyde/production/history/trunk/preferences.html Fri Aug 31 15:16:15 2012 @@ -96,6 +96,7 @@
    @@ -143,7 +144,7 @@

    Resolve dependencies in workpace:

    Apache IvyDE allows Ivy dependencies between projects in the workspace to be realized through project references rather than jars from the repository. See the documentation for further information on this feature.

    Accepted types:

    -

    A comma separated list of extensions which will make IvyDE add the artifact to the classpath

    +

    A comma separated list of extensions which will make IvyDE add the artifact to the classpath. Setting * will make very kind of type accepted. Note that a type specified as a source or javadoc type won't be accepted in any manner.

    Order of the classpath entries:

    By default, the classpath container entries are ordered by order of declaration in the ivy.xml. When there are many entries, it can be useful to have them ordered lexically for enhanced readability.

    Build the classpath with:

    @@ -162,6 +163,8 @@

    By default, Apache IvyDE will parse the ivy settings file each times it is needed (each resolve, refresh, clean cache or completion in the ivy editor). For remote ivysettings this can slow the UI dramatically, so it is possible to make IvyDE keep the settings in a cache and only reload them via the context menu on the container).

    Ivy settings path:

    The path to your ivy settings file. Leave it blank to use Ivy default resolvers. See also the documentation about Eclipse variables.

    +

    Ivy user dir:

    +

    The path to the default Ivy user directory, where Ivy have its default cache location

    Property files:

    This is a list of Java properties files to load before loading the ivysettings.xml. Specify in this files properties which you expect to use in the ivysettings.xml

    Modified: ant/site/ivyde/production/history/trunk/release-notes.html URL: http://svn.apache.org/viewvc/ant/site/ivyde/production/history/trunk/release-notes.html?rev=1379475&r1=1379474&r2=1379475&view=diff ============================================================================== --- ant/site/ivyde/production/history/trunk/release-notes.html (original) +++ ant/site/ivyde/production/history/trunk/release-notes.html Fri Aug 31 15:16:15 2012 @@ -96,6 +96,7 @@ @@ -127,11 +128,11 @@ The Apache IvyDE project is pleased to a Apache IvyDE is the Eclipse plugin which integrates Apache Ivy's dependency management into Eclipse™.

    Apache IvyDE lets you manage your dependencies declared in an ivy.xml in your Java Eclipse projects, or any other kind of project which needs dependency management. Apache IvyDE will contribute to the classpath of your Java project or you can make it retrieve your dependencies directly into your project. Last but not least Apache IvyDE offer editors of ivy.xml and ivysettings.xml files with completion. Get some preview here: http://ant.apache.org/ivy/ivyde/screenshots.html.

    Status of this release

    -This release contains sevral major improvements along with some bug fixes. The major
    improvements are about the resolve scheduler and how retrieved artifact are handled.
    Thus this release is considered as a beta one.

    Major Changes in this Release

    +This release contains sevral major improvements along with some bug fixes. The major improvements are about the resolve scheduler and how retrieved artifact are handled.
    Thus this release is considered as a beta one.

    Major Changes in this Release

    -As for this release and the next ones, Apache IvyDE now expects to be installed in Eclipse 3.4 or superior.

    Apache IvyDE has now a synchronous job to launch resolve of dependencies on the projets. So
    IvyDE will be able to order the resolve of the projects in the correct order regarding
    their inter dependencies. And the immediate effect is that Eclipse get notified only
    one time of a classpath change, and thus triggerin only one wrokspace build.

    Apache IvyDE is now capable of having a classpath based on retrieved artifact rather than
    on the cached ones.

    The existing retrieve configuration are now considered "standonale" ones, as they
    are independant of the classpath container. They can even now be part of non Java
    project.

    Committers and Contributors for this Release

    +As for this release and the next ones, Apache IvyDE now expects to be installed in Eclipse 3.4 or superior.

    Apache IvyDE has now a synchronous job to launch resolve of dependencies on the projets. So IvyDE will be able to order the resolve of the projects in the correct order regarding their inter dependencies. And the immediate effect is that Eclipse get notified only one time of a classpath change, and thus triggerin only one wrokspace build.

    Apache IvyDE is now capable of having a classpath based on retrieved artifact rather than on the cached ones.

    The existing retrieve configuration are now considered "standonale" ones, as they are independant of the classpath container. They can even now be part of non Java project.

    Committers and Contributors

    -Here is the list of people who have contributed source code and documentation
    to this release. Many thanks to all of them, and also to the whole IvyDE community
    contributing ideas and feedback, and promoting the use of Apache IvyDE. The list would be too
    long, but Apache IvyDE couldn't be what it is without you!
    +Here is the list of people who have contributed source code and documentation up to this release. Many thanks to all of them, and also to the whole IvyDE community contributing ideas and feedback, and promoting the use of Apache IvyDE !
      Committers
    • Maarten Coene
    • Xavier Hanin
      • @@ -140,22 +141,65 @@ Here is the list of people who have cont
    • Gilles Scokart
      Contributors: +
    • Daniel Becheanu
      • +
    • Peter Blstak
    • Clint Burghduff
      • +
    • Peter Chanthamynavong
    • Gregory Fernandez
      • +
    • Thomas Friol
      • +
    • Troy Gaines
      • +
    • Eugene Goldfarb
      • +
    • Matt Goldspink
      • +
    • Will Gorman
      • +
    • Miguel Griffa
      • +
    • Adam Karl
      • +
    • Ivica Loncar
    • Jeffrey M. Metcalf
      • +
    • Sébastien Moran
      • +
    • Marko Niemi
      • +
    • Peter Oxenham
      • +
    • Joe Sortelli
      • +
    • Phillip Webb
      • +
    • James Wilkins

    List of Changes in this Release

    List of changes since Apache IvyDE 2.2.0 beta1:
      - +
    • NEW: Support Accepted Types: * (IVYDE-306)
      • +
    • NEW: Support Workspace/Filesystem/Variables for "Ivy File" setting (IVYDE-304)
      • +
    • NEW: Retrieve list does not resolve workspace projects (IVYDE-308) (thanks to Peter Oxenham)
      • +
    • NEW: Allow to set the Ivy user directory globally or project by project (IVYDE-311)
      • +
    • NEW: Add support for the OSGi access rules
      • +
    • NEW: Source and Javadoc attachements can now be edited jar by jar
    - -Most of our changes are logged in our JIRA, where you can find comments and links to our subversion:
    https://issues.apache.org/jira/browse/ivyde

    +
      +
    • IMPROVE: The properties file paths can now be edited
      • +
    • IMPROVE: ivy.xml and ivysettings.xml files are not better detected as such, so they can be open with the Ivy editors
      • +
    +
      +
    • FIX: org.eclipse.swt.SWTException: Invalid thread access with Eclipse Juno (IVYDE-313)
      • +
    • FIX: Divide by zero during IvyDE resolve (IVYDE-312) (thanks to Joe Sortelli)
      • +
    • FIX: Ivy report view stopped working on Linux (IVYDE-292)
      • +
    • FIX: Ivy settings URL is constructed incorrectly from environment variable (IVYDE-314)
      • +
    • FIX: Incomplete variable substitution for ivysettings.xml (IVYDE-318)
      • +
    • FIX: In case of a multi-resolve, one fail make them all fail (IVYDE-316)
      • +
    • FIX: Cannot change retrieve pattern at the workspace level (IVYDE-301)
      • +
    • FIX: Resolution failure when workspace has project & artifact sub-element exists (IVYDE-296, IVYDE-319)
      • +
    • FIX: IvyDE classpath containers become empty on eclipse/MyEclipse startup (IVYDE-317)
      • +
    +

    Most of our changes are logged in our JIRA, where you can find comments and links to our subversion:
    https://issues.apache.org/jira/browse/ivyde

    Printer Friendly