Skip to Content
Last modified by Henrique Prange on 2015/09/11 17:57
From version 24.1
edited by Lachlan Deck
on 2008/07/03 00:05
Change comment: Adding basic info and links for further info on project inheritance
To version 21.1
edited by Lachlan Deck
on 2008/07/02 23:41
Change comment: Adding example for building WOApplications

Summary

Details

Page properties
Content
... ... @@ -201,12 +201,6 @@
201 201  
202 202  {{/noformat}}
203 203  
204 -=== Project Inheritance ===
205 -
206 -It naturally gets a bit boring having to define the same things over and over again. So, you can utilise a parent pom file specifying its packaging as 'pom'. Dependencies, plugins and executions, resources specifications and so forth can be defined once and shared by any sub-modules. See [[http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance]] and [[Java World's The Maven 2 POM demystified>>http://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html]] for further information and examples.
207 -
208 -For our example we'll have trunk/pom.xml which will define everything common to any and all modules in the hierarchy. Likewise, trunk/frameworks/pom.xml and trunk/apps/pom.xml will define everything common to frameworks and applications respecively.
209 -
210 210  === Repositories ===
211 211  
212 212  So far we have assumed that maven just knows where to find third party libraries. There is the default local repository (e.g., /.m2/repository) and a remote one at ibiblio.org or a mirror of the same. See [[http://maven.apache.org/guides/introduction/introduction-to-repositories.html]].
... ... @@ -472,7 +472,7 @@
472 472   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
473 473   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
474 474   http://maven.apache.org/xsd/maven-4.0.0.xsd">
475 -
469 +
476 476   <modelVersion>4.0.0</modelVersion>
477 477  
478 478   <!-- parent artifact -->
... ... @@ -504,7 +504,7 @@
504 504   <artifactId>JavaWOExtensions</artifactId>
505 505   <groupId>${wonder.common.groupId}</groupId>
506 506   </dependency>
507 -
501 +
508 508   <!-- project libs -->
509 509   <dependency>
510 510   <artifactId>CustomExtensions</artifactId>
... ... @@ -514,7 +514,7 @@
514 514   <artifactId>CustomBusinessLogic</artifactId>
515 515   <groupId>${my.frameworks.groupId}</groupId>
516 516   </dependency>
517 -
511 +
518 518   <!-- webobjects dependencies -->
519 519   <dependency>
520 520   <artifactId>JavaFoundation</artifactId>
... ... @@ -545,7 +545,7 @@
545 545   <groupId>${webobjects.groupId}</groupId>
546 546   </dependency>
547 547   </dependencies>
548 -
542 +
549 549   <!-- build config (for modules) -->
550 550   <build>
551 551   <sourceDirectory>src</sourceDirectory>
... ... @@ -669,7 +669,7 @@
669 669   <artifactId>WOOgnl</artifactId>
670 670   <groupId>${wonder.common.groupId}</groupId>
671 671   </dependency>
672 -
666 +
673 673   <!-- general libs -->
674 674   <dependency>
675 675   <artifactId>jcaptcha-all</artifactId>
... ... @@ -692,6 +692,12 @@
692 692  
693 693  You can find steps to package WO Applications as True WAR [[here>>Packaging WO Applications as true WAR with Maven]].
694 694  
689 +more details to come...
690 +
691 +=== Project Inheritance ===
692 +
693 +details to come...
694 +
695 695  === Eclipse Integration ===
696 696  
697 697  details to come...