>How do you intend to manage both branches of the fork? svn branches? >Maybe creating a new "legacy" Maven module for one of them would be >clearer.
the plan was to use a svn branch for the "old SPI": [1] release would then be done both on the trunk (2.x) and this branch (1.x) versions. we are doing this already like this for the parallel maintenance of osgi-mock and sling-mock 1.x / 2.x. [2] and it works quite well. stefan [1] https://svn.apache.org/repos/asf/sling/branches/fsresource-1.1.x [2] https://svn.apache.org/repos/asf/sling/branches/testing/mocks/
