Hi, Philip,
From the development perspective, I’m happy with however these bundles may be packaged and delivered in features, whether optionally installed or not.
It’s only in the development workspace that I have a concern, hence the focus on the Oomph setup model. I just need to be able to plausibly exclude them from a workspace that imports the other tooling bundles. And my patch achieves that. 😉 Thanks in advance for the review! There is absolutely no rush, because it’s working fine for me with the URI redirection to my local git (of course), and will continue to do so even through rebases.
On 12 July, 2016 at 12:52:08, Philip Langer (planger@xxxxxxxxxxxxxxxxx) wrote:
Hi Charles,
thanks for clarifying that!
So I understand that the feature in general is not optional
from a project plan point of view, but still could be made
available as an optional feature from a installation point of
view.
@development team of Papyrus-RT:
What are you thoughts on that, should the diff/merge support
be installed by default or just be available to be installed if
needed?
I'm open to both, of course. In case, you'd prefer the latter,
I just think we need to document the installation process on a Wiki
page or in another documentation.
Thanks for your input!
Best wishes,
Philip
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|