Skip to Content
Last modified by Henrique Prange on 2015/09/11 17:57
From version 12.1
edited by Lachlan Deck
on 2008/06/15 18:39
Change comment: Continuing to flesh it out...
To version 19.1
edited by Henrique Prange
on 2008/06/15 19:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ldeck
1 +XWiki.hprange
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  {{info title="Recommended Homework (or pre-requisites)"}}
4 4  
5 -It's _really_ worth doing your homework on maven in order to understand it. The place to start is Learning Maven found at http://maven.apache.org. Various guides are also found at http://maven.apache.org/guides/.
5 +It's _really_ worth doing your homework on maven in order to understand it. The place to start is Learning Maven found at [http://maven.apache.org]. Various guides are also found at [http://maven.apache.org/guides/].
6 6  
7 7  At the very least you want to have read through, and understood, the [Getting Started Tutorial|http://maven.apache.org/guides/getting-started/index.html].
8 8  
... ... @@ -39,33 +39,55 @@
39 39  Typical things that make up a pom are as follows. (Note: only pom identification is mandatory. All the others have defaults.)
40 40  
41 41  1. pom identification (who am I?)
42 - The base triplet used to identify an artifact (i.e., product)
43 - {{noformat}}
42 +The base triplet used to identify an artifact (i.e., product)
43 +
44 +{{noformat}}
45 +
44 44   <artifactId>CustomExtensions</artifactId>
45 45   <groupId>com.mywostuff.frameworks</groupId>
46 46   <version>0.0.1-SNAPSHOT</version>
47 - {{/noformat}}
49 +
50 +
51 +{{/noformat}}
52 +
48 48  1. pom packaging (i.e., what are we building?)
49 - The default value for the packaging element is JAR if not specified. For the purposes of this exercise, we'll use JAR for the frameworks and woapplication for the applications, which requires the woproject maven plugin (TODO revisit this scenario with the apple maven plugin)
50 - {{noformat}}
54 +The default value for the packaging element is JAR if not specified. For the purposes of this exercise, we'll use JAR for the frameworks and woapplication for the applications, which requires the woproject maven plugin (TODO revisit this scenario with the apple maven plugin)
55 +
56 +{{noformat}}
57 +
51 51   <packaging>woapplication</artifactId>
52 - {{/noformat}}
59 +
60 +
61 +{{/noformat}}
62 +
53 53  1. pom parent identification (who do I belong to?)
54 - {{noformat}}
64 +
65 +{{noformat}}
66 +
55 55   <parent>
56 56   <artifactId>frameworks</artifactId>
57 57   <groupId>com.mywostuff</groupId>
58 58   </parent>
59 - {{/noformat}}
71 +
72 +
73 +{{/noformat}}
74 +
60 60  1. modules (a.k.a kids; who belongs to me?)
61 - {{noformat}}
76 +
77 +{{noformat}}
78 +
62 62   <modules>
63 63   <module>CustomExtensions</module>
64 64   <module>CustomBusinessLogic</module>
65 65   </modules>
66 - {{/noformat}}
83 +
84 +
85 +{{/noformat}}
86 +
67 67  1. dependencies (what do I need?)
68 - {{noformat}}
88 +
89 +{{noformat}}
90 +
69 69   <dependencies>
70 70   <dependency>
71 71   <groupId>log4j</groupId>
... ... @@ -80,13 +80,16 @@
80 80   <scope>test</scope>
81 81   </dependency>
82 82   </dependencies>
83 - {{/noformat}}
105 +
106 +
107 +{{/noformat}}
108 +
84 84  1. build sources/resources (what do I have?)
85 85  1. properties and filtering resources (variable definitions)
86 86  1. dependency/plugin management (shared configuration and versioning)
87 87  1. repositories (where to find dependencies and plugins)
88 88  
89 -Of course, with the plethora of plugins available for maven, this is only the tip of the iceberg. However, these main concepts will suffice for now.
114 +Of course, with the plethora of plugins available for maven, this is only the tip of the iceberg. However, these main concepts will suffice for now.
90 90  
91 91  === Alternate File System Layout Concepts ===
92 92  
... ... @@ -160,6 +160,12 @@
160 160  
161 161  details to come...
162 162  
188 +=== Packaging Applications as True WAR ===
189 +
190 +You can find steps to package WO Applications as True WAR [[here>>Packaging WO Applications as true WAR with Maven]].
191 +
192 +more details to come...
193 +
163 163  === Project Inheritance ===
164 164  
165 165  details to come...