Changes for page Getting Started with BugTracker
Last modified by Pascal Robert on 2012/07/27 20:28
From version 30.1
edited by David Holt
on 2007/10/31 20:40
on 2007/10/31 20:40
Change comment:
There is no comment for this version
To version 27.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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,11 +1,9 @@ 1 1 **Getting Started with BugTracker** 2 2 3 -~1. Import the source code folders neededforBugTrackereither[[from local Wonder sourcetree>>http://wiki.objectstyle.org/confluence/display/WONDER/Working+with+Wonder+source+in+Eclipse]] orfromWonderCVSserverasdiscussed below.3 +~1. Import the following source code folders from CVS according to the [[tutorial>>http://wiki.objectstyle.org/confluence/display/WOL/Project+Wonder+woa+with+Linked+Source]]. 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. 4 4 5 -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. 5 +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. 6 6 7 -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. 8 - 9 9 [[image:Context-023.jpg]] 10 10 [[image:Context-024.jpg]] 11 11 [[image:Context-025.jpg]] ... ... @@ -36,28 +36,20 @@ 36 36 37 37 ---- 38 38 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"37 +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. 40 40 41 -{{warning title="Missing Properties"}} 42 - 43 -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?) 44 - 45 -er.extensions.ERXRaiseOnMissingEditingContextDelegate=false 46 - 47 -{{/warning}} 48 - 49 49 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]] 50 50 51 51 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: 52 52 53 -ERXConfigurationManager properties moved in from Properties.ak 54 -Original Settings for Postgresql 55 -Changed to Frontbase 43 +#ERXConfigurationManager properties moved in from Properties.ak 44 +#Original Settings for Postgresql 45 +#Changed to Frontbase 56 56 dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug 57 57 dbConnectUserGLOBAL=//system 58 58 dbConnectPluginGLOBAL=Frontbase 59 -dbConnectDriverGLOBAL=org.postgresql.Driver 60 -dbConnectPasswordGLOBAL = 49 +#dbConnectDriverGLOBAL=org.postgresql.Driver 50 +#dbConnectPasswordGLOBAL = 61 61 dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes 62 62 er.javamail.adminEmail=foo@localhost.com// 63 63 ... ... @@ -65,23 +65,6 @@ 65 65 66 66 [[image:Context-036.jpg]] 67 67 68 -{{info title="MySQL Configuration for BugTracker"}} 69 - 70 -* Create a database named "bug" in your MySQL development database 71 -* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish) 72 -* Add the following properties to the Properties file in BugTracker using the user and password from the previous step 73 - 74 -dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true 75 -dbConnectUserGLOBAL=user 76 -dbConnectPasswordGLOBAL=password 77 -dbConnectPluginGLOBAL= 78 -dbConnectDriverGLOBAL= 79 -dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes 80 -er.javamail.adminEmail=foobar@domain.com 81 - 82 - 83 -{{/info}} 84 - 85 85 ---- 86 86 87 87 Make sure that the build path contains the plugin for your database; ... ... @@ -124,4 +124,4 @@ 124 124 125 125 ---- 126 126 127 -12. Explore 100 +12. Explore!!