#1321 Bundle-Version of 3.0.0 annotations.jar is 2.0.3

[Andreas Sewe]

Not entirely sure who uploads the JARs under groupId com.google.code.findbugs to Maven central (http://search.maven.org/#search|ga|1|com.google.code.findbugs), but the 3.0.0 annotation.jar still has a Bundle-Version of 2.0.3.

[Andrey Loskutov]

Good catch.
I've fixed the code (see https://code.google.com/p/findbugs/source/detail?r=8b9f55b3ea833a253d891151913334d8dfa73127), but somebody needs to deploy this to maven repository.

[Tagir Valeev]

I updated the annotations.jar and committed the pom file here:
https://github.com/findbugsproject/findbugs/blob/master/pom/annotations/pom.xml
I made two bad attempts, so now artifact has 3.0.1u2 version. Nevertheless Bundle-Version for OSGI is 3.0.1. You can take then from here:
http://repo1.maven.org/maven2/com/google/code/findbugs/annotations/3.0.1u2/

Now it's independent on /findbugs/etc/MANIFEST-findbugs-annotations.MF file (manifest is generated automatically, all the necessary data is provided in POM). Among other changes:

• Separate proper artifacts generated for source, javadoc and jar
• Bundle-Version is updated to 3.0.1.
• jcip and jsr305 is automatically downloaded from maven, bundled with findbugs-annotations, repacked and deployed
• The whole deploy process is automatized: as long as you have Sonatype account with proper permissions and have gpg2 properly installed to attach a digital signature (Sonatype requires this), you may just run mvn clean deploy in pom/annotations directory to build and deploy the whole thing. Use mvn clean package just to build (skips digital signature, local installation and Sonatype deployment).
• It was necessary to remove the dependencies from Priorities and BugRanker classes defined in FindBugs itself, so I updated some annotations specifying the constants explicitly (with a proper comment).