Message-ID: <1661546121.211.1369153297645.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_210_450371507.1369153297645" ------=_Part_210_450371507.1369153297645 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Contains reimplementation of interpolation and model-cloning logic for p= erformance reasons.
Along with these, new functionality has been introduced that propagates = changes in the project state out to areas of the POM build section that wer= e originally specified as expressions, to keep references to project inform= ation such as build paths up to date with any changes to those values made = by plugins. This new functionality is termed build dynamism for now.
This new feature is meant to allow building only the projects inside the= current multimodule directory structure that the current project depends o= n, rather than forcing the user to rebuild the entire project tree. Of cour= se, ordering of this subset of projects should be calculated as if it were = part of the full reactor build, with dependency modules being built ahead o= f those modules that use them.
Review the other changes made for those that can be incorporated with su= fficient testing not to impact the release schedule for 2.1.0.
Having scanned JIRA I didn't find any others (@since and imp= lementation in plugins have been backported already), but will look at the = commit history =E2=80=93 Brett
This should be implemented, but needs some soak time to ensure all the k= inks are worked out. It should be straightforward to include this and spin = a new milestone release. I'm separating it from M1 mainly so we have an abs= olutely stable base in M1 from which to build. Other than fixing any issues= that may come from this, it should be a zero-cost move from the perspectiv= e of resource planning for the 2.1.0 final release.
This new feature will simply streamline the resolution of artifacts - pl= ugins, dependencies, etc. - to allow parallel download for artifacts that d= on't share the same groupId. The groupId distinction is important here, sin= ce it is the highest level at which Maven currently keeps metadata. Therefo= re, to avoid contention for access to these metadata files, all downloads w= ithin a groupId are managed serially as before.
This release will contain any stabilizing bugfixes for the features and = other modifications introduced during the milestone releases.