Skip to Content
Version 34.1 by David Holt on 2008/05/07 17:51
Hide last authors
David Holt 11.1 1 **Getting Started with BugTracker**
2
David Holt 29.1 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.
David Holt 11.1 4
David Holt 31.1 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
David Holt 29.1 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.
David Holt 11.1 12
David Holt 29.1 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
David Holt 31.1 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
David Holt 25.1 21 [[image:Context-023.jpg]]
22 [[image:Context-024.jpg]]
23 [[image:Context-025.jpg]]
24
David Holt 11.1 25 ----
26
David Holt 25.1 27 2. Check out the folders into their own projects in your workspace.
David Holt 11.1 28
David Holt 25.1 29 [[image:Context-026.jpg]]
30
31 ----
32
33 3. Your workspace should look roughly like this once it has completed rebuilding:
34
David Holt 11.1 35 [[image:Context-027.jpg]]
36
37 ----
38
David Holt 25.1 39 4. First order of business is to find your Properties file by turning off the filter that is on by default:
40
41 [[image:Context-028.jpg]]
42
43 ----
44
45 5. Uncheck the item selected in the image below:
46
47 [[image:Context-029.jpg]]
48
49 ----
50
David Holt 33.1 51 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"
David Holt 11.1 52
David Holt 29.1 53 {{warning title="Missing Properties"}}
54
55 The current Wonder source (Oct 31,2007) requires the addition of this property to he Properties file in BugTracker to run properly (Can someone commit this please?)
56
57 er.extensions.ERXRaiseOnMissingEditingContextDelegate=false
58
59 {{/warning}}
60
David Holt 25.1 61 You can either set Global properties for your database, or you can set them for a specific model. See the Wonder docs for more information about Properties files and database configuration [[ERXConfigurationManager documentation>>http://webobjects.mdimension.com/wonder/api/er/extensions/ERXConfigurationManager.html]]
62
63 Here are the Global database connection settings I used for FrontBase. If you are using a different setup, you may want to ask on the mailing list for guidance:
64
David Holt 29.1 65 ERXConfigurationManager properties moved in from Properties.ak
66 Original Settings for Postgresql
67 Changed to Frontbase
David Holt 25.1 68 dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
69 dbConnectUserGLOBAL=//system
70 dbConnectPluginGLOBAL=Frontbase
David Holt 29.1 71 dbConnectDriverGLOBAL=org.postgresql.Driver
72 dbConnectPasswordGLOBAL =
David Holt 25.1 73 dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
74 er.javamail.adminEmail=foo@localhost.com//
75
76 You can see the Properties file that you are editing in the following screenshot:
77
Kieran Kelleher 23.1 78 [[image:Context-036.jpg]]
David Holt 11.1 79
David Holt 29.1 80 {{info title="MySQL Configuration for BugTracker"}}
81
82 * Create a database named "bug" in your MySQL development database
83 * Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
84 * Add the following properties to the Properties file in BugTracker using the user and password from the previous step
85
86 dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
87 dbConnectUserGLOBAL=user
88 dbConnectPasswordGLOBAL=password
89 dbConnectPluginGLOBAL=
90 dbConnectDriverGLOBAL=
91 dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
92 er.javamail.adminEmail=foobar@domain.com
93
94
95 {{/info}}
96
David Holt 11.1 97 ----
98
David Holt 25.1 99 Make sure that the build path contains the plugin for your database;
David Holt 11.1 100
101 [[image:Context-030.jpg]]
102
103 ----
104
David Holt 25.1 105 7. Now we want to run the app. The Wonder team has set it up so that you can generate all necessary tables and populate them when you launch the BugTracker application for the first time using a special launch configuration.
David Holt 11.1 106
107 You'll see BugTracker launch configurations for creating, creating without dropping, and normal launching. We need to select the BugTracker (create without drop) launch configuration for the initial setup.
108
109 [[image:Context-031.jpg]]
110
111 ----
112
David Holt 25.1 113 8. We do that by selecting Run as > Run...
David Holt 11.1 114
115 [[image:Context-032.jpg]]
116
117 ----
118
David Holt 25.1 119 9. In the resulting dialog box, select BugTracker (create without drop). If you try to use (create) you'll get a bunch of errors complaining about lack of tables in the database.
David Holt 11.1 120
121 [[image:Context-033.jpg]]
122
123 ----
124
David Holt 25.1 125 10. You'll see a long list of things being done in your console window that takes several minutes. When you get the final Done message, your database is set up and ready to go. You can log into your database to confirm that the tables have been magically created and populated.
David Holt 11.1 126
127 Now select BugTracker as your launch configuration to start the application:
128
129 [[image:Context-034.jpg]]
130
131 ----
132
David Holt 25.1 133 ~11. You should see a login screen. Your default administrative user is "admin" with password "admin"
David Holt 11.1 134
135 [[image:Context-035.jpg]]
136
137 ----
138
David Holt 29.1 139 12. Explore