Changes for page Maven Creating Wonder Applications
Last modified by David Holt on 2022/06/25 01:40
From version 18.1
edited by Greg.Brown
on 2009/02/28 16:27
on 2009/02/28 16:27
Change comment:
There is no comment for this version
To version 27.1
edited by Greg.Brown
on 2009/02/20 07:26
on 2009/02/20 07:26
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,7 +1,7 @@ 1 1 = Creating Wonder Applications using Maven + m2eclicpse = 2 2 3 3 {{note}} 4 - Under Construction - but still a good starting point4 + Under Construction 5 5 {{/note}} 6 6 7 7 If you want to use Wonder in your applications (and why woundn't one) you must be correctly setup with: ... ... @@ -41,37 +41,20 @@ 41 41 The woapplication-archtype is under construction, so you must fix a few things. 42 42 # Fix the pom.xml. Delete the properties and dependencies sections that the woapplication-archtype created, and paste this into the pom: 43 43 {code:xml} 44 - ...44 + 45 45 <properties> 46 - <woversion>5.4.3</woversion> 47 - <wonderclassifier>wo54</wonderclassifier> 46 + <woversion>5.3.3</woversion> 48 48 <wonderversion>5.0.0-SNAPSHOT</wonderversion> 49 49 </properties> 50 50 51 - <!-- the dependency management section defines the characteristics of your dependencies to use when referenced elsewhere --> 52 - <!-- See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html --> 53 53 <dependencyManagement> 54 - <!-- Only ERExtensions and WOOgnl need a wo53 or wo54 classifier but adding it for all WOnder dependencies safeguards it for any future changes to WOnder --> 55 55 <dependencies> 56 - <!-- in the order you'd like --> 57 57 <dependency> 58 - <groupId>wonder.core</groupId> 59 - <artifactId>ERExtensions</artifactId> 60 - <version>${wonderversion}</version> 61 - <classifier>${wonderclassifier}</classifier> 53 + <groupId>com.webobjects</groupId> 54 + <artifactId>JavaFoundation</artifactId> 55 + <version>${woversion}</version> 62 62 </dependency> 63 63 <dependency> 64 - <groupId>wonder.core</groupId> 65 - <artifactId>WOOgnl</artifactId> 66 - <version>${wonderversion}</version> 67 - <classifier>${wonderclassifier}</classifier> 68 - </dependency> 69 - <dependency> 70 - <groupId>wonder.core</groupId> 71 - <artifactId>ERPrototypes</artifactId> 72 - <version>${wonderversion}</version> 73 - </dependency> 74 - <dependency> 75 75 <groupId>com.webobjects</groupId> 76 76 <artifactId>JavaWebObjects</artifactId> 77 77 <version>${woversion}</version> ... ... @@ -81,51 +81,57 @@ 81 81 <artifactId>JavaEOAccess</artifactId> 82 82 <version>${woversion}</version> 83 83 </dependency> 67 + <dependency> 68 + <groupId>wonder.core</groupId> 69 + <artifactId>ERExtensions</artifactId> 70 + <version>${wonderversion}</version> 71 + <classifier>wo53</classifier> 72 + </dependency> 84 84 <dependency> 85 - <groupId>com.webobjects</groupId> 86 - <artifactId>JavaFoundation</artifactId> 87 - <version>${woversion}</version> 74 + <groupId>wonder.core</groupId> 75 + <artifactId>ERPrototypes</artifactId> 76 + <version>${wonderversion}</version> 77 + 88 88 </dependency> 89 89 </dependencies> 90 90 </dependencyManagement> 91 - 92 - <!-- now you just reference the groupId and artifactId of each dependency required. This will work for any child pom also. --> 93 - <!-- See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html --> 81 +<!-- Only ERExtensions and WOOgnl need a wo53 or wo54 classifier --> 94 94 <dependencies> 95 95 <dependency> 96 96 <groupId>wonder.core</groupId> 97 97 <artifactId>ERExtensions</artifactId> 98 - <classifier>${wonderclassifier}</classifier> 86 + <version>${wonderversion}</version> 87 + <classifier>wo53</classifier> 99 99 </dependency> 100 100 <dependency> 101 101 <groupId>wonder.core</groupId> 102 - <artifactId>WOOgnl</artifactId> 103 - <classifier>${wonderclassifier}</classifier> 104 - </dependency> 105 - <dependency> 106 - <groupId>wonder.core</groupId> 107 107 <artifactId>ERPrototypes</artifactId> 92 + <version>${wonderversion}</version> 108 108 </dependency> 109 109 <dependency> 110 110 <groupId>com.webobjects</groupId> 111 111 <artifactId>JavaFoundation</artifactId> 97 + <version>${woversion}</version> 112 112 </dependency> 113 113 <dependency> 114 114 <groupId>com.webobjects</groupId> 115 115 <artifactId>JavaWebObjects</artifactId> 102 + <version>${woversion}</version> 116 116 </dependency> 117 117 <dependency> 118 118 <groupId>com.webobjects</groupId> 119 119 <artifactId>JavaEOAccess</artifactId> 107 + <version>${woversion}</version> 120 120 </dependency> 109 + 121 121 </dependencies> 122 122 123 123 {code} Fix the versions and classifiers in the pom to be the correct values. 124 124 125 -2. Fix the Application, Session, DirectAction jave files import statements.As of this writing theimport statementsare incorrect for Wonder5.0 which refactoredall its classesintopackagesotherhan{code}er.extensions{code}.So justrightclick on Thesethreefilesand chooseSource > Organize Importswhich should, as of this writing, makethem {code}importer.extensions.appserver.ERX...{code}114 +2. Fix the Application, Session, DirectAction jave files. They all should: {code}import er.extensions.appserver.ERX????{code} But the ".appserver." is left out of the import statements. 126 126 127 127 3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent. 128 -4. The "Properties" fileis blank,you cancopyonefromanonMavenWonderApplication.117 +4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.? 129 129 5. Main component is NSMacOSRomanStringEncoding, non-Maven Wonder apps use "UTF-8" in the woo. 130 130 131 131 {{/note}}