You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by hi...@apache.org on 2010/11/26 14:52:54 UTC
svn commit: r1039355 - in /ant/ivy/ivyde/trunk/doc: cpc/cleancache.html
cpc/jarmapping.html cpc/maven.html cpc/resolve.html cpc/retrieve.html
cpc/workspace.html cpc/wtp.html dev/build.html dev/release.html
Author: hibou
Date: Fri Nov 26 13:52:53 2010
New Revision: 1039355
URL: http://svn.apache.org/viewvc?rev=1039355&view=rev
Log:
IVYDE-264:
* add more "Apache" prefix
Modified:
ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html
ant/ivy/ivyde/trunk/doc/cpc/maven.html
ant/ivy/ivyde/trunk/doc/cpc/resolve.html
ant/ivy/ivyde/trunk/doc/cpc/retrieve.html
ant/ivy/ivyde/trunk/doc/cpc/workspace.html
ant/ivy/ivyde/trunk/doc/cpc/wtp.html
ant/ivy/ivyde/trunk/doc/dev/build.html
ant/ivy/ivyde/trunk/doc/dev/release.html
Modified: ant/ivy/ivyde/trunk/doc/cpc/cleancache.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/cleancache.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/cleancache.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/cleancache.html Fri Nov 26 13:52:53 2010
@@ -24,7 +24,7 @@
</head>
<body>
<textarea id="xooki-source">
-IvyDE has the ability to clean the various types of Ivy caches.
+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 <b>Clean Ivy cache</b> entry. A menu of configured caches will be shown.
Modified: ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/jarmapping.html Fri Nov 26 13:52:53 2010
@@ -23,7 +23,8 @@
<script type="text/javascript" src="../xooki/xooki.js"></script>
</head>
<body>
- <textarea id="xooki-source">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.
+ <textarea id="xooki-source">
+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.
<h1>Finding jars types</h1>
@@ -34,7 +35,7 @@ There are three types of jars handled by
<li>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.</li>
</ul>
-To find the binary jars, IvyDE is relying on the "Accepted types" preference field you can find in the <a href="create.html">container configuration panel</a>, or in the <a href="../preferences.html#classpath">global one</a>. If the artifact has a type listed here, it is then added to the classpath.
+To find the binary jars, Apache IvyDE is relying on the "Accepted types" preference field you can find in the <a href="create.html">container configuration panel</a>, or in the <a href="../preferences.html#classpath">global one</a>. 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".
@@ -42,7 +43,7 @@ For the javadocs, it is relying on the "
<h1>Binding the jars</h1>
-The second step is to bind a source artifact with a binary one. IvyDE has the folowing algorithm:
+The second step is to bind a source artifact with a binary one. Apache IvyDE has the folowing algorithm:
<ul>
<li>first if a binary jar has the same artifact name than a source one, there are bound together.</li>
<li>if none matched, then IvyDE search for sources which have one of the suffix specified in "Sources suffixes".</li>
@@ -56,7 +57,7 @@ For instance, searching for the sources
<li>mylib-src.jar (type=source)</li>
</ul>
-Note that IvyDE don't care about the extension, it can be .zip too.
+Note that Apache IvyDE don't care about the extension, it can be .zip too.
Same apply for javadocs with respectively "Javadocs suffixes".</textarea>
<script type="text/javascript">xooki.postProcess();</script>
Modified: ant/ivy/ivyde/trunk/doc/cpc/maven.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/maven.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/maven.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/maven.html Fri Nov 26 13:52:53 2010
@@ -24,11 +24,11 @@
</head>
<body>
<textarea id="xooki-source">
-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.
+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 IvyDE:
+Both examples below are a good illustration of the simplicity of using maven poms in Apache IvyDE:
<ul>
<li><a href="#one">Maven1 sample</a></li>
<li><a href="#two">Maven2 sample</a></li>
@@ -64,7 +64,7 @@ This sample presents a simple use case i
<h1><a name="two"></a>Maven2 Sample</h1>
-This sample demonstrates how the IvyDE classpath container on a Maven2 pom can handle transitive dependencies.
+This sample demonstrates how the IvyDE classpath container on a Apache Maven 2 pom can handle transitive dependencies.
<b> - Create a new empty java project in Eclipse.</b>
@@ -78,7 +78,7 @@ This sample demonstrates how the IvyDE c
</ivysettings>
</code>
-Using the m2compatible attribute, you can benefit from Maven2 repository compatibility.
+Using the m2compatible attribute, you can benefit from Apache Maven 2 repository compatibility.
<b> - In your project, create a <tt>pom.xml</tt> file: </b>
Modified: ant/ivy/ivyde/trunk/doc/cpc/resolve.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/resolve.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/resolve.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/resolve.html Fri Nov 26 13:52:53 2010
@@ -26,9 +26,9 @@
<textarea id="xooki-source">
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.
+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 (<b>Windows > Preferences > Ivy</b>), 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.
+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 Apache 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 (<b>Windows > Preferences > Ivy</b>), 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.
<center><img src="../images/cp_resolve.jpg"></center><br/>
Modified: ant/ivy/ivyde/trunk/doc/cpc/retrieve.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/retrieve.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/retrieve.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/retrieve.html Fri Nov 26 13:52:53 2010
@@ -24,7 +24,7 @@
</head>
<body>
<textarea id="xooki-source">
-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.
+It is possible to make Apache 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".
Modified: ant/ivy/ivyde/trunk/doc/cpc/workspace.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/workspace.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/workspace.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/workspace.html Fri Nov 26 13:52:53 2010
@@ -24,9 +24,9 @@
</head>
<body>
<textarea id="xooki-source">
-Some projects are composed of mulpliple modules. Often, these modules have dependencies between them, dependencies managed by Ivy (of course!).
+Some projects are composed of mulpliple modules. Often, these modules have dependencies between them, dependencies managed by Apache 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.
+Eclipse is capable of calculating the workspace's build order according to dependencies between projects. To leverage this advantage, Apache 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 being 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.
Modified: ant/ivy/ivyde/trunk/doc/cpc/wtp.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/cpc/wtp.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/cpc/wtp.html (original)
+++ ant/ivy/ivyde/trunk/doc/cpc/wtp.html Fri Nov 26 13:52:53 2010
@@ -24,7 +24,7 @@
</head>
<body>
<textarea id="xooki-source">
-WTP refers to the <a href="http://www.eclipse.org/webtools/">Web Tools Platform</a> 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+).
+WTP refers to the <a href="http://www.eclipse.org/webtools/">Web Tools Platform</a> project from the Eclipse foundation which allows Eclipse users to easily develop, launch and debug web applications. Apache 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.
Modified: ant/ivy/ivyde/trunk/doc/dev/build.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/dev/build.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/dev/build.html (original)
+++ ant/ivy/ivyde/trunk/doc/dev/build.html Fri Nov 26 13:52:53 2010
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-This page describes how to build the IvyDE plugin from the source. The build is based on the Eclipse build system so it requires an Eclipse install. You also need to have an Ivy bundle installed.
+This page describes how to build the Apache IvyDE plugin from the source. The build is based on the Eclipse build system so it requires an Eclipse install. You also need to have an Ivy bundle installed.
<h1><a name="setup"></a>Setup of the build</h1>
@@ -40,9 +40,9 @@ Lots of ant target depends on that Eclip
baseLocation=/home/me/tools/eclipse-3.4
</code>
-<h2><a name="install-ivy"></a>The Ivy bundle</h2>
+<h2><a name="install-ivy"></a>The Apache Ivy bundle</h2>
-The IvyDE plugins depends on the Ivy 2.0 OSGi bundle. So the Ivy bundle have to be installed in the Eclipse installation before starting the build. An ant target will accomplished that task quite automatically. Inline help will be displayed when no property is specified:
+The IvyDE plugins depends on the Apache Ivy 2.0 OSGi bundle. So the Ivy bundle have to be installed in the Eclipse installation before starting the build. An Ant target will accomplished that task quite automatically. Inline help will be displayed when no property is specified:
<code>ant install-ivy</code>
<u>Note</u>: due to <a href="https://issues.apache.org/jira/browse/IVY-802">an old bug in the build script of Ivy</a>, the OSGi version of Ivy is "0.0.0" for every version older than the 2.0.0-RC1. So older version than 2.0.0-RC1 is not supported.
Modified: ant/ivy/ivyde/trunk/doc/dev/release.html
URL: http://svn.apache.org/viewvc/ant/ivy/ivyde/trunk/doc/dev/release.html?rev=1039355&r1=1039354&r2=1039355&view=diff
==============================================================================
--- ant/ivy/ivyde/trunk/doc/dev/release.html (original)
+++ ant/ivy/ivyde/trunk/doc/dev/release.html Fri Nov 26 13:52:53 2010
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-This documentation is defining every steps that needs to be accomplished when releasing IvyDE.
+This documentation is defining every steps that needs to be accomplished when releasing Apache IvyDE.
In this doc, the released version is denoted as $VERSION, so it HAVE to be replaced in the command line argument accordingly. There is also some $LOGIN which is referencing your login on the Apache machines.
<h1>Prepare</h1>
@@ -61,7 +61,7 @@ In the files:
</ul>
The header should look like this
<code>
-<title>${title} | IvyDE $VERSION Documentation</title>
+<title>${title} | Apache IvyDE $VERSION Documentation</title>
</code>
<h2>Commit your changes</h2>
@@ -111,7 +111,7 @@ And launch the vote on the ant-dev maili
<code>
Subject: [VOTE] IvyDE $VERSION Release
-I have built a release candidate for IvyDE $VERSION
+I have built a release candidate for Apache IvyDE $VERSION
You can download the distribution from this URL: http://people.apache.org/~$LOGIN/ivyde-$VERSION/
@@ -227,7 +227,7 @@ Edit the release notes in the documentat
<li>edit the content under "Release Annoucement": edit the version it is talking about and clean it up so it is a summary of the release notes</li>
<li>edit the content under "Status of this release": update it with the goal of the next release, or a TODO if it has not yet been defined</li>
<li>edit the content under "Major Changes in this Release": wipe it all and put there something like "Nothing done yet"</li>
- <li>edit the content under "List of Changes in this Release": remove the list of entries and update the version in "List of changes since IvyDE X.X.X"</li>
+ <li>edit the content under "List of Changes in this Release": remove the list of entries and update the version in "List of changes since Apache IvyDE X.X.X"</li>
</ul>
</textarea>
<script type="text/javascript">xooki.postProcess();</script>