Stefan Wagner
«Truth can only be found in one place: the code.»
Blog | Archive | Resume | Projects | References
Define your Architecture with Maven
03 May 2011 | maven, architecture
Maven is not just a build and dependency management tool, it also offers a way to define the architecture of your software. You can have your modules in layers such as a presentation, a business-logic and a persistence layer.
Lets suppose your architecture looks like the following image.
The maven root pom.xml defines the layers and the domain model, which is accessible on all layers.
<project>
...
<modules>
<module>athene-domain</module>
<module>athene-service</module>
<module>athene-ui</module>
<module>athene-store</module>
</modules>
...
</project>Now, you can define layer specific dependencies in a layer pom.xml. With this possibility your root pom.xml will be less crowded. I’ve experienced projects where the root pom.xml was totally full with declaration that it was hard to read the file.
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>ch.fhnw.business.iwi</groupId>
<artifactId>athene</artifactId>
<version>1.0.0</version>
</parent>
<artifactId>athene.service</artifactId>
<name>Athene Business Layer</name>
<description>Athene Business Layer</description>
<packaging>pom</packaging>
<modules>
<module>athene-service-model-api</module>
<module>athene-service-concept-api</module>
<module>athene-service-model</module>
<module>athene-service-view</module>
<module>athene-service-concept</module>
</modules>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-core</artifactId>
<version>3.0.1</version>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
</dependency>
</dependencies>
</project>The main structure looks as following. The source is available here.
athene
├── athene-domain
│ └── src
│ └── main
│ └── java
│ └── athene
│ └── domain
├── athene-service
│ ├── athene-service-concept
│ │ └── src
│ │ └── main
│ │ └── java
│ │ └── athene
│ │ └── service
│ │ └── concept
│ ├── athene-service-concept-api
│ │ └── src
│ │ └── main
│ │ └── java
│ │ └── athene
│ │ └── service
│ │ └── concept
│ │ └── api
│ ├── athene-service-model
│ │ └── src
│ │ └── main
│ │ └── java
│ │ └── athene
│ │ └── service
│ │ └── model
│ ├── athene-service-model-api
│ │ └── src
│ │ └── main
│ │ └── java
│ │ └── athene
│ │ └── service
│ │ └── model
│ └── athene-service-view
│ └── src
│ └── main
│ └── java
│ └── athene
│ └── service
│ └── view
├── athene-store
│ ├── athene-store-api
│ │ └── src
│ │ └── main
│ │ └── java
│ │ └── athene
│ │ └── store
│ │ └── api
│ └── athene-store-graph
│ └── src
│ └── main
│ └── java
│ └── athene
│ └── store
│ └── graph
└── athene-ui
├── athene-ui-concept
│ └── src
│ └── main
│ └── java
│ └── athene
│ └── ui
│ └── concept
├── athene-ui-metamodel
│ └── src
│ └── main
│ └── java
│ └── athene
│ └── ui
│ └── metamodel
└── athene-ui-model-oryx
└── src
└── main
└── java
└── athene
└── ui
└── model
└── oryx