Brett and others, I rolled back MI to Java5, but I agree, due to API breakage I did bump the version to 5.0.0-SNAPSHOT.
https://github.com/cstamas/maven-indexer/commits/fixes As for "consumer" side code, few examples: Maven Indexer Examples updated to represent needed changes (commented on API changes for clarity sake, but I had some reformats happening too, sorry for that): https://github.com/cstamas/maven-indexer-examples/commit/eb38e442889d072d380c8fb18e5f35a5dd372076 Other example might be Nexus itself, here is a branch (from yesterday, where MI version is still 4.5.0-SNAP but API is already the same as in 5.0.0-SNAP): https://github.com/sonatype/nexus/commit/e8301d4cf93b7dba5d10988124696262b1786433 As you see, the "API breakage" actually depends very much on how you use MI, as for example Nexus code _had no changes_ (only one UT doing low-level stuff to bring index into some specific state). If you did not tamper with "low level" access of it by using IndexSearcher directly, you might be lucky and need no change at all :) Thanks, ~t~ On Thu, Aug 9, 2012 at 2:33 AM, Brett Porter <br...@apache.org> wrote: > I don't have a problem with updating it if there's something useful to > take advantage of, knowing the user-base of the library. In other > libraries, we don't need to upgrade just for the sake of it, of course. > > Perhaps with this requirement, and the API breakage you indicated, the > version could bump to 5.0.0-SNAPSHOT? I like the semantic versioning rules ( > semver.org). > >
