Skip to content

Commit

Permalink
Remove references to old versions of the plugin (#55)
Browse files Browse the repository at this point in the history
* Remove references to old versions of the plugin
  • Loading branch information
elharo authored Mar 20, 2024
1 parent 5f79cd9 commit 3c830d7
Showing 1 changed file with 4 additions and 9 deletions.
13 changes: 4 additions & 9 deletions src/site/apt/supplemental-models.apt.vm
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,6 @@

Supplementing Missing POM Information

<<Note:>> This feature was added in version 1.0-alpha-5.

One of Maven's great strengths is that it allows you, the user, to build directly on the work of
others with minimal effort. For instance, by adding five lines (or less) to your POM, you can
declare a dependency on someone else's library, and instruct Maven to use that library during
Expand All @@ -40,12 +38,11 @@ Supplementing Missing POM Information
information critical to assembling licensing and dependency notice files.

For example, the templates used by many Apache distributions assemble a listing of project
dependencies according to their organization name (and URL), along with the URL each project's
dependencies according to their organization name (and URL), along with the URL of each project's
website. When dependency POMs are missing this information, the dependency notice file
that the Remote Resources Plugin renders can be invalid.

To compensate for incomplete dependency POMs, you can use the supplemental models support, introduced
to the Remote Resources Plugin in version 1.0-alpha-5, and improved in version 1.1.
To compensate for incomplete dependency POMs, you can use the supplemental models support.


* Fixing Incomplete POMs: Using Supplemental Models
Expand Down Expand Up @@ -146,14 +143,12 @@ From: Apache Software Foundation (http://www.apache.org/)

* Publishing and Reusing Supplemental Models

<<Note:>> This feature was added in version 1.1.

The configuration above is fine for single projects that need to address deficiencies in their dependencies'
metadata. But what happens when your organization wants to use these same deficient dependencies across multiple
projects? The configuration we just examined cannot handle reuse of supplemental-model files.

To address this shortcoming, version 1.1 of the Remote Resources Plugin introduces a new parameter:
<<<supplementalModelArtifacts>>>. When combined with the <<<supplementalModels>>> parameter used above, this new
To address this shortcoming, the Remote Resources Plugin includes the
<<<supplementalModelArtifacts>>> parameter. When combined with the <<<supplementalModels>>> parameter used above, this
parameter allows the Remote Resources Plugin to resolve artifacts containing supplemental model information, then
search those artifacts for the paths given in the <<<supplementalModels>>> listing.

Expand Down

0 comments on commit 3c830d7

Please sign in to comment.