lionelvillard commented on issue #730: Multiple projects management
   The idea of the explicit dependencies approach is to have only one project 
which include all your dependencies. Only one project needs to be deployed (and 
wskdeploy can compute an optimal deployment plan). 
   Going back to the multiple projects management issue (in which dependencies 
are not explicitly specified and instead managed outside of wskdeploy), here I 
currently think what could go wrong and things to be aware of:
   -  if asset a in Project A and asset b in Project B have the same name but 
not identical (different code, parameters, etc...) then in general b cannot be 
deployed, otherwise it would break A. 
   -  consequently: if the purpose of B is to extends A (e.g. adding new 
actions to a package P), then both package descriptions P in A and B must be 
identical (same parameters, annotations, ...). 
   - comparing feeds for equality required adding additional annotations to 
store feed parameters.
   - comparing APIs should probably be done by comparing swagger specifications
   Bottom line: 
   - By default, deployment should fail when assets of the same name are 
different. A flag could be provided to override this behavior
   - Asset equality must be formally defined to support the default behavior 

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