Re: [ptp-user] A command and a question about Synchronized Projects in I

[Corey Ashford <cjashfor@xxxxxxxxxxxxxxxxxx>]

Greg,

Thanks for the quick reply!

By the way, I should have mentioned that I'm working with Eclipse Indigo
RC1.

I just tried what you suggested, but I wasn't able to get it to work.
First, I cannot delete the existing include paths.  I was able to add
the remote path, as you suggested, but it didn't seem to "take".  The
path does show up in the list of include paths, at the top, but perhaps
something I didn't set up it correctly, because when I try to open the
twisty in the Includes tree of the project in the Project Explorer, it
shows no entries.  Furthermore, if I re-run the indexing operation, I
still get the local /usr/include/string.h file.

Two other things I'm finding:

1) Remote makes don't seem to work.  When I attempt it, I'm seeing this
error:

!ENTRY org.eclipse.core.resources 4 2 2011-05-17 17:12:05.902
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
!STACK 0
java.lang.NoClassDefFoundError:
org.eclipse.ptp.rdt.sync.core.BuildConfigurationManager (initialization
failure)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
	at
org.eclipse.ptp.rdt.sync.core.remotemake.RemoteMakeBuilder.invokeMake(RemoteMakeBuilder.java:317)
	at org.eclipse.cdt.make.core.MakeBuilder.build(MakeBuilder.java:101)
	at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
	at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
	at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
	at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
	at
org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:513)
	at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:422)
	at
org.eclipse.ui.actions.GlobalBuildAction$1.run(GlobalBuildAction.java:180)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


2) Quite frequently I'm seeing a hang condition where there are multiple
"Remote Synchronization" processes running in Eclipse, all of which
appear to be in a hung state, making no progress.  I'm seeing quite a
few Java stack dumps.  Here's a typical one:

sync failed:
org.eclipse.ptp.rdt.sync.git.core.RemoteSyncException:
        at
org.eclipse.ptp.rdt.sync.git.core.GitRemoteSyncConnection.syncLocalToRemote(GitRemoteSyncConnection.java:550)
        at
org.eclipse.ptp.rdt.sync.git.core.GitServiceProvider.synchronize(GitServiceProvider.java:264)
        at
org.eclipse.ptp.internal.rdt.sync.core.ResourceChangeListener$SynchronizeJob.run(ResourceChangeListener.java:71)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.eclipse.jgit.errors.TransportException: Invalid packet
line header: sh -
        at
org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefs(BasePackConnection.java:182)
        at
org.eclipse.jgit.transport.TransportGitSsh$SshPushConnection.<init>(TransportGitSsh.java:327)
        at
org.eclipse.jgit.transport.TransportGitSsh.openPush(TransportGitSsh.java:152)
        at
org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:130)
        at org.eclipse.jgit.transport.Transport.push(Transport.java:1120)
        at
org.eclipse.ptp.rdt.sync.git.core.GitRemoteSyncConnection.syncLocalToRemote(GitRemoteSyncConnection.java:546)
        ... 3 more
Caused by: java.io.IOException: Invalid packet line header: sh -
        at
org.eclipse.jgit.transport.PacketLineIn.readLength(PacketLineIn.java:193)
        at
org.eclipse.jgit.transport.PacketLineIn.readString(PacketLineIn.java:138)
        at
org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefsImpl(BasePackConnection.java:195)
        at
org.eclipse.jgit.transport.BasePackConnection.readAdvertisedRefs(BasePackConnection.java:176)
        ... 8 more

- Corey


On 05/17/2011 04:14 PM, Greg Watson wrote:
> Corey,
> 
> Thanks for your feedback!
> 
> I'll say a couple of things, then I'll let Roland and/or John (who have done most of the work) respond.
> 
> The original idea was not to replace Team support in Eclipse, but to provide a separate mechanism for supporting remote projects. So I had always envisioned checking out the project from CVS (or GIT or SVN) into my workspace, then converting to a synchronized project. This way, commits to the main repo would still be managed by the user through the Team interfaces, and the commits to the synchronized version would be purely for the purpose of keeping it in sync. However, that doesn't mean your suggestion to batch commits wouldn't be a useful option.
> 
> Regarding remote include files. I implemented a mechanism for supporting remote includes in CDT that is in the latest builds. However, we haven't managed to get this to work automatically with synchronized project yet, as it requires some integration with the remote scanner discovery (the thing that discovers what includes/defines are set on the remote system). I'm not sure if this will make it into 5.0 or not yet. However, in the mean time you can play with manually configuring remote includes. All you need to do is to open the project properties, go to C/C++ General Settings > Paths and Symbols. Then choose the build configuration you want to use. Click on GNU C and remove the existing paths. Then add new paths to the remote include directories using UNC notation (e.g. //<connection>/usr/include where <connection> is the name of the connection you specified for Remote Tools).
> 
> Hope this helps,
> Greg
> 
>