You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/04/13 18:29:36 UTC

[GitHub] klcodanr commented on issue #113: Improve Maven/Java Tooling

klcodanr commented on issue #113: Improve Maven/Java Tooling
URL: https://github.com/apache/incubator-openwhisk-devtools/pull/113#issuecomment-381223141
 
 
   So I looked into wskdeploy, looks like a really nice toolset. I was wondering how it would handle if you wanted one or more modules to contribute to a single package? I'm thinking of a case where you'd have some pretty significant dependencies for a set of actions which you don't want to bloat other actions with. 
   
   The best solution to me would be to support two different mojos:
   
    - Scan (or something like that) - gather up all of the classes in some identified location and evaluate their annotations
    - Update - write out the YAML manifest file and optionally install it into OpenWhisk
   
   so your project could look something like:
   
   - reactor
     - module 1 (action 1, 2) (scan)
     - module 2 (action 3, 4) (scan)
     - module 3 (update) 
   
   The artifact for module 3 can then be a ZIP file containing the manifest YAML and all of the previous artifacts required to build it.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services