davidbreitgand commented on issue #730: Multiple projects management
   @pritidesai This is exactly what we had in mind. @lionelvillard The 
functionality we want to achieve is that there will be only one copy of an 
annotated asset that when updated retains connections to the projects that it 
is managed by. It's our understanding that creating a library asset is a 
possible solution, but with the current implementation, if the user updates the 
library asset, she will need to call wskdeply for each project that has 
dependency on that asset and the asset will be overwritten N times in the DB, 
where N is the number of projects. Having an array of annotations, as 
@pritidesai suggests seems to be a faster and cleaner way of achieving the 
result. Thoughts? 

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