Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 19452 invoked from network); 9 Jun 2005 22:25:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jun 2005 22:25:11 -0000 Received: (qmail 33984 invoked by uid 500); 9 Jun 2005 22:25:10 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 33962 invoked by uid 500); 9 Jun 2005 22:25:10 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 33949 invoked by uid 99); 9 Jun 2005 22:25:09 -0000 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,HTML_20_30,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from web81307.mail.yahoo.com (HELO web81307.mail.yahoo.com) (206.190.37.82) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 09 Jun 2005 15:25:05 -0700 Message-ID: <20050609222458.43041.qmail@web81307.mail.yahoo.com> Received: from [32.97.110.142] by web81307.mail.yahoo.com via HTTP; Thu, 09 Jun 2005 15:24:58 PDT Date: Thu, 9 Jun 2005 15:24:58 -0700 (PDT) From: Susan Cline Subject: Re: Amend to BUILDING.TXT with ant target info for the plugin To: Derby Development , Andrew McIntyre In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1011248539-1118355898=:42646" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --0-1011248539-1118355898=:42646 Content-Type: multipart/alternative; boundary="0-512707956-1118355898=:42646" --0-512707956-1118355898=:42646 Content-Type: text/plain; charset=us-ascii Great, thanks for the info. Attached is a patch for two items: 1) Add a section about how to build the core plugin in BUILDING.TXT 2) Put the Readme.txt file for building the UI plugin into the source tree under trunk/plugins/eclipse Once this patch is committed I'll fix the link in the web page integrate/plugin_howto.html to point to Readme.txt in the source. Also could you help with an svn question? I did another svn update right before I made this patch to make sure I was up to date. For the two files for DERBY-314 I modified I got this output: G plugins\eclipse\org.apache.derby.ui\src\org\apache\derby\ui\common\Messages.java G plugins\eclipse\org.apache.derby.ui\src\org\apache\derby\ui\properties\DerbyPropertiesPage.java Could you explain to me what the 'G' means, other than Merged? Also thank you for committing the patch for DERBY-314. Thanks a lot, Susan Andrew McIntyre wrote: You can do 'svn diff BUILDING.TXT' to get just the changes for BUILDING.TXT. Any number of filenames can be passed in to svn diff, and it will produce a patch for the listed files. Providing no filenames produces the diffs for all modified files in your current view. Also, I don't think I realized you had posted a patch for Derby-314. I'll take a look at that shortly as well. --0-512707956-1118355898=:42646 Content-Type: text/html; charset=us-ascii
Great, thanks for the info.
 
Attached is a patch for two items:
 
1) Add a section about how to build the core plugin in BUILDING.TXT
2) Put the Readme.txt file for building the UI plugin into the source tree
    under trunk/plugins/eclipse
 
Once this patch is committed I'll fix the link in the web page integrate/plugin_howto.html to point to Readme.txt in the source.
 
Also could you help with an svn question?  I did another svn update right before I made this patch to make sure I was up to date.  For the two files for DERBY-314 I modified I got this output:
 
G  plugins\eclipse\org.apache.derby.ui\src\org\apache\derby\ui\common\Messages.java
G  plugins\eclipse\org.apache.derby.ui\src\org\apache\derby\ui\properties\DerbyPropertiesPage.java
Could you explain to me what the 'G' means, other than Merged?
 
Also thank you for committing the patch for DERBY-314.
 
Thanks a lot,
 
Susan

Andrew McIntyre <mcintyre.a@gmail.com> wrote:



You can do 'svn diff BUILDING.TXT' to get just the changes for
BUILDING.TXT. Any number of filenames can be passed in to svn diff,
and it will produce a patch for the listed files. Providing no
filenames produces the diffs for all modified files in your current
view.

Also, I don't think I realized you had posted a patch for Derby-314.
I'll take a look at that shortly as well.

