Skip to Content

Getting Started with BugTracker

Version 11.1 by David Holt on 2008/09/11 19:47
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Getting Started with BugTracker

1. Import the source code folders needed for BugTracker either from local Wonder source tree or from Wonder CVS server as discussed below.

Information
Alternate method for getting started with BugTracker

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.

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.

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.

Warning
Missing Projects from the screenshots below

BugTracker has new dependencies on DerbyPlugin and ERChronic since these screenshots were taken. Make sure to import them into your workspace as well.

Context-023.jpg
Context-024.jpg
Context-025.jpg

2. Check out the folders into their own projects in your workspace.

Context-026.jpg

3. Your workspace should look roughly like this once it has completed rebuilding:

Context-027.jpg

4. First order of business is to find your Properties file by turning off the filter that is on by default:

Context-028.jpg

5. Uncheck the item selected in the image below:

Context-029.jpg

Invalid macro parameters used for the [id] macro. Cause: [Property [name] mandatory]. Click on this message for details.

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"

Information
Update: Sept 11, 2008 How to enable properties for databases other than Derby (FrontBase,PostgreSQL)
  • 3 Default Global database properties files are now included with BugTracker. Please see Properties.Derby,Properties.FrontBase,Properties.PostgreSQL
  • In the 3 launch configurations (discussed below in point 7) user.name=Derby is now set by default.
  • You can swap out Derby for your favourite database (i.e. user.name=FrontBase or user.name=PostgreSQL) in all 3 launch configurations if you want to use your database properties instead of the default Derby

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

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:

ERXConfigurationManager properties moved in from Properties.ak
Original Settings for Postgresql
Changed to Frontbase
dbConnectURLGLOBAL=jdbc:frontbase://localhost/bug
dbConnectUserGLOBAL=system
dbConnectPluginGLOBAL=Frontbase
dbConnectDriverGLOBAL=org.postgresql.Driver
dbConnectPasswordGLOBAL =
dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
er.javamail.adminEmail=foo@localhost.com

You can see the Properties file that you are editing in the following screenshot:

Context-036.jpg

Information
MySQL Configuration for BugTracker
  • Create a database named "bug" in your MySQL development database
  • Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
  • Add the following properties to the Properties file in BugTracker using the user and password from the previous step

dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
dbConnectUserGLOBAL=user
dbConnectPasswordGLOBAL=password
dbConnectPluginGLOBAL=
dbConnectDriverGLOBAL=
dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
er.javamail.adminEmail=foobar@domain.com

Make sure that the build path contains the plugin for your database;

Context-030.jpg

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.

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.

Context-031.jpg

8. We do that by selecting Run as > Run...

Context-032.jpg

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.

Context-033.jpg

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.

Now select BugTracker as your launch configuration to start the application:

Context-034.jpg

11. You should see a login screen. Your default administrative user is "admin" with password "admin"

Context-035.jpg

12. Explore