Changes for page Getting Started with BugTracker
Last modified by Pascal Robert on 2012/07/27 20:28
From version 28.1
edited by David Holt
on 2007/06/20 20:07
on 2007/06/20 20:07
Change comment:
There is no comment for this version
To version 26.1
edited by David Holt
on 2008/05/07 18:11
on 2008/05/07 18:11
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,9 +1,23 @@ 1 1 **Getting Started with BugTracker** 2 2 3 -~1. Import the followingsource code folders fromCVSaccordingto the [[tutorial>>http://wiki.objectstyle.org/confluence/display/WOL/Project+Wonder+woa+with+Linked+Source]]. You mayneed to adjust the exact folders youimport depending on the databaseyouplan touse. Inthis case, I have added the FrontBasepluginaswell as all the otherframeworksthat BugTracker expectsto findn itsbuildpath.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 - The next three screenshots are showing thefoldersthatcan befound ontheCVS server for Wonder. I have splitthemup because allthe foldersdon'tfiton the screenatonce!Asyou can see,thefoldersthatare necessary are found in several different sub-folders.5 +{{info title="Alternate method for getting started with BugTracker"}} 6 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 +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 + 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 + 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 + 7 7 [[image:Context-023.jpg]] 8 8 [[image:Context-024.jpg]] 9 9 [[image:Context-025.jpg]] ... ... @@ -34,20 +34,30 @@ 34 34 35 35 ---- 36 36 37 - 6. Change the Properties locatedin the resources folder to match the requirements for your database. Wonder applications need Propertiesfiles to manage their configurationcorrectly. 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 movedthe relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database.51 +{{id value="Configuration"}}{{/id}} 38 38 53 +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" 54 + 55 +{{warning title="Missing Properties"}} 56 + 57 +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?) 58 + 59 +er.extensions.ERXRaiseOnMissingEditingContextDelegate=false 60 + 61 +{{/warning}} 62 + 39 39 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]] 40 40 41 41 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: 42 42 43 - #ERXConfigurationManager properties moved in from Properties.ak44 - #Original Settings for Postgresql45 - #Changed to Frontbase67 +ERXConfigurationManager properties moved in from Properties.ak 68 +Original Settings for Postgresql 69 +Changed to Frontbase 46 46 dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug 47 47 dbConnectUserGLOBAL=//system 48 48 dbConnectPluginGLOBAL=Frontbase 49 - #dbConnectDriverGLOBAL=org.postgresql.Driver50 - #dbConnectPasswordGLOBAL =73 +dbConnectDriverGLOBAL=org.postgresql.Driver 74 +dbConnectPasswordGLOBAL = 51 51 dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes 52 52 er.javamail.adminEmail=foo@localhost.com// 53 53 ... ... @@ -55,6 +55,23 @@ 55 55 56 56 [[image:Context-036.jpg]] 57 57 82 +{{info title="MySQL Configuration for BugTracker"}} 83 + 84 +* Create a database named "bug" in your MySQL development database 85 +* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish) 86 +* Add the following properties to the Properties file in BugTracker using the user and password from the previous step 87 + 88 +dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true 89 +dbConnectUserGLOBAL=user 90 +dbConnectPasswordGLOBAL=password 91 +dbConnectPluginGLOBAL= 92 +dbConnectDriverGLOBAL= 93 +dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes 94 +er.javamail.adminEmail=foobar@domain.com 95 + 96 + 97 +{{/info}} 98 + 58 58 ---- 59 59 60 60 Make sure that the build path contains the plugin for your database; ... ... @@ -97,4 +97,4 @@ 97 97 98 98 ---- 99 99 100 -12. Explore !!141 +12. Explore