diff --git a/README.md b/README.md
new file mode 100644
index 0000000..5392990
--- /dev/null
+++ b/README.md
@@ -0,0 +1,25 @@
+Visual Source Safe - Jenkins plugin
+===================================
+
+[Jenkins](https://wiki.jenkins-ci.org/display/JENKINS/Visual+SourceSafe+Plugin) vss plugin
+
+Created this fork primarily with the intention of fixing the polling bug. JENKINS-10730
+
+In doing so, I tried upgrading the version of com4j which appears to work. I use this now at a client's
+site and have not had to restart Jenkins due to a memory leak.
+
+Building
+========
+Install [maven](http://maven.apache.org)
+
+then in root of these files type:
+
+ mvn package
+
+You should end up with `vss.hpi` inside the `target` directory which you can install in Jenkins as if
+you had downloaded it manually.
+
+I don't know how we go about getting this officially released as version 1.10? I don't want to be the
+maintainer as I'm only using VSS for a particular client and _hopefully_ won't be using it in the
+longer term.
+
diff --git a/pom.xml b/pom.xml
index 4788b36..f9879b4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -4,7 +4,7 @@
org.jenkins-ci.plugins
plugin
- 1.424
+ 1.466
vss
@@ -30,6 +30,10 @@
scm:git:ssh://git@github.com/jenkinsci/vss-plugin.git
https://github.com/jenkinsci/vss-plugin
+
+
+ UTF-8
+
@@ -40,7 +44,7 @@
org.jvnet.com4j
com4j
- 20070717
+ 20120426
diff --git a/src/main/java/scm/vss/VSSSCM.java b/src/main/java/scm/vss/VSSSCM.java
index 00a064f..01ad6b8 100644
--- a/src/main/java/scm/vss/VSSSCM.java
+++ b/src/main/java/scm/vss/VSSSCM.java
@@ -745,7 +745,7 @@ protected PollingResult compareRemoteRevisionWith(AbstractProject, ?> project,
{
//If this is the build then it deserves a build.
AbstractBuild, ?> lastBuild = (AbstractBuild,?>)project.getLastBuild();
- if(lastBuild == null)
+ if(lastBuild != null)
{
tl.getLogger().println("[poll] Last Build : #" + lastBuild.getNumber());
}