Automatic check-out causes problems with putty: "Connection refused."-Dialog

[GoogleCodeExporter]

Projects containing the .svn folder show a Putty error: "Connection
refused". It is shown by the standard putty-exception-dialog. We have to
click the ok-button manually for every project, then the headless builder
continues the building. The projects were previously exported by the
subclipse-plugin in eclipse. We are using svn+ssh. The connection data is
stored in the eclipse workspace (not that, that is created by
headlesseclipse) and is not stored in the putty-program itself. This maybe
causes the problem.

1) Why tries headlesseclipse connect using putty to the svn-server? What I
can do, to suppress this functionality, except to remove the .svn folders?

2) A command "svn" would be nice, but it needs a setting file, where the
whole svn connection-data can be stored. In our opinion, an automatic
check-out should be disabled.

I'm using: Eclipse for RCP/Plug-in Developers, Build id: 20090920-1017, OS:
WindowsXP

Original issue reported on code.google.com by remi2...@googlemail.com on 20 Nov 2009 at 8:57

[GoogleCodeExporter]

As a short version I would say use export instead of checkout if possible, then 
there 
is no problem with .svn dirs. I dont know why this connection takes place, we 
will 
examine your issue, as soon as possible. Could you please attach the metadata 
of your 
projects? You may send it in email, if you do not want to attach here. We need 
the 
.project, .classpath, .settings folder.

Original comment by gabor.li...@gmail.com on 20 Nov 2009 at 9:19

[GoogleCodeExporter]

Thank you for your suggestion to use export and not checkout. :)

I have repeated this seconds ago:

Building startet by this build.bat:
@echo off
set ECLIPSE_HOME=C:\Programme\eclipse
set WORKSPACE=C:\Projekt\Java\AutoBuild
%ECLIPSE_HOME%/eclipsec -nosplash -data %WORKSPACE% -application
com.ind.eclipse.headlessworkspace.Application import clean build exportfeatures

The exception occurs on (projects renamed to shortening the names):

OPENING PROJECT: test
PROGRESS   0,00%: Opening 'test'.
PROGRESS   0,00%: Opening 'test'. Opening 'test'.

Then putty shows the Dialog "PuTTY Fatal Error" with the message: "Network 
error:
Connection timed out". So not "Connection refused", but this shouldn't matter. 
:)

#####################
.project
#####################
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
    <name>test</name>
    <comment></comment>
    <projects>
    </projects>
    <buildSpec>
    <buildCommand>
            <name>org.eclipse.jdt.core.javabuilder</name>
            <arguments>
            </arguments>
        </buildCommand>
        <buildCommand>
            <name>org.eclipse.pde.ManifestBuilder</name>
            <arguments>
            </arguments>
        </buildCommand>
        <buildCommand>
            <name>org.eclipse.pde.SchemaBuilder</name>
            <arguments>
            </arguments>
        </buildCommand>
    </buildSpec>
    <natures>
        <nature>org.eclipse.pde.PluginNature</nature>
        <nature>org.eclipse.jdt.core.javanature</nature>
    </natures>
</projectDescription>

#####################
.classpath
#####################
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" path="src"/>
    <classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.
launcher.StandardVMType/JavaSE-1.6"/>
    <classpathentry kind="output" path="bin"/>
</classpath>

#####################
.settings/org.eclipse.jdt.core.prefs
#####################
#Wed Nov 11 16:49:58 CET 2009
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.6
org.eclipse.jdt.core.compiler.compliance=1.6
org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
org.eclipse.jdt.core.compiler.source=1.6

Original comment by remi2...@googlemail.com on 20 Nov 2009 at 2:04

[GoogleCodeExporter]

Nothing special so far. Could you attach the output of our plugin as well? The 
system 
out you know.

Original comment by gabor.li...@gmail.com on 20 Nov 2009 at 2:29

[GoogleCodeExporter]

Parameters: [import, clean, build, exportfeatures]
"workspace" path variable has been set.

Auto building is set to false

ANT LOG: Listening on file: C:\Projekt\Java\AutoBuild\.build.log

Circular build path problems: error
Circular build path problems set to: error

Incomplete build path problems: error
Incomplete build path problems set to: warning

