Message-ID: <1599447172.41750.1371675794692.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_41749_1527136015.1371675794691" ------=_Part_41749_1527136015.1371675794691 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This use case address the situation where a monolithic project n= eeds to be modularized with the ability to generate a consolidated jar that= mimic the current situation.
Download a sample of= this use case
Assuming that the project Foo has been split into 3 modules.
Each of the three modules have a jar packaging. The build gener= ates the main build as well as the sources using the source plugin. The foo-all project generates the cons= olidated build of the 3 modules (jar, sources and javadoc).
Main pom sample:
The 3 modules have their own configuration and dependencies. Each of the= m extends the main pom of the application (see above). For instance, a mini= mal pom for module-a would look like:
The foo-all is responsible of building the main application. It has a de= pendencies on the 3 modules (both the main build and the source archive). T= he consolidated build and source archive are generated by the assembly plugin. The Javadoc is generated on the fl= y by expanding the source archives.------=_Part_41749_1527136015.1371675794691--