Error importing CS10 module into CS16

I'm trying to use the Eclipse plugin Import... > Source Code from OLL command to import a CS10 ospace into CS16. This worked fine with CS10.5.

However, it seems CS16 places all .os files into a single directory/package (i.e., things are no longer automatically grouped by package). This causes errors when multiple .os files have the same name. If the filenames match case-sensitive then one overwrites the other. If the filenames match case-insensitive then Eclipse throws an error and something like the following is written to the log:

!MESSAGE A resource exists with a different case: '/cs16projects/srcmodules/importtest/IMPORTTEST/MyNodeType.os'.

Is this a known bug? Any workarounds beside importing first into CS10.5 and then CS16?

Find more posts tagged with

Comments

AKropp

Hi Chris,

Yes, this is a known issue – tracking number is OIDE-964. I’d suggest you open a support ticket so we can gather your details and add them to the report.

I’m not aware of any better workaround at the moment. This one was actually reported by our good friend Appu Nair whom you may have seen on these forums once or twice If he’s managed to figure out something better maybe he’ll chime in here.

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, September 22, 2016 2:49 AM
To: eLink Recipient
Subject: Error importing CS10 module into CS16

Error importing CS10 module into CS16

Posted by Meyer, Chris On 09/22/2016 02:45 AM

I'm trying to use the Eclipse plugin Import... > Source Code from OLL command to import a CS10 ospace into CS16. This worked fine with CS10.5.

!MESSAGE A resource exists with a different case: '/cs16projects/srcmodules/importtest/IMPORTTEST/MyNodeType.os'.

Is this a known bug? Any workarounds beside importing first into CS10.5 and then CS16?

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

eLink User

Not much I am just following what the OT support person send me in email.I cannot but say to OT that you are letting down the programming community made up of independent OScript programmers.For people like me who relished looking at OT code and trying to design solutions it is almost a complete let down.I am sure somebody is going to post a reply to appease saying that I needed to contact OT with a bunch of logs and help them develop the IDE better,but I don't think that is practical.At least for the work I am doing which I am expected to do in a time that my company pays money for me,I usually don't want to get bothered saying to my supervisors "Hey the new IDE from OT is to blame" so I just fix it whatever tools I have(mostly builder code straightway works) and moves on.

It might be beneficial for more OT programmers in the development community to at least come out with best practices/advises/workarounds to any OScripter who may be wanting to enhance their CS investment but again gets completely clueless by countless errors.dump files and such like.I believe internally OT uses CSIDE correct , are all your programmers happy or have they not seen builder?Mostly for old grumpy people like me the ease with which we did this with builder may be the frustrating part,anyway that will come back?Come to think of it CSIDE 16 is much more stabler to me say for a few quirks maybe I will tide over it one day.

To answer Alex's comment I followed David Carpento's advise.If I see a module not directly importable in CS16 (well the bus is not about importing,but it losing out on old objects),I would do a Hop Step and Jump.Put them in CS10.5 and Jump into CS16.

I have a long list of workarounds on CSIDE dev ,I reported about 10 -12 bugs a year and a half back perhaps many of them are fixed.

Sorry for the strong words I never lose it but some things were left where they were...

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Thu, Sep 22, 2016 at 9:49 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

RE Error importing CS10 module into CS16 Posted byKropp, AlexOn 09/22/2016 10:48 AM

Hi Chris, Yes, this is a known issue – tracking number is OIDE-964. I’d suggest you open a support ticket so we can gather your details and add them to the report. I’m not aware of any better workaround at the moment. This one was actually reported by our good friend Appu Nair whom you may have seen on these forums once or twice If he’s managed to figure out something better maybe he’ll chime in here. AK From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, September 22, 2016 2:49 AM
To: eLink Recipient
Subject: Error importing CS10 module into CS16

Error importing CS10 module into CS16

Posted by Meyer, Chris On 09/22/2016 02:45 AM

I'm trying to use the Eclipse plugin Import... > Source Code from OLL command to import a CS10 ospace into CS16. This worked fine with CS10.5.

!MESSAGE A resource exists with a different case: '/cs16projects/srcmodules/importtest/IMPORTTEST/MyNodeType.os'.

Is this a known bug? Any workarounds beside importing first into CS10.5 and then CS16?

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Error importing CS10 module into CS16
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

Juliano_Ghisi

Hi Appu,

First of all, thanks for your participation here in the forum, as usual.

It is important to highlight that we have delivered a major version of Content Server (16) and also many teams have worked together to ship components for our Suites. All of them have used the CSIDE as a tool to successfully achieve their goals. Is it a perfect product? No and we are aware of it and we are working hard, especially for the next EP2 release, to make the necessary stability and performance enhancements.

The feedback from our developers are indeed very important, especially when bugs or blockers are in place. You mentioned that you have many workarounds, but if we don’t have more information about the problem we will never be able to fix or improve our tool.

One thing that is important to mention is that you may be experiencing a problem that we do not face internally, because of the different processes, tools, environments or scenarios that are different from what we are using or testing internally, that is why is very important to receive a feedback from external developers and keep the channel live.

I look forward to help as much as we can to make our product and your productivity better.

Best Regards

Juliano Ghisi