Is there a way to point Eclipse to a remote CVS

Thread view:

Deodiaus - 01 Jul 2008 00:40 GMT

I am trying to debug code from jgears.sourceforge.org.
I have the class files in a jar, but I would just like to be able to
point to the remote CVS repository when I am stepping through the
code. Is this possible, or do I have to recompile and link that
project?

Reply to this Message

Lew - 01 Jul 2008 02:16 GMT

> I am trying to debug code from jgears.sourceforge.org.
> I have the class files in a jar, but I would just like to be able to
> point to the remote CVS repository when I am stepping through the
> code. Is this possible, or do I have to recompile and link that
> project?

CVS is *pre-* source, that is, it is unaffected by the compilation and linking
(?) of your project, which are *post-* source. Your Java relies on your
repository; your repository doesn't rely on your source. It's strictly a
one-way dependency.

You can point to a remote source-code repository, but that will not be dynamic
during debugging. It sounds like you want to step through the code live from
the repository - correct me if I'm wrong since you didn't actually say that.
If that is what you want, I don't know of any way to do it, and I wouldn't
recommend it if I did.

You point Eclipse to a remote repository by setting the project from CVS in
the first place. I went to the "New Project" wizard and selected "CVS /
Projects from CVS", then "_N_ext". It opened up a dialog that let me specify
any CVS repository for my source.

You didn't give enough information in your post, so I went to
<http://sourceforge.net/cvs/?group_id=118950>
and read up on what they say about CVS access. Have you read this page?

The repository is at jgears.cvs.sourceforge.net, specifically

:pserver:anonymous@jgears.cvs.sourceforge.net:/cvsroot/jgears. I transcribed

that information into the appropriate textboxes in the New Project wizard,
gave "anonymous" as the user, and clicked "_N_ext".

For the "_s_pecified module name" I used 'jgears-1.1', but I could have chosen
"Use an existing _m_odule". Then I asked Eclipse to "Check out as a _p_roject
in the workspace", giving it the name 'jgears-1.1'. (I also left "_C_heckout
subfolders" checked.) "_N_ext". "Use default _w_orkspace location".
"_N_ext". "_F_inish".

This gave me an Eclipse project which I could use for browsing during debugging.

Signature

Lew

Reply to this Message

Deodiaus - 01 Jul 2008 23:29 GMT

Thank Lee.
The problem I really have is that JGears will not build clean. There
are missing files (JGHidden) as well as hard coded paths which need to
be fixed.
Ideally, I would just like to be able to copy the JGear jar files to
where they are ultimately built, so that I could step throught them
with the debugger, and not worry about building the project.
I went so far as to use Jad to decompile the missing files, but this
needs to be automated in some way.

> --
> Lew

Reply to this Message

Lew - 02 Jul 2008 02:07 GMT

> Thank Lee.

That's "Lew".

> The problem I really have is that JGears will not build clean. There

It built fine for me once I fixed the lines in the build.xml at the top that
referred to hard-coded paths. I simply made them relative and everything just
built.

> are missing files (JGHidden) as well as hard coded paths which need to
> be fixed.

I didn't have any problem with missing files. The hard-coded paths in the
build.xml were easy to fix - I just matched the actual project structure and
made them relative to the directory in which I had the build.xml. It took
about one minute.

> Ideally, I would just like to be able to copy the JGear jar files to
> where they are ultimately built, so that I could step throught them
> with the debugger, and not worry about building the project.

How would you be certain the JARs matched the source if you didn't build them?

> I went so far as to use Jad to decompile the missing files, but this
> needs to be automated in some way.

How can you decompile missing files? Doesn't the fact that they're missing
get in the way of that?

Signature

Lew

Reply to this Message

Deodiaus - 03 Jul 2008 01:55 GMT

> Deodiauswrote:
> > Thank Lee.
>
> That's "Lew".

Sorry, Lew!

> > The problem I really have is that JGears will not build clean. There
>
> It built fine for me once I fixed the lines in the build.xml at the top that
> referred to hard-coded paths. I simply made them relative and everything just
> built.

Ok, I set
src.home value='projects'
doc.home value='projects/docs'
cvs.home value='projects'

or should I use
src.home value='./projects'
which says to start from the current dir, e.g /home/workspace/
jgears1.1
and give me the error

BUILD FAILED
/home/workspace/jgears-1.1/build.xml:35: The following error occurred
while executing this line:
/home/workspace/jgears-1.1/projects/jgears-framework/build.xml:5: The
following error occurred while executing this line:
/home/workspace/jgears-1.1/projects/jgears-framework/core/build.xml:
26: /home/workspace/jgears-1.1/projects/jgears-framework/core/projects
not found.

Total time: 1 second

Reply to this Message

Lew - 03 Jul 2008 02:46 GMT

> Ok, I set
> src.home value='projects'
[quoted text clipped - 5 lines]
> which says to start from the current dir, e.g /home/workspace/
> jgears1.1

> and give me the error
>
[quoted text clipped - 8 lines]
>
> Total time: 1 second

Ah, yes, I do get that error once I select the 'build' target instead of the
'replicate' target.

I guess there's some work needed on the build.xml files.

Signature

Lew

Reply to this Message

Deodiaus - 12 Jul 2008 07:18 GMT

A simpler question, should I use

> > src.home value='projects'
> > doc.home value='projects/docs'
[quoted text clipped - 3 lines]
> > src.home value='./projects'
> > which says to start from the current dir, e.g /home/workspace/jgears1.1

or are they equivalent?
Is there a time when they might not be and the later form is
preferred, e.g. the current dir is not in your path?

Reply to this Message

Is there a way to point Eclipse to a remote CVS

Free Magazines