Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@178545 13f79535-47bb-0310-9956-ffa450edef68

This commit is contained in:
John Dennis Casey 2005-05-25 22:51:13 +00:00
parent 9401fbb6b0
commit b8042e780d
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
maven-site/src/site/xdoc/developers/plugin-overview.xml
View File

@ -78,9 +78,19 @@
<p>Also starting with Maven 2.0 is an effort to integrate multiproject
builds directly into the core architecture. In Maven 1.x, many large
projects were fragmented into smaller builds to sidestep issues such
as conditional compilation of a subset of classes; separation
of client-server code; or cyclical dependencies between
distinct application libraries.</p>
as conditional compilation of a subset of classes; separation of
client-server code; or cyclical dependencies between distinct
application libraries. This in turn created extra complexity with
running builds, since multiple builds had to be run in order to build
the application as a whole - one or more per project. While the first
version (1.x) did indeed address this new multiple projects issue, it
did so as an afterthought. The Reactor was created to act as a sort
of <i>apply-to-all-these</i> function, and the multiproject plugin
was later added to provide Reactor settings for some common build
types. However, this solution (it <i>is</i> really only one solution,
plus some macros) really never integrated the idea of the
multi-project build process into the maven core conceptual
framework. </p>
</subsection>
<subsection name="Why Change the Plugin Architecture?">
</subsection>