Setting the default JRE name to 'JRE' from 'jre6'

IMPORTING PROJECTS...
REFRESHING PROJECT: test
PROGRESS   0,00%:
PROGRESS   0,00%:  Refreshing '/test'.
...
PROGRESS 100,00%:  Refreshing '/test8'.

OPENING PROJECT: test9
PROGRESS   0,00%: Opening 'test9'.
PROGRESS   0,00%: Opening 'test9'. Opening 'test9'.
PROGRESS  19,00%: Opening 'test9'. Opening 'test9'.
PROGRESS  19,00%: Opening 'test9'. Refreshing '/test9'.
...
PROGRESS  98,00%: Opening 'test10'. Refreshing '/test10'.
PROGRESS  98,00%: Opening 'test10'.
PROGRESS 100,00%: Opening 'test10'.

OPENING PROJECT: test11
PROGRESS   0,00%: Opening 'test11'.
PROGRESS   0,00%: Opening 'test11'. Opening 'test11'.
<<< putty exception dialog open >>>

The first projects could be opened, but then all other projects show the error. 
I
thought that the projects I closed the exception dialogs for in the last build 
can be
opened this time. But this is not true. Also I compared the well opened 
projects with
a problematic one, there is no appreciable difference in .project, .classpath or
.settings/*.

Maybe this is an isue of subclise, which is installed in eclipse (sorry, no 
time to
test it now, maybe next week :)) Headlesseclipse uses the eclipse-installation 
so
maybe it uses subclipse too? If I create a new workspace in eclipse, I must 
change a
property of subclipse in Window/Preferences/Team/SVN/SVN-interface: Client from
JavaHL to SVNKit (Pure Java). Only after that change is done, subclipse is 
running
properly. It this change is not done, the same error occurs, that is discussed 
here.
Since Headlesseclipse is not changing this value (I suppose ^^), the isue 
occurs. But
I don't know, why Headlesseclipse (or one of the used eclipse builders) want to
connect to SVN.

Original comment by remi2...@googlemail.com on 20 Nov 2009 at 3:57

[GoogleCodeExporter]

OK, one more idea, why headlesseclipse connects to SVN: because the subclipse 
plug-in
is installed, if a project is opened which contains valid SVN-data, the package
explorer updates his label provider to show the SVN-info. (Just install 
subclipse,
and you will see, what I mean.) Maybe this subclipse verrifies the 
SVN-connection so
if the settings of subclipse are wrong (which is the default case on our 
machines on
new fresh workspaces), the error occurs. Because headlesseclipse openes the 
projects,
an open-event listened by subclipse can cause this problem.

I would say, this all is not the fault of the headlesseclipse plug-in. Maybe 
there is
a way to import settings, that will be append to the new created workspace by
headlesseclipse? Or you load only that plugins you need for building. Or I'm 
using a
fresh install of eclipse without subclipse :) (But now no time to test this)

Original comment by remi2...@googlemail.com on 20 Nov 2009 at 4:16

[GoogleCodeExporter]

First of all, thank you for your work to investigate this issue. Your idea 
seems to be 
right. Since Eclipse is not capable to be run in headless mode without GUI, we 
need to 
start a fake GUI as mentioned in wiki. SVN plugin can be the responsible as you 
said. 
The simple solution is to remove SVN plugin from the Eclipse you use for 
creating 
headless builds. Please inform us about your test, and after the results, we 
will 
display it in a "known issues section"

Original comment by gabor.li...@gmail.com on 20 Nov 2009 at 9:32

[GoogleCodeExporter]

After testing, now I'm sure: subclipse is the problem. Like I said before the 
SVN
client setting has to be changed in the workspace to avoid the error. This also 
can
be done simply by removing "org.tigris.subversion.clientadapter.*javahl*" from 
the
plugin-directory of eclipse. Then a new created workspace will automatically 
pick the
svnkit pure-java client adapter and the error will disapear. Or even simplier: 
remove
subclipse from eclipse used for headless building. :)

Original comment by remi2...@googlemail.com on 23 Nov 2009 at 11:16

[GoogleCodeExporter]

Thanks, I will update then the user manual.

Original comment by gabor.li...@gmail.com on 23 Nov 2009 at 11:28

• Changed state: WontFix