Am 14.02.2013 um 11:03 schrieb Lukas Krejci:
While the location of the code and its versioning are basically
orthogonal
problems, IMHO, drawing the "repository boundaries" in our codebase is a very
strong suggestion of the essential independence of the pieces and hence hints
strongly at the intended versioning strategy.
And having the plugins in a separate repository with stable core components
to build against, makes it a lot easier for 3rd parties to build their own plugins
and/or enhance the existing ones.
And I understand the email from Elias that this would be the case for him.
That's why I wanted to bring it up while we're thinking about the migration
and the possible split. Because it can help us define the proper "demarcation
lines". That does not mean that we need to solve the versioning problem before
we do the migration though.
I don't think we should directly go to arbitrary numbering schemes - especially as
afaik the plugin(-container) can't say "I require jmx-plugin with version
4.7-5.3"