Use ee.j2se for bndtools.bndplugins
Build diagnostics
Additional diagnostic for failed remote resource downloading.
Set workspace location for p2 generation task
CLOSED - task 396: Repo name "Workspace" in -runrepos not recognised 
http://github.com/bndtools/bndtools/issues/issue/396
Fix NPE in AnalyseBundleResolutionJob
Don't force rebuild of  "-nobundles" projects
Generate workspace OBR index on demand from the resolver.
Don't regenerate workspace OBR index if no bundles have changed
Builder enhancement: check staleness of project before calling build
update echo ant target

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
OSGiRunLaunchDelegate: fix NPE

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
BundleSettingsWizardPage: fix NPE

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
fix findbugs warning: Check for sign of bitwise operation

Check for sign of bitwise operation in
  bndtools.editor.BndEditor.resourceChanged(IResourceChangeEvent)

This method compares an expression such as
  ((event.detail & SWT.SELECTED) > 0)
Using bit arithmetic and then comparing with the greater than
operator can lead to unexpected results (of course depending
on the value of SWT.SELECTED). If SWT.SELECTED is a negative
number, this is a candidate for a bug. Even when SWT.SELECTED
is not negative, it seems good practice to use '!= 0' instead
of '> 0'.

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
fix findbugs warning: Comparison of String parameter using == or !=

Comparison of String parameter using == or != in
  bndtools.editor.completion.BndSourceViewerConfiguration.getDefaultPrefixes(ISourceViewer, String)

This code compares a java.lang.String parameter for reference
equality using the == or != operators. Requiring callers to
pass only String constants or interned strings to a method is
unnecessarily fragile, and rarely leads to measurable performance
gains. Consider using the equals(Object) method instead.

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
fix findbugs warning: .equals(Object) does not check for null argument

  bndtools.diff.ClassInfo.equals(Object)
does not check for null argument

This implementation of equals(Object) violates the contract defined by
java.lang.Object.equals() because it does not check for null being passed
as the argument. All equals() methods should return false if passed a
null value.

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
fix findbugs warning: Possible null pointer dereference

Possible null pointer dereference of editResult in
  bndtools.editor.common.MapEntryCellModifier.modify(Object, String, Object)

There is a branch of statement that, if executed, guarantees that a
null value will be dereferenced, which would generate a
NullPointerException when the code is executed. Of course, the
problem might be that the branch or statement is infeasible and that
the null pointer exception can't ever be executed; deciding that is
beyond the ability of FindBugs.

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
add findbugs target to ant build

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
findbugs: filter out j2se jars

They cause false findbugs warnings.

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
Added plugin templates for URLConnector plugins.