davidbreitgand commented on issue #730: Multiple projects management
   @lionelvillard  I think that --override flag makes perfect sense. Also 
agreed that assets equality definition is required. Concerning explicit 
dependencies approach, assume that you have project A -> B and project C -> B, 
where -> means "depends on". For the sake of discussion, wskdeploy project == 
OW package. Furthermore, there is a an asset b in B. Now, suppose the user does 
wsk action update b blah-blah. How would that change propagate to  A and C? The 
dependencies are reflected only in the manifests of the respective projects, 
but nowhere in the OW data model, right? So, today the user will have to 
wskdeploy A and wskdeploy C. With multiple projects annotations on the asset, 
the user just does  wsk action update b carefree, because the dependencies of 
other projects on asset b are reflected in the annotations of the asset b.

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:

With regards,
Apache Git Services

Reply via email to