Jump to: navigation, search

Buckminster Maven Reader

< To: Buckminster Project
The maven Component Reader is based on the url.catalog reader that lists all available jar-files in a directory to determine best version. Extended with functionality that maps component names to the maven specific groupId and artifactId.

Plugin

The maven plugin is based on the url.catalog plugin - See URL Catalog Reader. The maven reader does not yet support all maven 2.0 features.

Supplying username and password for maven repository access

The maven provider allows you to supply username and password via properties, or directly in the url, to access the repository. Via url you would have something like the following in your rmap.

 <searchpath name="maven">
   <provider source="false" mutable="false" componenttypes="osgi.bundle" readertype="maven2" xsi:type="mp:MavenProvider">
     <uri format="http://username:password@my.hosted.maven.repo/repos/public/"></uri>
     <mp:mappings>
       <mp:entry ...
        ...
      </mp:mappings>
    </provider>
 </searchpath>

Since buckminster 1.5.0.v20130207-0733

Obviously you might not want your credentials in plain text in the rmap. To accommodate this you can pass your credentials via property elements, using keys 'maven.username' and 'maven.password'. The values can be property references which you can pass to the rmap through the usual property mechanisms (rmap, cquery, property file etc). This can be done as follows:

 <searchpath name="maven">
   <provider source="false" mutable="false" componenttypes="osgi.bundle" readertype="maven2" xsi:type="mp:MavenProvider">
     <bc:property key="maven.username" value="${my.maven.username}" />
     <bc:property key="maven.password" value="${my.maven.password}" />
     <uri format="http://my.hosted.maven.repo/repos/public/"></uri>
     <mp:mappings>
       <mp:entry ...
        ...
      </mp:mappings>
    </provider>
 </searchpath>

More maven information needed - and examples