Re: [Architecture] Deployable Artifact Model

2016-03-31 Thread Supun Sethunga
[+ arch@] Hi, IMO, we have to go with separate artifacts, for the easiness of maintainability. for eg: if we have separate artifacts (say for projects and analyzes), - One can easily add and remove analyzes at any time from a project, just by adding/deleting the file corresponds to that ar

Re: [Architecture] Deployable Artifact Model

2016-04-03 Thread Nirmal Fernando
+1 for separate artifacts. That would also help us to keep the same UI flow. On Fri, Apr 1, 2016 at 11:14 AM, Supun Sethunga wrote: > [+ arch@] > > Hi, > > IMO, we have to go with separate artifacts, for the easiness of > maintainability. for eg: if we have separate artifacts (say for projects >