Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 32.1
edited by David Holt
on 2008/05/07 18:09
Change comment: There is no comment for this version
To version 30.1
edited by David Holt
on 2007/10/31 20:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,22 +2,10 @@
2 2  
3 3  ~1. Import the source code folders needed for BugTracker either [[from local Wonder source tree>>http://wiki.objectstyle.org/confluence/display/WONDER/Working+with+Wonder+source+in+Eclipse]] or from Wonder CVS server as discussed below.
4 4  
5 -{{info title="Alternate method for getting started with BugTracker"}}
6 -
7 -If you're just exploring BugTracker, you may prefer to use the method outlined on [this page|Getting Started with BugTracker Alternate method] that depends on installed Wonder frameworks instead of importing the Wonder source into your workspace.
8 -
9 -{{/info}}
10 -
11 11  The next three screenshots are showing the folders that can be found on the CVS server for Wonder. I have split them up because all the folders don't fit on the screen at once As you can see, the folders that are necessary are found in several different sub-folders.
12 12  
13 13  You may need to adjust the exact folders you import depending on the database you plan to use. In this case, I have added the FrontBase plugin as well as all the other frameworks that BugTracker expects to find in its build path.
14 14  
15 -{{warning title="Missing Projects from the screenshots below"}}
16 -
17 -BugTracker has new dependencies on DerbyPlugin and ERChronic since these screenshots were taken. Make sure to import them into your workspace as well.
18 -
19 -{{/warning}}
20 -
21 21  [[image:Context-023.jpg]]
22 22  [[image:Context-024.jpg]]
23 23  [[image:Context-025.jpg]]
... ... @@ -48,7 +48,7 @@
48 48  
49 49  ----
50 50  
51 -[[||anchor="Configuration"]]6. Change the Properties located in the resources folder to match the requirements for your database. Wonder applications need Properties files to manage their configuration correctly. There are a number of different places in the Wonder frameworks that application properties will be read from. In the original example, the Database connection properties are taken from a logged in user's properties file, in this case it is named "Properties.ak". I moved the relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database. Alternatively (a recommended way) you can create your own "Properties.username" file by duplicating "Properties.ak"
39 +6. Change the Properties located in the resources folder to match the requirements for your database. Wonder applications need Properties files to manage their configuration correctly. There are a number of different places in the Wonder frameworks that application properties will be read from. In the original example, the Database connection properties are taken from a logged in user's properties file, in this case it is named "Properties.ak". I moved the relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database. Alternatively (a recommended way) you can create your own "Properties.username" file by duplicating "Properties.ak"
52 52  
53 53  {{warning title="Missing Properties"}}
54 54