--0-512707956-1118355898=:42646-- --0-1011248539-1118355898=:42646 Content-Type: text/plain; name="building.diff" Content-Description: 4231402294-building.diff Content-Disposition: inline; filename="building.diff" Index: BUILDING.txt =================================================================== --- BUILDING.txt (revision 189829) +++ BUILDING.txt (working copy) @@ -554,6 +554,9 @@ cleandocs: remove javadoc directory (${derby.source}/javadoc) + plugin: creates a zip file, derby_eclipse_plug-in.zip, in the + jars/insane directory. The plugin target depends on the + default ant target. This creates the Core plug-in only. 4.2 Derby source code upgrade Index: plugins/eclipse/Readme.txt =================================================================== --- plugins/eclipse/Readme.txt (revision 0) +++ plugins/eclipse/Readme.txt (revision 0) @@ -0,0 +1,120 @@ +Obtaining the Source and Building the Derby 1.0 UI and Help Plug-ins + +This document describes how to obtain the source for the +Apache Derby 1.0 UI and Help plug-ins for Eclipse. Instructions +for importing the source as an Eclipse project and packaging the +plug-ins as a zip file are also included. + +Contents: + +I. Creating the Apache Derby UI and Help Plug-in Projects +II. Creating zip files for the Derby UI and Help Plug-ins via the Project + +========================================================================= + +I. Creating the Apache Derby UI and Help Plug-in projects: + +1) Check out the source for the UI and Help plug-ins via SVN (Subversion). + + Refer to the detailed instructions on readying your environment + to check out any Derby source here: + + http://incubator.apache.org/derby/derby_downloads.html + + To check out the entire development trunk use this command: + + svn checkout https://svn.apache.org/repos/asf/incubator/derby/code/trunk/ + + This includes the source for both the UI and Help plugins. If you want to + check out only the UI and Help plugins, and not the entire Derby source code + issue this command instead: + + svn checkout https://svn.apache.org/repos/asf/incubator/derby/code/trunk/plugins + + +2) Install Eclipse 3.x and the JDK needed + +3) Install the Apache Derby 10.1.0 Eclipse Core plug-in from: + http://incubator.apache.org/derby/derby_downloads.html + + It is available as a zip file: + + for example; derby_core_plugin_10.1.0.178324.zip + + Unzip this file into the directory where the eclipse executable is located. + For instance, if Eclipse is installed in C:\eclipse, unzip the Derby + Core plug-in zip file to C:\eclipse. + +4) Invoke the Eclipse IDE, provide an appropriate location as the workspace + + for example: c:\derby\plugin + +5) Import the Apache Derby UI project: + File -> Import -> Existing Project into Workspace + - Click Next + - Click Browse and point to the "org.apache.derby.ui" directory (created in + Step 1, which is under the plugins/eclipse directory where you checked + out the source) + - Click Finish + +6) Switch to the Plug-in perspective + Window -> Open Perspective -> Other -> Select Plug-in Development + +7) To invoke and test the Apache Derby UI Plug-in in this development environment + + Run ->Run As -> Eclipse Application (Eclipse 3.1) + OR + Run --> Run As --> Run-time Workbench (Eclipse 3.0) + + An alternate way would be to open the plugin.xml and select the + 'Launch a runtime workbench' link. + + This will open a new Eclipse window with all the current plug-ins under + development in its environment. + +Follow steps 4 - 7 as above for creating the Help plug-in project, substituting +org.apache.derby.plugin.doc for org.apache.derby.ui. +================================================================================ + +II. Creating zip files for the Derby UI and Help Plug-ins via the Project + +In order to install the plug-ins easily in another Eclipse environment creating +a zip file is useful. + +To create a zip file for the UI plug-in: + +1) From within the Plug-in Development perspective, right-click the org.apache.derby.ui + project. Select Export --> Deployable plug-ins and fragments, then the Next button. + +2) In the Export Plug-ins and Fragments window select the org.apache.derby.ui project + listed in the Available Plug-ins and Fragments text area. For the Export Options + section select Deploy as: a single ZIP file. Click the Build Options button. + Check any options desired from the Build Options Preferences window and then + click OK. + +3) Browse to a Destination where you would like to put the zip file and name it + org.apache.derby.ui_1.0.0.zip to represent the name and version of the plug-in. + +4) Finally, click Finish. + +5) To install in another Eclipse installation unzip this file in the base + directory of the Eclipse installation. + +To create a zip file for the Doc plug-in: + +1) From within the Plug-in Development perspective, right-click the + org.apache.derby.plugin.doc project. Select Export --> Zip file. + +2) In the Export Zip file window select the org.apache.derby.plugin.doc project + listed in the left frame. In the right frame uncheck the .project and + build.properties files. + +3) Browse to a Destination where you would like to put the zip file and name it + org.apache.derby.plugin.doc_1.0.0.zip to represent the name and version of + the plug-in. + +4) Finally, click Finish. + +5) Note that the documentation zip files' base directory is + org.apache.derby.plugin.doc and therefore must be unzipped in the plug-ins + directory. Property changes on: plugins/eclipse/Readme.txt ___________________________________________________________________ Name: svn:eol-style + native --0-1011248539-1118355898=:42646--