On Tue, Feb 16, 2016 at 4:00 PM, Olivier Lamy <[email protected]> wrote: > ... > Pros: easy to understand for newbies
Easy to understand for developers, too. > Cons: no separation of concerns a release will be a release of all (is it > really a problem?) > I'd argue that the separation of concerns is still maintained by virtue of the separate subprojects, each having its own very specific purpose and scope. If we all endure some kind of head injury and vote to rewrite the C components in Java and merge everything into a single Maven mega-project, then we have problems. ;) In practice, our separating Guacamole into two (or more) repositories caused more problems than it solved. It lead to confusion when different versions were incompatible at the protocol level, complicated download procedures (the "Download" button on SourceForge gives you a text file containing instructions on how to download the components), and made it difficult to estimate the size of the Guacamole user community.
