db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bakk...@apache.org
Subject svn commit: r329187 [63/66] - in /db/derby/code/trunk: ./ frameworks/NetworkServer/ frameworks/NetworkServer/bin/ frameworks/embedded/bin/ java/build/ java/build/org/apache/derbyBuild/ java/build/org/apache/derbyBuild/eclipse/ java/build/org/apache/der...
Date Fri, 28 Oct 2005 12:52:21 GMT
Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/derby_app.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/derby_app.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/derby_app.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/derby_app.html Fri Oct 28 04:51:50 2005
@@ -1,264 +1,264 @@
-<html>
-<head>
-<title>Creating a Java application to access a Derby database</title>
-</head>
-<body>
-<h2>Creating a Java application to access a Derby database</h2>
-<p>
-Once you've become familiar with starting the network server and running
-SQL queries, you'll want to use Derby from within a Java application.
-This section will demonstrate using Derby from a stand-alone Java
-application.
-</p>
-<p>
-This example will access the data in our sample database, <b>myDB</b>, 
-which contains the restaurants table.  By following the two <a href="ij_toc.html"><b>ij</b></a> sections in the help, this database and table will have already
-been created and ready to use.  If you have not created the database and the table return to the <a href="ij_toc.html"><b>ij</b></a> sections and create them now.
-</p>
-<h3>Steps to create a stand-alone Java application</h3>
-<ul>
-<li>
-From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
-<b>New, Class</b>.
-</li>
-</ul>
-</p>
-<img src="images/new_class.GIF" alt="Creating a Java class in Eclipse" width="914" height="638"></img>
-<p>
-Give the Java class a package name, <b>myapp</b>, name the class 
-<b>Restaurants</b>, make it a public class, and include a main method 
-in the class since this will be a stand-alone application.  The image 
-below shows an example of this. 
-Click <b>Finish</b> to create the class.
-</p>
-<img src="images/create_class.GIF" alt="New Java class wizard" width="515" height="566"></img>
-
-<p>
-The Java class shown below, <b>Restaurants.java</b>, connects to the Derby Network Server, inserts a row into the restaurants table, and then displays a select
-from the restaurants table.  Copy the code below into the Java editor window
-for the <b>Restaurants.java</b> class you just created. 
-</p>
-
-<pre>
-package myapp;
-import java.sql.Connection;
-import java.sql.DriverManager;
-import java.sql.ResultSet;
-import java.sql.SQLException;
-import java.sql.Statement;
-import java.sql.ResultSetMetaData;
-
-
-public class Restaurants
-{
-    private static String dbURL = "jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine";
-    private static String tableName = "restaurants";
-    // jdbc Connection
-    private static Connection conn = null;
-    private static Statement stmt = null;
-
-    public static void main(String[] args)
-    {
-        createConnection();
-        insertRestaurants(5, "LaVals", "Berkeley");
-        selectRestaurants();
-        shutdown();
-    }
-    
-    private static void createConnection()
-    {
-        try
-        {
-            Class.forName("org.apache.derby.jdbc.ClientDriver").newInstance();
-            //Get a connection
-            conn = DriverManager.getConnection(dbURL); 
-        }
-        catch (Exception except)
-        {
-            except.printStackTrace();
-        }
-    }
-    
-    private static void insertRestaurants(int id, String restName, String cityName)
-    {
-        try
-        {
-            stmt = conn.createStatement();
-            stmt.execute("insert into " + tableName + " values (" +
-                    id + ",'" + restName + "','" + cityName +"')");
-            stmt.close();
-        }
-        catch (SQLException sqlExcept)
-        {
-            sqlExcept.printStackTrace();
-        }
-    }
-    
-    private static void selectRestaurants()
-    {
-        try
-        {
-            stmt = conn.createStatement();
-            ResultSet results = stmt.executeQuery("select * from " + tableName);
-            ResultSetMetaData rsmd = results.getMetaData();
-            int numberCols = rsmd.getColumnCount();
-            for (int i=1; i<=numberCols; i++)
-            {
-                //print Column Names
-                System.out.print(rsmd.getColumnLabel(i)+"\t\t");  
-            }
-
-            System.out.println("\n-------------------------------------------------");
-
-            while(results.next())
-            {
-                int id = results.getInt(1);
-                String restName = results.getString(2);
-                String cityName = results.getString(3);
-                System.out.println(id + "\t\t" + restName + "\t\t" + cityName);
-            }
-            results.close();
-            stmt.close();
-        }
-        catch (SQLException sqlExcept)
-        {
-            sqlExcept.printStackTrace();
-        }
-    }
-    
-    private static void shutdown()
-    {
-        try
-        {
-            if (stmt != null)
-            {
-                stmt.close();
-            }
-            if (conn != null)
-            {
-                DriverManager.getConnection(dbURL + ";shutdown=true");
-                conn.close();
-            }           
-        }
-        catch (SQLException sqlExcept)
-        {
-            
-        }
-
-    }
-}
-</pre>
-<p>
-Once Restaurants.java is compiled without errors, run the Java application by
-right-clicking it from the Package Explorer view and selecting <b>Run, Java Application</b>.  
-</p>
-
-<img src="images/run_javaapp.GIF" alt="Running a java application" width="914" height="713"></img>
-
-<p>
-The output from running <b>Restaurants.java</b> is shown below.  It shows the 
-successful insert of a row into our restaurants table and a select of all rows
-in the table.  If you encounter any errors when running the application make
-sure the Derby Network Server has been started on port 1527 and the myDB
-database exists in the current workspace and Java project.
-</p>
-<img src="images/completed_javaapp.GIF" alt="Output from a java application" width="904" height="688"></img>
-
-<h3>Changing the application to use the Derby Embedded Driver</h3>
-<p>
-<b>Restaurants.java</b> accessed the Derby database, <b>myDB</b> using
-the Derby Network Client Driver.  The values for loading the driver and the
-Database connection URL are shown below.
-</p>
-<ul>
-<li>
-<b>
-Driver name <br/>
-</b>
-org.apache.derby.jdbc.ClientDriver
-<br/><br/>
-</li>
-<li>
-<b>
-Database connection URL<br/>
-</b>
-jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine
-<br/><br/>
-</li>
-</ul>
-<p>
-To change the application to use the Derby Embedded Driver we need to change
-these values to:
-</p>
-<ul>
-<li>
-<b>
-Driver name <br/>
-</b>
-org.apache.derby.jdbc.EmbeddedDriver
-<br/><br/>
-</li>
-<li>
-<b>
-Database connection URL<br/>
-</b>
-jdbc:derby:myDB;create=true;user=me;password=mine
-<br/><br/>
-</li>
-</ul>
-
-<h3>About Schema Names</h3>
-<p>
-If a database is created in Derby using the embedded driver and no user
-name is specified, the default schema used becomes <b>APP</b>.  Therefore
-any tables created in the database have a schema name of <b>APP</b>.
-However, when creating a Derby database using the Network Server, the value
-for the schema becomes the value of the username used to connect with as
-part of the database URL.  In our example we first created the <b>myDB</b> 
-database using the user <b>me</b>.
-</p>
-<p>
-When we change the application to connect using the embedded driver, the 
-schema will default to <b>APP</b> unless we explicitly specify a schema, 
-or pass the username as part of the Database connection URL. To access the 
-table without passing the username as part of the embedded driver Database 
-URL we would refer to the table as <b>ME.restaurants</b>.
-</p>
-<p>
-Only two lines of code need to be changed in Restaurants.java to use the
-Derby Embedded Driver to access the myDB database and insert and select into
-the me.restaurants table.  The old values are listed below.
-</p>
-<pre>
-// variables
-private static String dbURL = "jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine";
-
-// from the createConnection method
-Class.forName("org.apache.derby.jdbc.ClientDriver").newInstance();
-</pre>
-<p>
-The new values are shown below to use the Embedded Driver.
-</p>
-<pre>
-// variables
-private static String dbURL = "jdbc:derby:myDB;create=true;user=me;password=mine";
-
-// from the createConnection method
-Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
-</pre>
-
-<p>
-Comment out the old values and replace them with the new ones shown above.
-Recompile the class and if your Derby Network Server is running stop it before
-running the Java application with the Embedded Driver.  
-</p>
-<p>
-Applications which use the Derby Embedded Driver may only access the database 
-from the same JVM.  Applications which use the Derby Network Server can 
-access the database from other JVM's.
-</p>
-<p>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Creating a Java application to access a Derby database</title>
+</head>
+<body>
+<h2>Creating a Java application to access a Derby database</h2>
+<p>
+Once you've become familiar with starting the network server and running
+SQL queries, you'll want to use Derby from within a Java application.
+This section will demonstrate using Derby from a stand-alone Java
+application.
+</p>
+<p>
+This example will access the data in our sample database, <b>myDB</b>, 
+which contains the restaurants table.  By following the two <a href="ij_toc.html"><b>ij</b></a> sections in the help, this database and table will have already
+been created and ready to use.  If you have not created the database and the table return to the <a href="ij_toc.html"><b>ij</b></a> sections and create them now.
+</p>
+<h3>Steps to create a stand-alone Java application</h3>
+<ul>
+<li>
+From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
+<b>New, Class</b>.
+</li>
+</ul>
+</p>
+<img src="images/new_class.GIF" alt="Creating a Java class in Eclipse" width="914" height="638"></img>
+<p>
+Give the Java class a package name, <b>myapp</b>, name the class 
+<b>Restaurants</b>, make it a public class, and include a main method 
+in the class since this will be a stand-alone application.  The image 
+below shows an example of this. 
+Click <b>Finish</b> to create the class.
+</p>
+<img src="images/create_class.GIF" alt="New Java class wizard" width="515" height="566"></img>
+
+<p>
+The Java class shown below, <b>Restaurants.java</b>, connects to the Derby Network Server, inserts a row into the restaurants table, and then displays a select
+from the restaurants table.  Copy the code below into the Java editor window
+for the <b>Restaurants.java</b> class you just created. 
+</p>
+
+<pre>
+package myapp;
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.sql.ResultSetMetaData;
+
+
+public class Restaurants
+{
+    private static String dbURL = "jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine";
+    private static String tableName = "restaurants";
+    // jdbc Connection
+    private static Connection conn = null;
+    private static Statement stmt = null;
+
+    public static void main(String[] args)
+    {
+        createConnection();
+        insertRestaurants(5, "LaVals", "Berkeley");
+        selectRestaurants();
+        shutdown();
+    }
+    
+    private static void createConnection()
+    {
+        try
+        {
+            Class.forName("org.apache.derby.jdbc.ClientDriver").newInstance();
+            //Get a connection
+            conn = DriverManager.getConnection(dbURL); 
+        }
+        catch (Exception except)
+        {
+            except.printStackTrace();
+        }
+    }
+    
+    private static void insertRestaurants(int id, String restName, String cityName)
+    {
+        try
+        {
+            stmt = conn.createStatement();
+            stmt.execute("insert into " + tableName + " values (" +
+                    id + ",'" + restName + "','" + cityName +"')");
+            stmt.close();
+        }
+        catch (SQLException sqlExcept)
+        {
+            sqlExcept.printStackTrace();
+        }
+    }
+    
+    private static void selectRestaurants()
+    {
+        try
+        {
+            stmt = conn.createStatement();
+            ResultSet results = stmt.executeQuery("select * from " + tableName);
+            ResultSetMetaData rsmd = results.getMetaData();
+            int numberCols = rsmd.getColumnCount();
+            for (int i=1; i<=numberCols; i++)
+            {
+                //print Column Names
+                System.out.print(rsmd.getColumnLabel(i)+"\t\t");  
+            }
+
+            System.out.println("\n-------------------------------------------------");
+
+            while(results.next())
+            {
+                int id = results.getInt(1);
+                String restName = results.getString(2);
+                String cityName = results.getString(3);
+                System.out.println(id + "\t\t" + restName + "\t\t" + cityName);
+            }
+            results.close();
+            stmt.close();
+        }
+        catch (SQLException sqlExcept)
+        {
+            sqlExcept.printStackTrace();
+        }
+    }
+    
+    private static void shutdown()
+    {
+        try
+        {
+            if (stmt != null)
+            {
+                stmt.close();
+            }
+            if (conn != null)
+            {
+                DriverManager.getConnection(dbURL + ";shutdown=true");
+                conn.close();
+            }           
+        }
+        catch (SQLException sqlExcept)
+        {
+            
+        }
+
+    }
+}
+</pre>
+<p>
+Once Restaurants.java is compiled without errors, run the Java application by
+right-clicking it from the Package Explorer view and selecting <b>Run, Java Application</b>.  
+</p>
+
+<img src="images/run_javaapp.GIF" alt="Running a java application" width="914" height="713"></img>
+
+<p>
+The output from running <b>Restaurants.java</b> is shown below.  It shows the 
+successful insert of a row into our restaurants table and a select of all rows
+in the table.  If you encounter any errors when running the application make
+sure the Derby Network Server has been started on port 1527 and the myDB
+database exists in the current workspace and Java project.
+</p>
+<img src="images/completed_javaapp.GIF" alt="Output from a java application" width="904" height="688"></img>
+
+<h3>Changing the application to use the Derby Embedded Driver</h3>
+<p>
+<b>Restaurants.java</b> accessed the Derby database, <b>myDB</b> using
+the Derby Network Client Driver.  The values for loading the driver and the
+Database connection URL are shown below.
+</p>
+<ul>
+<li>
+<b>
+Driver name <br/>
+</b>
+org.apache.derby.jdbc.ClientDriver
+<br/><br/>
+</li>
+<li>
+<b>
+Database connection URL<br/>
+</b>
+jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine
+<br/><br/>
+</li>
+</ul>
+<p>
+To change the application to use the Derby Embedded Driver we need to change
+these values to:
+</p>
+<ul>
+<li>
+<b>
+Driver name <br/>
+</b>
+org.apache.derby.jdbc.EmbeddedDriver
+<br/><br/>
+</li>
+<li>
+<b>
+Database connection URL<br/>
+</b>
+jdbc:derby:myDB;create=true;user=me;password=mine
+<br/><br/>
+</li>
+</ul>
+
+<h3>About Schema Names</h3>
+<p>
+If a database is created in Derby using the embedded driver and no user
+name is specified, the default schema used becomes <b>APP</b>.  Therefore
+any tables created in the database have a schema name of <b>APP</b>.
+However, when creating a Derby database using the Network Server, the value
+for the schema becomes the value of the username used to connect with as
+part of the database URL.  In our example we first created the <b>myDB</b> 
+database using the user <b>me</b>.
+</p>
+<p>
+When we change the application to connect using the embedded driver, the 
+schema will default to <b>APP</b> unless we explicitly specify a schema, 
+or pass the username as part of the Database connection URL. To access the 
+table without passing the username as part of the embedded driver Database 
+URL we would refer to the table as <b>ME.restaurants</b>.
+</p>
+<p>
+Only two lines of code need to be changed in Restaurants.java to use the
+Derby Embedded Driver to access the myDB database and insert and select into
+the me.restaurants table.  The old values are listed below.
+</p>
+<pre>
+// variables
+private static String dbURL = "jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine";
+
+// from the createConnection method
+Class.forName("org.apache.derby.jdbc.ClientDriver").newInstance();
+</pre>
+<p>
+The new values are shown below to use the Embedded Driver.
+</p>
+<pre>
+// variables
+private static String dbURL = "jdbc:derby:myDB;create=true;user=me;password=mine";
+
+// from the createConnection method
+Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
+</pre>
+
+<p>
+Comment out the old values and replace them with the new ones shown above.
+Recompile the class and if your Derby Network Server is running stop it before
+running the Java application with the Embedded Driver.  
+</p>
+<p>
+Applications which use the Derby Embedded Driver may only access the database 
+from the same JVM.  Applications which use the Derby Network Server can 
+access the database from other JVM's.
+</p>
+<p>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/derby_app.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij.html Fri Oct 28 04:51:50 2005
@@ -1,91 +1,91 @@
-<html>
-<head>
-<title>Using ij to issue SQL commands</title>
-</head>
-<body>
-<h2>Using ij to issue SQL commands</h2>
-<p>
-<b>ij</b>, the interactive SQL scripting tool provided with Derby, allows
-you to issue ad-hoc queries against a Derby database.  Running <b>ij</b> from
-within Eclipse speeds application development by testing and running SQL 
-statements prior to coding JDBC calls.
-</p>
-<h3>To launch <b>ij</b>:</h3>
-<ul>
-<li>
-Select the project and bring up the context menu. Select the menu item, <b>Apache Derby, ij (Interactive SQL)</b>.
-</li>
-</ul>
-<blockquote>
-<img src="images/start_ij.GIF" width="782" height="682" alt="ij menu item"></img>
-</blockquote>
-<ul>
-<li>
-The <b>Console</b> view will show the <b>ij</b> prompt.  
-For this example we assume the Derby Network Server has been started; if you 
-haven't started it, go ahead and start it up now.
-<br/><br/>
-</li>
-<li>
-The first step to using Derby is to connect to the database using a database
-JDBC connection URL.  <br/>
-The database connection URL we'll use for this example will connect to our
-Network Server using the Derby Network Client driver on the localhost.  We'll
-create a database called <b>myDB</b> as the user 'me' with a password of 'mine.'
-<br/>
-<br/>
-To connect to the database from <b>ij</b> we need to issue the <b>connect</b>
-command, so the entire command to connect to our database looks like this:
-<pre>
-connect 'jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine';
-</pre>
-</li>
-<li>
-Cut and paste the above connection URL into the <b>ij</b> console window.  
-It should create a database in the current workspace, under the current Java
-project, called <b>myDB</b>.
-<br/><br/>
-</li>
-<li>
-We'll also create a table in our myDB database, insert some rows and select
-all rows from the table.  Here is the SQL to do this:  
-<pre>
-create table restaurants(id integer, name varchar(20), city varchar(50));
-insert into restaurants values (1, 'Irifunes', 'San Mateo');
-insert into restaurants values (2, 'Estradas', 'Daly City');
-insert into restaurants values (3, 'Prime Rib House', 'San Francisco');
-select * from restaurants;
-</pre>
-</li>
-<li>
-Cut and paste this SQL (one line at a time) into the <b>ij</b> console window.
-</li>
-</ul>
-</p> 
-<blockquote>
-Sample output from our <b>ij</b> session which runs the sql commands listed above is shown below.
-</blockquote>
-
-<blockquote>
-<img src="images/ij_commands.GIF" width="926" height="603" alt="ij console output"></img>
-</blockquote>
-
-<p>
-The database connection URL shown above is used to connect to the Derby Network Server.  If you want to connect to the database using the Derby JDBC embedded 
-driver the connection URL would look like <b>jdbc:derby:myDB;create=true</b>
-and the ij command would be this:
-<pre>
-connect 'jdbc:derby:myDB;create=true';
-</pre>
-</p>
-<p>
-For detailed information on the proper syntax to use for the Connection URL 
-refer to the Derby <i>Tools &amp; Utility
-Guide</i>. The section called <b>Getting started with ij</b> provides the
-necessary information to start using ij.
-</p>
-<p>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Using ij to issue SQL commands</title>
+</head>
+<body>
+<h2>Using ij to issue SQL commands</h2>
+<p>
+<b>ij</b>, the interactive SQL scripting tool provided with Derby, allows
+you to issue ad-hoc queries against a Derby database.  Running <b>ij</b> from
+within Eclipse speeds application development by testing and running SQL 
+statements prior to coding JDBC calls.
+</p>
+<h3>To launch <b>ij</b>:</h3>
+<ul>
+<li>
+Select the project and bring up the context menu. Select the menu item, <b>Apache Derby, ij (Interactive SQL)</b>.
+</li>
+</ul>
+<blockquote>
+<img src="images/start_ij.GIF" width="782" height="682" alt="ij menu item"></img>
+</blockquote>
+<ul>
+<li>
+The <b>Console</b> view will show the <b>ij</b> prompt.  
+For this example we assume the Derby Network Server has been started; if you 
+haven't started it, go ahead and start it up now.
+<br/><br/>
+</li>
+<li>
+The first step to using Derby is to connect to the database using a database
+JDBC connection URL.  <br/>
+The database connection URL we'll use for this example will connect to our
+Network Server using the Derby Network Client driver on the localhost.  We'll
+create a database called <b>myDB</b> as the user 'me' with a password of 'mine.'
+<br/>
+<br/>
+To connect to the database from <b>ij</b> we need to issue the <b>connect</b>
+command, so the entire command to connect to our database looks like this:
+<pre>
+connect 'jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine';
+</pre>
+</li>
+<li>
+Cut and paste the above connection URL into the <b>ij</b> console window.  
+It should create a database in the current workspace, under the current Java
+project, called <b>myDB</b>.
+<br/><br/>
+</li>
+<li>
+We'll also create a table in our myDB database, insert some rows and select
+all rows from the table.  Here is the SQL to do this:  
+<pre>
+create table restaurants(id integer, name varchar(20), city varchar(50));
+insert into restaurants values (1, 'Irifunes', 'San Mateo');
+insert into restaurants values (2, 'Estradas', 'Daly City');
+insert into restaurants values (3, 'Prime Rib House', 'San Francisco');
+select * from restaurants;
+</pre>
+</li>
+<li>
+Cut and paste this SQL (one line at a time) into the <b>ij</b> console window.
+</li>
+</ul>
+</p> 
+<blockquote>
+Sample output from our <b>ij</b> session which runs the sql commands listed above is shown below.
+</blockquote>
+
+<blockquote>
+<img src="images/ij_commands.GIF" width="926" height="603" alt="ij console output"></img>
+</blockquote>
+
+<p>
+The database connection URL shown above is used to connect to the Derby Network Server.  If you want to connect to the database using the Derby JDBC embedded 
+driver the connection URL would look like <b>jdbc:derby:myDB;create=true</b>
+and the ij command would be this:
+<pre>
+connect 'jdbc:derby:myDB;create=true';
+</pre>
+</p>
+<p>
+For detailed information on the proper syntax to use for the Connection URL 
+refer to the Derby <i>Tools &amp; Utility
+Guide</i>. The section called <b>Getting started with ij</b> provides the
+necessary information to start using ij.
+</p>
+<p>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij2.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij2.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij2.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij2.html Fri Oct 28 04:51:50 2005
@@ -1,95 +1,95 @@
-<html>
-<head>
-<title>Using ij to run SQL scripts</title>
-</head>
-<body>
-<h2>Using ij to run SQL scripts</h2>
-<p>
-<b>ij</b> scripts, files that end in an .sql extension and contain SQL
-commands, can be run using the Derby plug-ins.
-This allows you to use SQL scripts containing multiple commands
-and run them in a single execution of <b>ij</b>.
-</p>
-<h3>Follow these steps to run an SQL script:</h3>
-<ul>
-<li>
-Create a script which contains SQL commands and save the file with a .sql
-extension.  Remember to make the database connection your first command 
-in the script - no default connection exists. 
-<br/><br/>
-</li>
-<li>
-Save the file in your current workspace, under your Java project, or import
-it into your workspace.
-<br/><br/>
-</li>
-<li>
-Run the script using the menu item <b>Apache Derby, Run SQL script using 'ij'</b>
-<br/><br/>
-</li>
-<li>
-The output appears in the <b>ij</b> console window.
-<br/><br/>
-</li>
-</ul>
-<h3>Example of creating and running an SQL script</h3>
-<p>
-We'll go through a complete example below with an sql file called
-<b>restaurants.sql</b>.  This script relies on a table we created in the
-help section, <a href="ij.html">Use ij to issue SQL commands.</a>  
-Run that SQL prior to completing these steps.
-</p>
-<p>
-From the main Eclipse menu select <b>File, New, File</b>.
-</p>
-<blockquote>
-<img src="images/create_file.GIF" alt="Creating a new file in Eclipse" width="841" height="574"></img>
-</blockquote>
-<p>
-Use the current Java project as the parent folder, for example, myJavaProject.
-Name the file <b>restaurants.sql</b>, and click <b>Finish</b>.
-</p>
-<p>
-Now the workspace will look like this.
-</p>
-<blockquote>
-<img src="images/create_restaurant.GIF" alt="Adding an sql file to the Java project" width="899" height="609"></img>
-</blockquote>
-<p>
-Type the following in the restaurants.sql editor window (you may need to
-double click the restaurants.sql file to create an editor window to type in.)
-</p>
-<pre>
-connect 'jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine;';
-insert into restaurants values (4, 'Grande Burrito', 'Oakland');
-update restaurants set city = 'Ukiah' where name = 'Irifunes';
-select * from restaurants;
-disconnect;
-exit;
-</pre>
-<p>
-Now save the restaurants.sql file so we can run the script.  Use <b>Ctrl + S</b>
-in the windows environment to save an open file.  Once the file has been saved
-the asterisk will disappear next to the name of the file in the editor.
-</p>
-<p>
-The last step is to run the SQL script.  Right-click the <b>restaurants.sql</b> 
-file in the <b>Package Explorer</b> view and select <b>Apache Derby, Run SQL 
-Script using 'ij'</b>.
-</p>
-<blockquote>
-<img src="images/restaurant_editor.GIF" alt="Run SQL Script using 'ij'" width="910" height="663"></img>
-</blockquote>
-<p>
-The <b>Console</b> view shows the SQL commands contained in the file
-and executing in <b>ij</b> along with the output of the commands.  
-</p>
-
-<blockquote>
-<img src="images/restaurant_script.GIF" alt="Console view of ij script output" width="910" height="663"></img>
-</blockquote>
-<p>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Using ij to run SQL scripts</title>
+</head>
+<body>
+<h2>Using ij to run SQL scripts</h2>
+<p>
+<b>ij</b> scripts, files that end in an .sql extension and contain SQL
+commands, can be run using the Derby plug-ins.
+This allows you to use SQL scripts containing multiple commands
+and run them in a single execution of <b>ij</b>.
+</p>
+<h3>Follow these steps to run an SQL script:</h3>
+<ul>
+<li>
+Create a script which contains SQL commands and save the file with a .sql
+extension.  Remember to make the database connection your first command 
+in the script - no default connection exists. 
+<br/><br/>
+</li>
+<li>
+Save the file in your current workspace, under your Java project, or import
+it into your workspace.
+<br/><br/>
+</li>
+<li>
+Run the script using the menu item <b>Apache Derby, Run SQL script using 'ij'</b>
+<br/><br/>
+</li>
+<li>
+The output appears in the <b>ij</b> console window.
+<br/><br/>
+</li>
+</ul>
+<h3>Example of creating and running an SQL script</h3>
+<p>
+We'll go through a complete example below with an sql file called
+<b>restaurants.sql</b>.  This script relies on a table we created in the
+help section, <a href="ij.html">Use ij to issue SQL commands.</a>  
+Run that SQL prior to completing these steps.
+</p>
+<p>
+From the main Eclipse menu select <b>File, New, File</b>.
+</p>
+<blockquote>
+<img src="images/create_file.GIF" alt="Creating a new file in Eclipse" width="841" height="574"></img>
+</blockquote>
+<p>
+Use the current Java project as the parent folder, for example, myJavaProject.
+Name the file <b>restaurants.sql</b>, and click <b>Finish</b>.
+</p>
+<p>
+Now the workspace will look like this.
+</p>
+<blockquote>
+<img src="images/create_restaurant.GIF" alt="Adding an sql file to the Java project" width="899" height="609"></img>
+</blockquote>
+<p>
+Type the following in the restaurants.sql editor window (you may need to
+double click the restaurants.sql file to create an editor window to type in.)
+</p>
+<pre>
+connect 'jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine;';
+insert into restaurants values (4, 'Grande Burrito', 'Oakland');
+update restaurants set city = 'Ukiah' where name = 'Irifunes';
+select * from restaurants;
+disconnect;
+exit;
+</pre>
+<p>
+Now save the restaurants.sql file so we can run the script.  Use <b>Ctrl + S</b>
+in the windows environment to save an open file.  Once the file has been saved
+the asterisk will disappear next to the name of the file in the editor.
+</p>
+<p>
+The last step is to run the SQL script.  Right-click the <b>restaurants.sql</b> 
+file in the <b>Package Explorer</b> view and select <b>Apache Derby, Run SQL 
+Script using 'ij'</b>.
+</p>
+<blockquote>
+<img src="images/restaurant_editor.GIF" alt="Run SQL Script using 'ij'" width="910" height="663"></img>
+</blockquote>
+<p>
+The <b>Console</b> view shows the SQL commands contained in the file
+and executing in <b>ij</b> along with the output of the commands.  
+</p>
+
+<blockquote>
+<img src="images/restaurant_script.GIF" alt="Console view of ij script output" width="910" height="663"></img>
+</blockquote>
+<p>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij2.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij_toc.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij_toc.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij_toc.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij_toc.html Fri Oct 28 04:51:50 2005
@@ -1,24 +1,24 @@
-<html>
-<head>
-<title>Using ij</title>
-</head>
-<body>
-<h2>Using ij</h2>
-<p>
-To issue SQL commands against a Derby database, use <b>ij</b>, the SQL 
-scripting tool. 
-</p>
-<p>
-<h3><a href="ij.html">Using ij to issue SQL commands</a></h3>
-</p>
-<p>
-ij, the interactive SQL scripting tool, can be run via the Eclipse console.
-</p>
-<p>
-<h3><a href="ij2.html">Using ij to run SQL scripts</a></h3>
-</p>
-<p>
-Entire SQL scripts can be executed using ij.
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Using ij</title>
+</head>
+<body>
+<h2>Using ij</h2>
+<p>
+To issue SQL commands against a Derby database, use <b>ij</b>, the SQL 
+scripting tool. 
+</p>
+<p>
+<h3><a href="ij.html">Using ij to issue SQL commands</a></h3>
+</p>
+<p>
+ij, the interactive SQL scripting tool, can be run via the Eclipse console.
+</p>
+<p>
+<h3><a href="ij2.html">Using ij to run SQL scripts</a></h3>
+</p>
+<p>
+Entire SQL scripts can be executed using ij.
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/ij_toc.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/java_project.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/java_project.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/java_project.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/java_project.html Fri Oct 28 04:51:50 2005
@@ -1,53 +1,53 @@
-<html>
-<head>
-<title>Creating an Eclipse Java project</title>
-</head>
-<body>
-<h2>Creating an Eclipse Java project</h2>
-<p>
-The steps below outline how to create a Java project using many of the default
-settings to make it easy to get started.
-</p>
-<p>
-<ul>
-<li>
-From the main workbench window, click File > New > Project. The New Project 
-wizard opens. <br/><br/>
-</li>
-<li>
-Select Java Project and click Next.<br/><br/>
-</li>
-<li>
-In the Project name field, type a name for your new Java project, like 
-myJavaProject. <br/><br/>
-</li>
-<li>
-For Location, choose <b>Create project in workspace</b> and for the Project
-Layout, select <b>Use project folder as root for sources and class files</b>.
-<br/>
-<br/>
-</li>
-<li>
-Click the Next button, then Finish.
-<br/>
-<br/>
-</li>
-
-<li>
-You may be prompted about switching to the Java Perspective.  Answer Yes to 
-this question.
-<br/>
-<br/>
-</li>
-
-<li>
-The Package Explorer view now shows your new Java project.
-<br/>
-<br/>
-</li>
-</ul>
-
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Creating an Eclipse Java project</title>
+</head>
+<body>
+<h2>Creating an Eclipse Java project</h2>
+<p>
+The steps below outline how to create a Java project using many of the default
+settings to make it easy to get started.
+</p>
+<p>
+<ul>
+<li>
+From the main workbench window, click File > New > Project. The New Project 
+wizard opens. <br/><br/>
+</li>
+<li>
+Select Java Project and click Next.<br/><br/>
+</li>
+<li>
+In the Project name field, type a name for your new Java project, like 
+myJavaProject. <br/><br/>
+</li>
+<li>
+For Location, choose <b>Create project in workspace</b> and for the Project
+Layout, select <b>Use project folder as root for sources and class files</b>.
+<br/>
+<br/>
+</li>
+<li>
+Click the Next button, then Finish.
+<br/>
+<br/>
+</li>
+
+<li>
+You may be prompted about switching to the Java Perspective.  Answer Yes to 
+this question.
+<br/>
+<br/>
+</li>
+
+<li>
+The Package Explorer view now shows your new Java project.
+<br/>
+<br/>
+</li>
+</ul>
+
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/java_project.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature.html Fri Oct 28 04:51:50 2005
@@ -1,37 +1,37 @@
-<html>
-<head>
-<title>Adding the Derby nature to a Java project</title>
-</head>
-<body>
-<h2>Adding the Derby nature to a Java project</h2>
-<p>
-Once a Java project is created the Derby nature can be added from within 
-the Java perspective.  To add the Derby nature to your project:
-<ul>
-<li>
-From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
-the menu item, <b>Apache Derby, Add Apache Derby nature</b>.
-</li>
-</ul>
-</p>
-<blockquote> 
-<img src="images/add_nature.GIF" alt="Adding the Derby nature to a project" width="720" height="615"></img>
-</blockquote> 
-<p>
-Adding the Derby nature to your Java project does the following:
-<ul>
-<li>
-Adds the <b>derby.jar, derbynet.jar, derbytools.jar, derbyclient.jar</b> jar files to the Java Build Path of the project.<br/><br/>
-</li>
-<li>
-Enables the Derby features for the project.  The <b>ij</b> and <b>sysinfo</b>
-tools are now accessible from the Eclipse menu, and the Apache Derby Network Server can now be started and stopped from within Eclipse. <br/><br/>
-</li>
-<li>
-Allows Apache Derby properties to be set for the project. 
-</li>
-</ul>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Adding the Derby nature to a Java project</title>
+</head>
+<body>
+<h2>Adding the Derby nature to a Java project</h2>
+<p>
+Once a Java project is created the Derby nature can be added from within 
+the Java perspective.  To add the Derby nature to your project:
+<ul>
+<li>
+From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
+the menu item, <b>Apache Derby, Add Apache Derby nature</b>.
+</li>
+</ul>
+</p>
+<blockquote> 
+<img src="images/add_nature.GIF" alt="Adding the Derby nature to a project" width="720" height="615"></img>
+</blockquote> 
+<p>
+Adding the Derby nature to your Java project does the following:
+<ul>
+<li>
+Adds the <b>derby.jar, derbynet.jar, derbytools.jar, derbyclient.jar</b> jar files to the Java Build Path of the project.<br/><br/>
+</li>
+<li>
+Enables the Derby features for the project.  The <b>ij</b> and <b>sysinfo</b>
+tools are now accessible from the Eclipse menu, and the Apache Derby Network Server can now be started and stopped from within Eclipse. <br/><br/>
+</li>
+<li>
+Allows Apache Derby properties to be set for the project. 
+</li>
+</ul>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature_toc.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature_toc.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature_toc.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature_toc.html Fri Oct 28 04:51:50 2005
@@ -1,31 +1,31 @@
-<html>
-<head>
-<title>The Derby Nature</title>
-</head>
-<body>
-<h2>The Derby Nature</h2>
-<p>
-Enabling a nature for a project allows a plug-in to give a project a 
-personality or characteristics it desires.  By adding the Derby Nature
-to a specific project you are enabling the Derby features for that project.
-</p>
-<p>
-<h3><a href="nature.html">Adding the Derby nature to a Java project</a></h3>  
-</p>
-<p>
-The Derby jar files are added to the Java project and the project class path 
-is automatically updated to include these jar files.  All Derby features, 
-like starting and stopping the Network Server, and running <b>ij</b> 
-and <b>sysinfo</b> are enabled for the project.
-</p>
-<p>
-<h3><a href="remove_nature.html">Removing the Derby nature from a Java project</a></h3>
-</p>
-<p>
-All Derby jar files are removed from the project and all Derby 
-features are disabled for the Java project.
-</p>
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>The Derby Nature</title>
+</head>
+<body>
+<h2>The Derby Nature</h2>
+<p>
+Enabling a nature for a project allows a plug-in to give a project a 
+personality or characteristics it desires.  By adding the Derby Nature
+to a specific project you are enabling the Derby features for that project.
+</p>
+<p>
+<h3><a href="nature.html">Adding the Derby nature to a Java project</a></h3>  
+</p>
+<p>
+The Derby jar files are added to the Java project and the project class path 
+is automatically updated to include these jar files.  All Derby features, 
+like starting and stopping the Network Server, and running <b>ij</b> 
+and <b>sysinfo</b> are enabled for the project.
+</p>
+<p>
+<h3><a href="remove_nature.html">Removing the Derby nature from a Java project</a></h3>
+</p>
+<p>
+All Derby jar files are removed from the project and all Derby 
+features are disabled for the Java project.
+</p>
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/nature_toc.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/properties.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/properties.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/properties.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/properties.html Fri Oct 28 04:51:50 2005
@@ -1,126 +1,126 @@
-<html>
-<head>
-<title>Setting Derby properties for a project</title>
-</head>
-<body>
-<h2>Setting Derby properties for a project</h2>
-<p>
-Properties relating to Apache Derby can be specified for any project 
-which has had the Apache Derby nature added to it.  The two categories
-of properties available to change are the Network Server and Derby System
-properties.
-</p>
-<p>
-<b>Network Server Properties</b>
-</p>
-<p>
-By starting the Derby Network Server using the default values the 
-server runs on the localhost, which is the host running Eclipse, 
-on port 1527. 
-</p>
-<p>
-The value used for the Network Server host name impacts the ability of 
-remote hosts to connect to the Network Server.  If the Network Server 
-Host value in the Apache Derby Properties for the project is set to 
-<b>localhost</b>, only clients running on the host where Eclipse is 
-running can connect to the network server.  If an ip address or hostname 
-(other than the name 'localhost')
-is used, client applications running on other hosts can connect to the 
-Derby Network Server.  For additional information about starting the Derby 
-Network Server see the <i>Derby Server and Administration Guide</i>.  
-The section called <b>Starting the Network Server</b> explains the effect 
-of setting the value for the hostname differently.
-</p>
-<p>
-If connections from other hosts is allowed, it is recommended to run
-under the Java security manager and enable user authentication prior to
-starting the Derby Network Server.
-</p>
-<b>Network Server Settings</b>
-<p>
-<ul>
-<li>
-Network Server Port - default value of 1527<br/><br/>
-Valid values for this field are:
-<ul>
-<li>
-Any port number not currently used by another process to listen on
-<br/><br/>
-</li>
-</ul>
-</li>
-<li>
-Network Server Host - default value of localhost <br/><br/>
-Valid values for this field are:
-<ul>
-<li>
-localhost
-</li>
-<li>
-The ip address of the host running Eclipse
-</li>
-<li>
-The host name of the host running Eclipse
-</li>
-<li>
-The ip address of 0.0.0.0 (to listen on all interfaces)
-</li>
-</ul>
-</li>
-</ul>
-</p>
-
-
-<p>
-<b>Derby System Properties</b>
-</p>
-<p>
-<b>derby.system.home</b> refers to the file system directory where the
-Derby database system will look for databases when Derby is started. 
-Setting this property allows for ease of use when specifiying a JDBC 
-connection URL to a Derby database which is not in the current directory. 
-For additional information on <b>derby.system.home</b> refer to the <i>Tuning Derby</i> guide.
-</p>
-<p>
-<b>Derby System Property values</b>
-</p>
-<ul>
-<li>
-derby.system.home - default value of '.', the current project directory<br/><br/>
-Valid values for this field are:
-<ul>
-<li>A directory path on the local host. Either an existing directory or a new
-one which has not yet been created. 
-</li>
-</ul>
-</li>
-</ul>
-</p>
-<h3>Changing the default Apache Derby properties for a project</h3>
-<p>
-<ul>
-<li>
-With the Java project active in the <b>Package Explorer</b> or <b>Navigator</b>
-view, select the menu item <b>Project, Properties</b>.
-</li>
-</ul>
-</p>
-<blockquote>
-<img src="images/properties.gif" alt="Project Properties" width="736" height="619"></img>
-</blockquote>
-
-<ul>
-<li>
-The list of properties available to modify for the project appears.  Select
-the <b>Apache Derby</b> item in the list. <br/><br/>
-</li>
-<li>
-Make any of the desired changes to the Apache Derby settings.  
-</li>
-</ul>
-</p>
-<blockquote>
-<img src="images/property_sheet.GIF" alt="Apache Derby project properties" width="690" height="539"></img>
-</blockquote>
-<p>
-</p>
+<html>
+<head>
+<title>Setting Derby properties for a project</title>
+</head>
+<body>
+<h2>Setting Derby properties for a project</h2>
+<p>
+Properties relating to Apache Derby can be specified for any project 
+which has had the Apache Derby nature added to it.  The two categories
+of properties available to change are the Network Server and Derby System
+properties.
+</p>
+<p>
+<b>Network Server Properties</b>
+</p>
+<p>
+By starting the Derby Network Server using the default values the 
+server runs on the localhost, which is the host running Eclipse, 
+on port 1527. 
+</p>
+<p>
+The value used for the Network Server host name impacts the ability of 
+remote hosts to connect to the Network Server.  If the Network Server 
+Host value in the Apache Derby Properties for the project is set to 
+<b>localhost</b>, only clients running on the host where Eclipse is 
+running can connect to the network server.  If an ip address or hostname 
+(other than the name 'localhost')
+is used, client applications running on other hosts can connect to the 
+Derby Network Server.  For additional information about starting the Derby 
+Network Server see the <i>Derby Server and Administration Guide</i>.  
+The section called <b>Starting the Network Server</b> explains the effect 
+of setting the value for the hostname differently.
+</p>
+<p>
+If connections from other hosts is allowed, it is recommended to run
+under the Java security manager and enable user authentication prior to
+starting the Derby Network Server.
+</p>
+<b>Network Server Settings</b>
+<p>
+<ul>
+<li>
+Network Server Port - default value of 1527<br/><br/>
+Valid values for this field are:
+<ul>
+<li>
+Any port number not currently used by another process to listen on
+<br/><br/>
+</li>
+</ul>
+</li>
+<li>
+Network Server Host - default value of localhost <br/><br/>
+Valid values for this field are:
+<ul>
+<li>
+localhost
+</li>
+<li>
+The ip address of the host running Eclipse
+</li>
+<li>
+The host name of the host running Eclipse
+</li>
+<li>
+The ip address of 0.0.0.0 (to listen on all interfaces)
+</li>
+</ul>
+</li>
+</ul>
+</p>
+
+
+<p>
+<b>Derby System Properties</b>
+</p>
+<p>
+<b>derby.system.home</b> refers to the file system directory where the
+Derby database system will look for databases when Derby is started. 
+Setting this property allows for ease of use when specifiying a JDBC 
+connection URL to a Derby database which is not in the current directory. 
+For additional information on <b>derby.system.home</b> refer to the <i>Tuning Derby</i> guide.
+</p>
+<p>
+<b>Derby System Property values</b>
+</p>
+<ul>
+<li>
+derby.system.home - default value of '.', the current project directory<br/><br/>
+Valid values for this field are:
+<ul>
+<li>A directory path on the local host. Either an existing directory or a new
+one which has not yet been created. 
+</li>
+</ul>
+</li>
+</ul>
+</p>
+<h3>Changing the default Apache Derby properties for a project</h3>
+<p>
+<ul>
+<li>
+With the Java project active in the <b>Package Explorer</b> or <b>Navigator</b>
+view, select the menu item <b>Project, Properties</b>.
+</li>
+</ul>
+</p>
+<blockquote>
+<img src="images/properties.gif" alt="Project Properties" width="736" height="619"></img>
+</blockquote>
+
+<ul>
+<li>
+The list of properties available to modify for the project appears.  Select
+the <b>Apache Derby</b> item in the list. <br/><br/>
+</li>
+<li>
+Make any of the desired changes to the Apache Derby settings.  
+</li>
+</ul>
+</p>
+<blockquote>
+<img src="images/property_sheet.GIF" alt="Apache Derby project properties" width="690" height="539"></img>
+</blockquote>
+<p>
+</p>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/properties.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/remove_nature.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/remove_nature.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/remove_nature.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/remove_nature.html Fri Oct 28 04:51:50 2005
@@ -1,37 +1,37 @@
-<html>
-<head>
-<title>Removing the Derby nature from a Java project</title>
-</head>
-<body>
-<h2>Removing the Derby nature from a Java project</h2>
-<p>
-The Derby nature can be removed from a Java project from within the Java
-perspective.  To remove the Derby nature:
-<ul>
-<li>
-From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
-the menu item, <b>Apache Derby, Remove Apache Derby nature</b>.
-</li>
-</ul>
-</p> 
-<blockquote>
-<img src="images/remove_nature.GIF" alt="Removing the Derby nature from a project" width="713" height="685"></img>
-</blockquote> 
-<p>
-Removing the Derby nature from your Java project does the following:
-<ul>
-<li>
-Removes the <b>derby.jar, derbynet.jar, derbytools.jar, derbyclient.jar</b> jar files from the Java Build Path of the project.<br/><br/>
-</li>
-<li>
-Removes the menu options for <b>ij</b>, <b>sysinfo</b> and starting and stopping
-the Derby Network Server. <br/><br/> 
-</li>
-<li>
-Removes the <b>Apache Derby</b> item from the project's properties.
-</li>
-</ul>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Removing the Derby nature from a Java project</title>
+</head>
+<body>
+<h2>Removing the Derby nature from a Java project</h2>
+<p>
+The Derby nature can be removed from a Java project from within the Java
+perspective.  To remove the Derby nature:
+<ul>
+<li>
+From the <b>Java</b> perspective, select the project in the <b>Package Explorer</b> view. Right-click the project to bring up the context menu and select
+the menu item, <b>Apache Derby, Remove Apache Derby nature</b>.
+</li>
+</ul>
+</p> 
+<blockquote>
+<img src="images/remove_nature.GIF" alt="Removing the Derby nature from a project" width="713" height="685"></img>
+</blockquote> 
+<p>
+Removing the Derby nature from your Java project does the following:
+<ul>
+<li>
+Removes the <b>derby.jar, derbynet.jar, derbytools.jar, derbyclient.jar</b> jar files from the Java Build Path of the project.<br/><br/>
+</li>
+<li>
+Removes the menu options for <b>ij</b>, <b>sysinfo</b> and starting and stopping
+the Derby Network Server. <br/><br/> 
+</li>
+<li>
+Removes the <b>Apache Derby</b> item from the project's properties.
+</li>
+</ul>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/remove_nature.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/resources.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/resources.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/resources.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/resources.html Fri Oct 28 04:51:50 2005
@@ -1,15 +1,15 @@
-<html>
-<head>
-<title>Derby Documentation</title>
-</head>
-<body>
-<h2>Derby Documentation</h2>
-<p>
-Derby documentation can be found on-line at 
-<a href="http://db.apache.org/derby/manuals/index.html" target="_blank">http://db.apache.org/derby/manuals/index.html</a>.  
-<br/><br/>
-</p>
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Derby Documentation</title>
+</head>
+<body>
+<h2>Derby Documentation</h2>
+<p>
+Derby documentation can be found on-line at 
+<a href="http://db.apache.org/derby/manuals/index.html" target="_blank">http://db.apache.org/derby/manuals/index.html</a>.  
+<br/><br/>
+</p>
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/resources.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/server_toc.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/server_toc.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/server_toc.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/server_toc.html Fri Oct 28 04:51:50 2005
@@ -1,31 +1,31 @@
-<html>
-<head>
-<title>Starting and Stopping the Derby Network Server</title>
-</head>
-<body>
-<h2>Starting and Stopping the Derby Network Server</h2>
-<p>
-The Derby Network Server for the host running Eclipse can be started and 
-stopped within Eclipse.  Multiple network servers can be started 
-using this option by changing the port number the Derby Network 
-Server listens on. 
-</p>
-<p>
-<h3><a href="start_server.html">Starting the Derby Network Server</a></h3>
-</p>
-<p>
-Multiple Derby Network Servers can be started on the host running Eclipse 
-using this menu option.  Additionally, the Derby Network Server can be
-started using the ip address of the host running Eclipse to allow remote 
-client access to the network server.
-</p>
-<p>
-<h3><a href="stop_server.html">Stopping the Derby Network Server</a></h3>
-</p>
-<p>
-Any Derby Network Server started from within Eclipse can be stopped using this menu option.
-</p>
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Starting and Stopping the Derby Network Server</title>
+</head>
+<body>
+<h2>Starting and Stopping the Derby Network Server</h2>
+<p>
+The Derby Network Server for the host running Eclipse can be started and 
+stopped within Eclipse.  Multiple network servers can be started 
+using this option by changing the port number the Derby Network 
+Server listens on. 
+</p>
+<p>
+<h3><a href="start_server.html">Starting the Derby Network Server</a></h3>
+</p>
+<p>
+Multiple Derby Network Servers can be started on the host running Eclipse 
+using this menu option.  Additionally, the Derby Network Server can be
+started using the ip address of the host running Eclipse to allow remote 
+client access to the network server.
+</p>
+<p>
+<h3><a href="stop_server.html">Stopping the Derby Network Server</a></h3>
+</p>
+<p>
+Any Derby Network Server started from within Eclipse can be stopped using this menu option.
+</p>
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/server_toc.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_server.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_server.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_server.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_server.html Fri Oct 28 04:51:50 2005
@@ -1,86 +1,86 @@
-<html>
-<head>
-<title>Starting the Derby Network Server</title>
-</head>
-<body>
-<h2>Starting the Derby Network Server</h2>
-<p>
-The Derby Network Server allows multiple applications running in different
-Java Virtual Machines to access a single Derby database.  
-Once the Network Server is started client applications from within Eclipse, 
-such as <b>ij</b> or other Java applications, can access a Derby database.  
-Additionally, the Network Server allows for client applications outside 
-of Eclipse on the localhost, or even on remote hosts to access the same 
-database.
-</p>
-<p>
-<h3>To start the Derby Network Server:</h3>
-</p>
-<p>
-<ul>
-<li>
-The Derby nature needs to be added to the project prior to starting the Network Server.<br/><br/>
-</li>
-<li>
-With the Java project selected, bring up the context menu and select 
-the menu item, <b>Apache Derby, Start Derby Network Server</b>.
-</li>
-</ul>
-<blockquote>
-<img src="images/start_server.GIF" alt="Start Derby Network Server" width="716" height="686"></img> 
-</blockquote>
-<ul>
-<li>
-The pop-up box will appear which states the Apache Derby Network Server is
-attempting to be started.
-</li>
-</ul>
-<ul>
-<li>
-If the network server startup is successful the <b>Console</b> view will
-display <b>Server is ready to accept connections on port xxxx.</b>
-  For each project that has a running Network Server associated with it 
-a green arrow appears next to the project name. 
-</li>
-</ul>
-<blockquote>
-<img src="images/start_server_console.gif" alt="Network Server started" width="746" height="577"></img> 
-</blockquote>
-<ul>
-<li>
-If other items that use the console as a display hide the Network Server
-console use the <b>Display Selected Console</b> drop down icon to the right 
-of the console menu bar to make the Network Server console visible.
-</li>
-</ul>
-</p> 
-
-<h3>Derby Network Server Host value</h3>
-<p>
-By starting the Derby Network Server using the default values the 
-server runs on the localhost, which is the host running Eclipse, 
-on port 1527.  To change the host name or the port number where the Derby 
-Network Server is running see <a href="properties.html"> Setting Derby properties for a project</a>.
-</p>
-<p>
-The value used for the Network Server host name impacts the ability of 
-remote hosts to connect to the Network Server.  If the Network Server Host value
-in the Project Properties is set to <b>localhost</b>, only clients running
-on the host where Eclipse is running can connect to the network server.
-If an ip address or hostname (other than the name 'localhost') is used, 
-client applications running on other hosts can connect to the Derby Network
-Server.  For additional information about starting the Derby Network Server
-see the Derby Server and Administration Guide.  The section
-called <b>Starting the Network Server</b> explains the effect of setting
-the value for the hostname differently.
-</p>
-<p>
-If connections from other hosts will be allowed, it is recommended to run
-under the Java security manager and enable user authentication prior to
-starting the Derby Network Server.
-</p>
-<p>
-</p>
-
-</body>
-</html>
+<html>
+<head>
+<title>Starting the Derby Network Server</title>
+</head>
+<body>
+<h2>Starting the Derby Network Server</h2>
+<p>
+The Derby Network Server allows multiple applications running in different
+Java Virtual Machines to access a single Derby database.  
+Once the Network Server is started client applications from within Eclipse, 
+such as <b>ij</b> or other Java applications, can access a Derby database.  
+Additionally, the Network Server allows for client applications outside 
+of Eclipse on the localhost, or even on remote hosts to access the same 
+database.
+</p>
+<p>
+<h3>To start the Derby Network Server:</h3>
+</p>
+<p>
+<ul>
+<li>
+The Derby nature needs to be added to the project prior to starting the Network Server.<br/><br/>
+</li>
+<li>
+With the Java project selected, bring up the context menu and select 
+the menu item, <b>Apache Derby, Start Derby Network Server</b>.
+</li>
+</ul>
+<blockquote>
+<img src="images/start_server.GIF" alt="Start Derby Network Server" width="716" height="686"></img> 
+</blockquote>
+<ul>
+<li>
+The pop-up box will appear which states the Apache Derby Network Server is
+attempting to be started.
+</li>
+</ul>
+<ul>
+<li>
+If the network server startup is successful the <b>Console</b> view will
+display <b>Server is ready to accept connections on port xxxx.</b>
+  For each project that has a running Network Server associated with it 
+a green arrow appears next to the project name. 
+</li>
+</ul>
+<blockquote>
+<img src="images/start_server_console.gif" alt="Network Server started" width="746" height="577"></img> 
+</blockquote>
+<ul>
+<li>
+If other items that use the console as a display hide the Network Server
+console use the <b>Display Selected Console</b> drop down icon to the right 
+of the console menu bar to make the Network Server console visible.
+</li>
+</ul>
+</p> 
+
+<h3>Derby Network Server Host value</h3>
+<p>
+By starting the Derby Network Server using the default values the 
+server runs on the localhost, which is the host running Eclipse, 
+on port 1527.  To change the host name or the port number where the Derby 
+Network Server is running see <a href="properties.html"> Setting Derby properties for a project</a>.
+</p>
+<p>
+The value used for the Network Server host name impacts the ability of 
+remote hosts to connect to the Network Server.  If the Network Server Host value
+in the Project Properties is set to <b>localhost</b>, only clients running
+on the host where Eclipse is running can connect to the network server.
+If an ip address or hostname (other than the name 'localhost') is used, 
+client applications running on other hosts can connect to the Derby Network
+Server.  For additional information about starting the Derby Network Server
+see the Derby Server and Administration Guide.  The section
+called <b>Starting the Network Server</b> explains the effect of setting
+the value for the hostname differently.
+</p>
+<p>
+If connections from other hosts will be allowed, it is recommended to run
+under the Java security manager and enable user authentication prior to
+starting the Derby Network Server.
+</p>
+<p>
+</p>
+
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_server.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_toc.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_toc.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_toc.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_toc.html Fri Oct 28 04:51:50 2005
@@ -1,72 +1,72 @@
-<html>
-<head>
-<title>Getting Started with the Derby plug-ins for Eclipse</title>
-</head>
-<body>
-<h2>Getting Started with the Derby plug-ins for Eclipse</h2>
-<p>
-The Apache Derby plug-ins for Eclipse provide a seamless integration between 
-Eclipse and Apache Derby. It enables the use of the Derby database JAR files 
-as an installable component to Eclipse. Additionally the ij SQL scripting tool 
-and the Apache Derby Network Server can be run from the Eclipse console.
-</p>
-<p>
-If you are new to Eclipse or Derby, the steps below will get you started 
-using both!  At the very least, follow the first four steps to become familiar
-with Eclipse and Derby.
-<ul>
-<li>
-Create an <a href="java_project.html">Eclipse Java project.</a>
-<br/>
-<br/>
-</li>
-<li>
-Add the <a href="nature.html">Apache Derby nature</a> to your Java project.
-<br/>
-<br/>
-</li>
-<li>
-Start the <a href="start_server.html">Derby Network Server.</a>
-<br/>
-<br/>
-</li>
-<li>
-Launch <a href="ij.html"><b>ij</b></a> to create and connect to a 
-Derby database.  <b>ij</b> is the Derby tool you can use to issue SQL commands 
-against the database.
-<br/>
-<br/>
-</li>
-<li>
-Run entire <a href="ij2.html">SQL scripts</a> against the database using ij.
-<br/>
-<br/>
-</li>
-<li>
-Create a <a href="derby_app.html">Java application</a> which accesses a Derby database.
-<br/>
-<br/>
-</li>
-<li>
-Shutdown the <a href="stop_server.html">Derby Network Server.</a>
-<br/>
-<br/>
-</li>
-<li>
-Obtain Java and Derby information to help in troubleshooting problems using 
-<a href="sysinfo.html">sysinfo.</a>
-<br/>
-<br/>
-</li>
-<li>
-Learn more about Apache Derby from the online <a href="resources.html">documentation.</a>
-<br/>
-<br/>
-</li>
-</ul>
-</p>
-
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Getting Started with the Derby plug-ins for Eclipse</title>
+</head>
+<body>
+<h2>Getting Started with the Derby plug-ins for Eclipse</h2>
+<p>
+The Apache Derby plug-ins for Eclipse provide a seamless integration between 
+Eclipse and Apache Derby. It enables the use of the Derby database JAR files 
+as an installable component to Eclipse. Additionally the ij SQL scripting tool 
+and the Apache Derby Network Server can be run from the Eclipse console.
+</p>
+<p>
+If you are new to Eclipse or Derby, the steps below will get you started 
+using both!  At the very least, follow the first four steps to become familiar
+with Eclipse and Derby.
+<ul>
+<li>
+Create an <a href="java_project.html">Eclipse Java project.</a>
+<br/>
+<br/>
+</li>
+<li>
+Add the <a href="nature.html">Apache Derby nature</a> to your Java project.
+<br/>
+<br/>
+</li>
+<li>
+Start the <a href="start_server.html">Derby Network Server.</a>
+<br/>
+<br/>
+</li>
+<li>
+Launch <a href="ij.html"><b>ij</b></a> to create and connect to a 
+Derby database.  <b>ij</b> is the Derby tool you can use to issue SQL commands 
+against the database.
+<br/>
+<br/>
+</li>
+<li>
+Run entire <a href="ij2.html">SQL scripts</a> against the database using ij.
+<br/>
+<br/>
+</li>
+<li>
+Create a <a href="derby_app.html">Java application</a> which accesses a Derby database.
+<br/>
+<br/>
+</li>
+<li>
+Shutdown the <a href="stop_server.html">Derby Network Server.</a>
+<br/>
+<br/>
+</li>
+<li>
+Obtain Java and Derby information to help in troubleshooting problems using 
+<a href="sysinfo.html">sysinfo.</a>
+<br/>
+<br/>
+</li>
+<li>
+Learn more about Apache Derby from the online <a href="resources.html">documentation.</a>
+<br/>
+<br/>
+</li>
+</ul>
+</p>
+
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/start_toc.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/stop_server.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/stop_server.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/stop_server.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/stop_server.html Fri Oct 28 04:51:50 2005
@@ -1,49 +1,49 @@
-<html>
-<head>
-<title>Stopping the Derby Network Server</title>
-</head>
-<body>
-<h2>Stopping the Derby Network Server</h2>
-<p>
-The Derby Network Server allows multiple applications running in different
-Java Virtual Machines to access a single Derby database.  
-</p>
-<p>
-<h3>To stop the Derby Network Server:</h3>
-</p>
-<ul>
-<li>
-Select the Java project, bring up the context menu and select 
-the menu item, <b>Apache Derby, Stop Derby Network Server</b>.
-</li>
-</ul>
-<blockquote>
-<img src="images/stop_server.GIF" alt="Stop Derby Network Server" width="784" height="676"></img>
-</blockquote>
-<ul>
-<li>
-The pop-up box will appear stating the Apache Derby Network Server is 
-attempting to be stopped.
-</li>
-</ul>
-<ul>
-<li>
-If the network server shutdown is successful the <b>Console</b> view will
-say <b>Shutdown successful.</b>
-</li>
-</ul>
-<blockquote>
-<img src="images/shutdown_success.gif" alt="Apache Derby Network Server stopped" width="773" height="645"></img>
-</blockquote>
-<ul>
-<li>
-When the Network Server associated with a particular project is shutdown 
-the green arrow designating a running server which appeared next to the project
-name, is no longer visible.
-</li>
-</ul>
-
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Stopping the Derby Network Server</title>
+</head>
+<body>
+<h2>Stopping the Derby Network Server</h2>
+<p>
+The Derby Network Server allows multiple applications running in different
+Java Virtual Machines to access a single Derby database.  
+</p>
+<p>
+<h3>To stop the Derby Network Server:</h3>
+</p>
+<ul>
+<li>
+Select the Java project, bring up the context menu and select 
+the menu item, <b>Apache Derby, Stop Derby Network Server</b>.
+</li>
+</ul>
+<blockquote>
+<img src="images/stop_server.GIF" alt="Stop Derby Network Server" width="784" height="676"></img>
+</blockquote>
+<ul>
+<li>
+The pop-up box will appear stating the Apache Derby Network Server is 
+attempting to be stopped.
+</li>
+</ul>
+<ul>
+<li>
+If the network server shutdown is successful the <b>Console</b> view will
+say <b>Shutdown successful.</b>
+</li>
+</ul>
+<blockquote>
+<img src="images/shutdown_success.gif" alt="Apache Derby Network Server stopped" width="773" height="645"></img>
+</blockquote>
+<ul>
+<li>
+When the Network Server associated with a particular project is shutdown 
+the green arrow designating a running server which appeared next to the project
+name, is no longer visible.
+</li>
+</ul>
+
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/stop_server.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/sysinfo.html
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/sysinfo.html?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/sysinfo.html (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/sysinfo.html Fri Oct 28 04:51:50 2005
@@ -1,50 +1,50 @@
-<html>
-<head>
-<title>Running sysinfo for environment information</title>
-</head>
-<body>
-<h2>Running sysinfo for environment information</h2>
-<p>
-<b>sysinfo</b> provides information about the Derby system. This tool is
-useful in determing the current Java and Derby environments.
-</p>
-<h3>To launch <b>sysinfo</b>:</h3>
-<ul>
-<li>
-Select the project and bring up the context menu. Select the menu item, <b>sysinfo (Derby System Information)</b>.
-</li>
-</ul>
-<blockquote>
-<img src="images/sysinfo_start.GIF" alt="sysinfo (Derby System Information)" width="836" height="684"></img>
-</blockquote>
-<ul>
-<li>
-The <b>Console</b> view will show the output from running the <b>sysinfo</b> 
-command. The output from <b>sysinfo</b> is divided into three sections:
-<ul>
-<li>
-Java Information
-</li>
-<li>
-Derby Information
-</li>
-<li>
-Locale Information (if present) <br/><br/>
-</li>
-</ul>
-<li>
-Additional info about using <b>sysinfo</b> can be found in the Derby <i>Tools &amp; Utility Guide</i>.
-</li>
-</ul>
-</p>
-<p>
-Sample output from running <b>sysinfo</b> is shown below.
-</p>
-
-<blockquote>
-<img src="images/sysinfo_output.GIF" alt="sysinfo output" width="862" height="645"></img>
-</blockquote>
-<p>
-</p>
-</body>
-</html>
+<html>
+<head>
+<title>Running sysinfo for environment information</title>
+</head>
+<body>
+<h2>Running sysinfo for environment information</h2>
+<p>
+<b>sysinfo</b> provides information about the Derby system. This tool is
+useful in determing the current Java and Derby environments.
+</p>
+<h3>To launch <b>sysinfo</b>:</h3>
+<ul>
+<li>
+Select the project and bring up the context menu. Select the menu item, <b>sysinfo (Derby System Information)</b>.
+</li>
+</ul>
+<blockquote>
+<img src="images/sysinfo_start.GIF" alt="sysinfo (Derby System Information)" width="836" height="684"></img>
+</blockquote>
+<ul>
+<li>
+The <b>Console</b> view will show the output from running the <b>sysinfo</b> 
+command. The output from <b>sysinfo</b> is divided into three sections:
+<ul>
+<li>
+Java Information
+</li>
+<li>
+Derby Information
+</li>
+<li>
+Locale Information (if present) <br/><br/>
+</li>
+</ul>
+<li>
+Additional info about using <b>sysinfo</b> can be found in the Derby <i>Tools &amp; Utility Guide</i>.
+</li>
+</ul>
+</p>
+<p>
+Sample output from running <b>sysinfo</b> is shown below.
+</p>
+
+<blockquote>
+<img src="images/sysinfo_output.GIF" alt="sysinfo output" width="862" height="645"></img>
+</blockquote>
+<p>
+</p>
+</body>
+</html>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.plugin.doc/topics/sysinfo.html
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.classpath
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.classpath?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.classpath (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.classpath Fri Oct 28 04:51:50 2005
@@ -1,7 +1,7 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
-	<classpathentry kind="src" path="src"/>
-	<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
-	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
-	<classpathentry kind="output" path="bin"/>
-</classpath>
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+	<classpathentry kind="src" path="src"/>
+	<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
+	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+	<classpathentry kind="output" path="bin"/>
+</classpath>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.classpath
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.project
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.project?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.project (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.project Fri Oct 28 04:51:50 2005
@@ -1,28 +1,28 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.apache.derby.ui</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.jdt.core.javabuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-		<nature>org.eclipse.jdt.core.javanature</nature>
-	</natures>
-</projectDescription>
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>org.apache.derby.ui</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>org.eclipse.jdt.core.javabuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.pde.ManifestBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.pde.SchemaBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>org.eclipse.pde.PluginNature</nature>
+		<nature>org.eclipse.jdt.core.javanature</nature>
+	</natures>
+</projectDescription>

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/.project
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/build.properties
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/build.properties?rev=329187&r1=329186&r2=329187&view=diff
==============================================================================
--- db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/build.properties (original)
+++ db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/build.properties Fri Oct 28 04:51:50 2005
@@ -1,7 +1,7 @@
-bin.includes = icons/,\
-               ui.jar,\
-               install_plugin.html,\
-               plugin.xml
-jars.compile.order = ui.jar
-source.ui.jar = src/
-output.ui.jar = bin/
+bin.includes = icons/,\
+               ui.jar,\
+               install_plugin.html,\
+               plugin.xml
+jars.compile.order = ui.jar
+source.ui.jar = src/
+output.ui.jar = bin/

Propchange: db/derby/code/trunk/plugins/eclipse/org.apache.derby.ui/build.properties
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message