Author: hibou
Date: Tue Nov 5 21:55:23 2013
New Revision: 1539145
URL: http://svn.apache.org/r1539145
Log:
Regenerate the trunk doc
Modified:
ant/site/ivyde/production/history/trunk/book.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=1539145&r1=1539144&r2=1539145&view=diff
==============================================================================
--- ant/site/ivyde/production/history/trunk/book.html (original)
+++ ant/site/ivyde/production/history/trunk/book.html Tue Nov 5 21:55:23 2013
@@ -76,7 +76,7 @@ Apache IvyDE is the Eclipse plugin which
This release is considered as stable. The beta of 2.2.0 has been out for a
(too) long time.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="majorchanges"></a>Major Changes in this Release</h1>
-The API of IvyDE has been stabilized so that third party plugins can rely on
it. The developper community will now ensure that the non "internal" package
will be kept backward compatible.<br class="xooki-br"/><br
class="xooki-br"/>While it is still not advertised as stable in Ivy, some
support of OSGi has been added. IvyDE can now read the OSGi metadata on the
dependencies being resolved and setup the proper access rules. It doesn't work
with the workspace resolver yet (see <a
href="https://issues.apache.org/jira/browse/IVYDE-350";>IVYDE-350</a>).<br
class="xooki-br"/><br class="xooki-br"/>IvyDE is automatically mapping sources
and javadocs to resolved jars. But now for edge cases, it is possible to
override the default mapping and edit the javadoc and source attachement jar by
jar.<br class="xooki-br"/><br class="xooki-br"/>The resolve process, the heart
of IvyDE features, has been even more stabalized and improved. For instance,
now at Eclipse startups IvyDE is far less required to
launch a resolve of the classpath; the privious state of the classpath
containers are saved between Eclipse sessions.<br class="xooki-br"/><br
class="xooki-br"/>IvyDE now have it own logging channel. In the Ivy console,
different levels can be choosed on how IvyDE itself is logging about the
resolve processes.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="contrib"></a>Committers and Contributors</h1>
+The API of IvyDE has been stabilized so that third party plugins can rely on
it. The developper community will now ensure that the non "internal" packages
will be kept backward compatible.<br class="xooki-br"/><br
class="xooki-br"/>While it is still not advertised as stable in Ivy, some
support of OSGi has been added. IvyDE can now read the OSGi metadata on the
dependencies being resolved and setup the proper access rules. It doesn't work
with the workspace resolver yet (see <a
href="https://issues.apache.org/jira/browse/IVYDE-350";>IVYDE-350</a>).<br
class="xooki-br"/><br class="xooki-br"/>IvyDE is automatically mapping sources
and javadocs to resolved jars. But now for edge cases, it is possible to
override the default mapping and edit the javadoc and source attachement jar by
jar.<br class="xooki-br"/><br class="xooki-br"/>The resolve process, the heart
of IvyDE features, has been even more stabilized and improved. For instance,
now at Eclipse startups IvyDE is far less required t
o launch a resolve of the classpaths; the previous state of the classpath
containers are saved between Eclipse sessions.<br class="xooki-br"/><br
class="xooki-br"/>IvyDE now have its own logging channel. In the Ivy console,
different levels can be chosen on how IvyDE itself is logging about the resolve
processes.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="contrib"></a>Committers and Contributors</h1>
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 !<br class="xooki-br"/>
<ul>Committers
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=1539145&r1=1539144&r2=1539145&view=diff
==============================================================================
--- ant/site/ivyde/production/history/trunk/release-notes.html (original)
+++ ant/site/ivyde/production/history/trunk/release-notes.html Tue Nov 5
21:55:23 2013
@@ -130,7 +130,7 @@ Apache IvyDE is the Eclipse plugin which
This release is considered as stable. The beta of 2.2.0 has been out for a
(too) long time.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="majorchanges"></a>Major Changes in this Release</h1>
-The API of IvyDE has been stabilized so that third party plugins can rely on
it. The developper community will now ensure that the non "internal" package
will be kept backward compatible.<br class="xooki-br"/><br
class="xooki-br"/>While it is still not advertised as stable in Ivy, some
support of OSGi has been added. IvyDE can now read the OSGi metadata on the
dependencies being resolved and setup the proper access rules. It doesn't work
with the workspace resolver yet (see <a
href="https://issues.apache.org/jira/browse/IVYDE-350";>IVYDE-350</a>).<br
class="xooki-br"/><br class="xooki-br"/>IvyDE is automatically mapping sources
and javadocs to resolved jars. But now for edge cases, it is possible to
override the default mapping and edit the javadoc and source attachement jar by
jar.<br class="xooki-br"/><br class="xooki-br"/>The resolve process, the heart
of IvyDE features, has been even more stabalized and improved. For instance,
now at Eclipse startups IvyDE is far less required to
launch a resolve of the classpath; the privious state of the classpath
containers are saved between Eclipse sessions.<br class="xooki-br"/><br
class="xooki-br"/>IvyDE now have it own logging channel. In the Ivy console,
different levels can be choosed on how IvyDE itself is logging about the
resolve processes.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="contrib"></a>Committers and Contributors</h1>
+The API of IvyDE has been stabilized so that third party plugins can rely on
it. The developper community will now ensure that the non "internal" packages
will be kept backward compatible.<br class="xooki-br"/><br
class="xooki-br"/>While it is still not advertised as stable in Ivy, some
support of OSGi has been added. IvyDE can now read the OSGi metadata on the
dependencies being resolved and setup the proper access rules. It doesn't work
with the workspace resolver yet (see <a
href="https://issues.apache.org/jira/browse/IVYDE-350";>IVYDE-350</a>).<br
class="xooki-br"/><br class="xooki-br"/>IvyDE is automatically mapping sources
and javadocs to resolved jars. But now for edge cases, it is possible to
override the default mapping and edit the javadoc and source attachement jar by
jar.<br class="xooki-br"/><br class="xooki-br"/>The resolve process, the heart
of IvyDE features, has been even more stabilized and improved. For instance,
now at Eclipse startups IvyDE is far less required t
o launch a resolve of the classpaths; the previous state of the classpath
containers are saved between Eclipse sessions.<br class="xooki-br"/><br
class="xooki-br"/>IvyDE now have its own logging channel. In the Ivy console,
different levels can be chosen on how IvyDE itself is logging about the resolve
processes.<br class="xooki-br"/><br class="xooki-br"/><h1><a
name="contrib"></a>Committers and Contributors</h1>
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 !<br class="xooki-br"/>
<ul>Committers
