bbende opened a new pull request #155: NIFIREG-213 Second phase of extension 
registry work
URL: https://github.com/apache/nifi-registry/pull/155
 
 
   This PR includes the second phase of extension registry work which parses 
and extracts information about the extensions in a given NAR from the 
extension-docs.xml file produced by the NAR Maven-plugin - 
https://github.com/apache/nifi-maven/pull/8 .
   
   To test this PR you can do the following:
   - Build the latest NAR Maven plugin using the pull request above
   - Update NIFI to use the snapshot version of the NAR plugin (1.2.1-SNAPSHOT) 
and build NIFI
   - Run NiFi Registry from this PR and use the REST API to upload a NAR from 
the above build of NiFi
   - Follow the links in the "extensions/repo" API and navigate down to the 
version and follow the link to the "extension-metadata", this show the list of 
extensions in the given NAR
   
   Commit messages:
   - Implementing parser for extension-docs.xml file and integrating into the 
NarBundleExtractor
   - Incorporating build info into DB and appropriate entity/model classes
   - Added ProvidedServiceAPI to DB schema, entities, and metadata service
   - Added Restrictions to DB, entity classes, and metadata service
   - Refactored DataModelMapper into separate classes
   - Updated StandardExtensionService to persist ExtensionDetails to DB
   - Added link to extension-metadata from extension repo API
   - Updated NarBundleExtractor to extract additionalDetails content and raw 
content of extension-docs.xml
   - Added additionalDetails and extension-docs content DB schema and entities
   - Added some REST end-points for access extension metadata by bundle version

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to