Hi all, I haven't had a lot of time to work on MercurialEclipse of late but have been beavering away at an extension and have a question about "packaging".
The extension will still take a little time to get into any useful state. It is a graphical changeset viewer that draws a graph of the changesets showing branches, merges, named branches, etc. The idea is to layout the changesets in a way that can enhance the users ability to understand what has been merged and where and to generally be able to explore the history of development. The project I'm working on we develop new product features and bug fixes on branches that are merged into the default or a release branch (or both) when testing of the feature shows that it is stable enough. So, we have *lots* of branches and merges and some branches have many changesets. I am using draw2d, gef and zest for the implementation and this leads to my question... If I put this directly into the MercurialEclipse plugin it introduces a new dependency for the plugin, any users will now need GEF and Zest loaded into their eclipse. Is this a problem or do I need to find a way to separate this (perhaps as an additional plugin?). I'm not sure exactly how to do this though. Much easier just to develop it directly in the existing plugin :-) thanks, brian wallis... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mercurialeclipse?hl=en -~----------~----~----~----~------~----~------~--~---
