Changes for page Maven Creating Wonder Applications

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ldeck
	1	+XWiki.gbrown

Content

...	...	@@ -21,18 +21,12 @@
21	21
22	22	With all the tools ready, it's time to make a Wonder application.
23	23
24		-~1. Make a new project File > New > Other project, choose a Maven project: [[image:wolimmave2.gif]]
	24	+1. Make a new project File > New > Other project, choose a Maven project: [[image:wolimmave2.gif]]
	25	+1. Hit Next
	26	+1. Hit Next again
	27	+1. Select an archtype, use the local catalog, select the woapplication-archtype, hit Next:!wolimmaven.gif!
	28	+1. Fill in appropriate parameters for the woapplication-archtype to set up your new application, hit Finish!
25	25
26		-2. Hit Next
27		-
28		-3. Hit Next again [[image:wolimmavena.gif]]
29		-
30		-4. Select an archtype, use the local catalog, select the woapplication-archtype, hit Next:!wolimmavenb.gif!
31		-
32		-5. Fill in appropriate parameters for the woapplication-archtype to set up your new application, hit Finish!
33		-
34		-[[image:wolimmaven.gif]]
35		-
36	36	The eclipse plugins now create your application!
37	37
38	38	You should create a WOApplication Run Configuration and add the projects build folder's Java to the classpath as detailed here: [[Maven Running or Debugging as WO Application]], otherwise classes won't be found, etc.
...	...	@@ -41,38 +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		-...
	38	+
45	45	<properties>
46		- <woclassifier>wo54</woclassifier>
47		- <woversion>5.4.3</woversion>
	40	+ <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>${woclassifier}</classifier>
	47	+ <groupId>com.webobjects</groupId>
	48	+ <artifactId>JavaFoundation</artifactId>
	49	+ <version>${woversion}</version>
62	62	</dependency>
63	63	<dependency>
64		- <groupId>wonder.core</groupId>
65		- <artifactId>ERPrototypes</artifactId>
66		- <version>${wonderversion}</version>
67		- <classifier>${woclassifier}</classifier>
68		- </dependency>
69		- <dependency>
70		- <groupId>wonder.core</groupId>
71		- <artifactId>WOOgnl</artifactId>
72		- <version>${wonderversion}</version>
73		- <classifier>${woclassifier}</classifier>
74		- </dependency>
75		- <dependency>
76	76	<groupId>com.webobjects</groupId>
77	77	<artifactId>JavaWebObjects</artifactId>
78	78	<version>${woversion}</version>
...	...	@@ -82,48 +82,54 @@
82	82	<artifactId>JavaEOAccess</artifactId>
83	83	<version>${woversion}</version>
84	84	</dependency>
	61	+ <dependency>
	62	+ <groupId>wonder.core</groupId>
	63	+ <artifactId>ERExtensions</artifactId>
	64	+ <version>${wonderversion}</version>
	65	+ <classifier>wo53</classifier>
	66	+ </dependency>
85	85	<dependency>
86		- <groupId>com.webobjects</groupId>
87		- <artifactId>JavaFoundation</artifactId>
88		- <version>${woversion}</version>
	68	+ <groupId>wonder.core</groupId>
	69	+ <artifactId>ERPrototypes</artifactId>
	70	+ <version>${wonderversion}</version>
	71	+
89	89	</dependency>
90	90	</dependencies>
91	91	</dependencyManagement>
92		-
93		- <!-- now you just reference the groupId and artifactId of each dependency required. This will work for any child pom also. -->
94		- <!-- See http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html -->
	75	+<!-- Only ERExtensions and WOOgnl need a wo53 or wo54 classifier -->
95	95	<dependencies>
96	96	<dependency>
97	97	<groupId>wonder.core</groupId>
98	98	<artifactId>ERExtensions</artifactId>
99		- <classifier>${wonderclassifier}</classifier>
	80	+ <version>${wonderversion}</version>
	81	+ <classifier>wo53</classifier>
100	100	</dependency>
101	101	<dependency>
102	102	<groupId>wonder.core</groupId>
103		- <artifactId>WOOgnl</artifactId>
104		- <classifier>${wonderclassifier}</classifier>
105		- </dependency>
106		- <dependency>
107		- <groupId>wonder.core</groupId>
108	108	<artifactId>ERPrototypes</artifactId>
	86	+ <version>${wonderversion}</version>
109	109	</dependency>
110	110	<dependency>
111	111	<groupId>com.webobjects</groupId>
112	112	<artifactId>JavaFoundation</artifactId>
	91	+ <version>${woversion}</version>
113	113	</dependency>
114	114	<dependency>
115	115	<groupId>com.webobjects</groupId>
116	116	<artifactId>JavaWebObjects</artifactId>
	96	+ <version>${woversion}</version>
117	117	</dependency>
118	118	<dependency>
119	119	<groupId>com.webobjects</groupId>
120	120	<artifactId>JavaEOAccess</artifactId>
	101	+ <version>${woversion}</version>
121	121	</dependency>
	103	+
122	122	</dependencies>
123	123
124	124	{code} Fix the versions and classifiers in the pom to be the correct values.
125	125
126		-2. Fix the Application, Session, DirectAction jave files import statements. As of this writing the import statements are incorrect for Wonder 5.0 which refactored all its classes into packages other than {code}er.extensions{code}. So just right click on These three files and choose Source > Organize Imports which should, as of this writing, make them {code}import er.extensions.appserver.ERX...{code}
	108	+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.
127	127
128	128	3. Possibly change web components to extend er.extensions.components.ERXComponent instead of the standard WOComponent.
129	129	4. Possible classpath issues; the eclipse component editor has multiple Component and Display Group tabs.?