It's all about the answers!

Ask a question

Problem debugging RTC code.


Jose Miguel Ordax Cassa (2.4k4126100) | asked Jul 13 '09, 7:10 a.m.
Hi, I am starting to play with RTC SDK 2.0 and I followed theoretically
all the indications of:
https://jazz.net/wiki/bin/view/Main/RTCSDK20_DevelopmentEnvironmentSetup
(Running as an Eclipse plug-in).

Snippets work fine, but when I try to get into RTC code I get a class
file opened in the editor saying: Source not found. The JAR of this
class file belongs to container 'Plug-in Dependencies' which does not
allow modifications to source attachments on its entries.

Any help?

Thanks in advance,

Chemi.

4 answers



permanent link
Jose Miguel Ordax Cassa (2.4k4126100) | answered Jul 13 '09, 7:43 a.m.
Chemi wrote:
Hi, I am starting to play with RTC SDK 2.0 and I followed theoretically
all the indications of:
https://jazz.net/wiki/bin/view/Main/RTCSDK20_DevelopmentEnvironmentSetup
(Running as an Eclipse plug-in).

Snippets work fine, but when I try to get into RTC code I get a class
file opened in the editor saying: Source not found. The JAR of this
class file belongs to container 'Plug-in Dependencies' which does not
allow modifications to source attachments on its entries.

Any help?

Thanks in advance,

Chemi.

Ok. Fixed... problem was that although I used Cygwin unzip tool, I
uncompressed the ZIP files in a directory structure where most of the
files couldn't be extracted because Windows length path restrictions. So
I had to uncompress it at \tmp folder which is just three characters.

Nevertheless, there were several problems extracting some files related
to JUnit so it seems it is impossible to extract 100% of the content in
Windows platform.

Have you seen the same behavior?

Thanks in advance,

Chemi.

permanent link
Jose Miguel Ordax Cassa (2.4k4126100) | answered Jul 13 '09, 7:59 a.m.
An example:

unable to process
source/rtc/eclipse/plugins/com.ibm.team.filesystem.feature.ide.source_2.0.0.I200905130131-7L--_MdJT9PBdBg_rI_UCQ9HBD/src/com.ibm.team.filesystem.setup.junit_2.0.0.I200905130131/junit-src/JUnitExamples/src/junit/samples/money/MoneyBag.java.
checkdir error: cannot create
source/rtc/eclipse/plugins/com.ibm.team.filesystem.feature.ide.source_2.0.0.I200905130131-7L--_MdJT9PBdBg_rI_UCQ9HBD/src/com.ibm.team.filesystem.setup.junit_2.0.0.I200905130131/junit-src/JUnitExamples/src/junit/samples

As sources should be copied at: /jazz/client/eclipse, the total string
is more or less 240 characters plus the name of each file almost 250
which is the maximum.

I created an installation directory of just one character. So I just add
one character to the default packaging. And it still failing with some
files as shown at the beginning (which seems to be related to JUnit
samples and perhaps are not important). But it seems more or less
impossible to use Windows and RTC SDK without errors.

Regards,

Chemi.

permanent link
Michele Pegoraro (1.8k14119103) | answered Jul 13 '09, 9:50 a.m.
Not all the extractor can use long path. I've used 7zip as suggested and it works fine. I suggest you to try it.

permanent link
Jose Miguel Ordax Cassa (2.4k4126100) | answered Jul 13 '09, 10:18 a.m.
mikyjpeg wrote:
Not all the extractor can use long path. I've used 7zip as suggested
and it works fine. I suggest you to try it.


Well in this case I was using Cygwin which I think hasn't the problem
(in fact, that was the reason I got some sources that I didn't get using
Windows zip support).

The problem now I think is a restriction by Windows itself to contain
long paths (not just the restriction of the extractor tool). Do you have
that
.../source/rtc/eclipse/plugins/com.ibm.team.filesystem.feature.ide.source_2.0.0.I200905130131-7L--_MdJT9PBdBg_rI_UCQ9HBD/src/com.ibm.team.filesystem.setup.junit_2.0.0.I200905130131/junit-src/JUnitExamples/src/junit/samples/money/MoneyBag.java
file in your Windows box? Can you post the full path to it?

Thanks in advance,

Chemi.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.