Fixed NPE on jar/war files without manifest
Allowing preparedPaths to be true even if there are errors.

This change means that if there are TONS of errors, the project won't be
reprocessed over and over and over again. A simple way to see where
this would be a problem is if you had many projects that included
each other in their buildpaths. Now remove one of the foundational
projects from your workspace -- actually delete the files, not
just delete the eclipse project. the Project class will get hung up
because it continues to process all Projects because none of them
are ever "Ok".
R6 package for the annotations. The code uses
strings (and had 3 error before I got the string right, long
live Java). So the package is only in the test code
#477 The method's return type was interpreted as raw type
bnd diffing only looked at the raw type of a return. It now uses
the generic signature of the return type. This will now
give a diff on a change from Collection<String> to 
Collection<Integer>. Since it uses the string representation
of the signature, Due to lack of time, I use the binary
form of the signature. So messages might look awkward. On the 
TODO list ...
Extra tests
Replace \n,\r,\b,\f,\t 's in the output of the macro processor
with the their real control code. This allows macros to generate
newlines.
Merge pull request #458 from KnisterPeter/master

Fixed NPE on jar/war files without manifest
#457 Exception in annotation handling
Turned out that the elements map was set to the Collections.empty() if there were no elements in the original annotations. This created an error when we tried to set a new value. Now use null for elements and will create a map when needed.
close
Support @1.2 as [1.2,2) and 1.2@ as [1.2,1.3)
Merge pull request #472 from derheld42/allowpreparepathstrue

Allowing preparedPaths to be true even if there are errors.
oops
Documentation