This plugin greatly reduces the pain associated with consistent packaging concerns across a large set of projects, or an entire organization. Any project can specify the use of a remote resource bundle and have the resources incorporated into their packaging. This means that you can create standard settings in a parent POM somewhere in the project hierarchy and have all projects use packaged common resources in a standard way like licenses, other legal notices and disclaimers, or anything else that may be common.

[top]

There are two solutions:

1. File bugs with the projects that produced those artifacts to get them to fix them. Also, file bugs with the Maven Evangelism project to have the Maven people enhance the metadata in the repository.
2. Use a supplemental data file. You can create a file that contains the missing metadata. For example:

                 <supplementalDataModels>
                   <supplement>
                     <project>
                       <groupId>com.sun.xml.bind</groupId>
                       <artifactId>jaxb-impl</artifactId>
                       <name>Sun JAXB Reference Implementation Runtime</name>
                       <organization>
                         <name>Sun Microsystems</name>
                         <url>http://www.sun.com/</url>
                       </organization>
                       <licenses>
                         <license>
                           <name>COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0</name>
                           <url>http://www.sun.com/cddl/cddl.html</url>
                         </license>
                       </licenses>
                     </project>
                   </supplement>
                 </supplementalDataModels>
              

   That location of that file can then be configured with the supplementalModels configuration element for the process goal. The supplemental information is merged with the information provided from the repository.

[top]