nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Importing an Oscript project

HFCDev

Hi,

I have some questions about importing an oscript project. A co-developer has created a CSIDE project and sent it to me. My Eclipse environment already has a few Oscript projects and one server project. I've imported the project. What do I have to do to a) build the project and b) get the new module to show up in staging? I've noticed that the Build Ospace menu item doesn't consistendly show up in my Oscript explorer.

I've noticed that I only seem to be able to have a CSIDE project in sync with a CS module if I am the one who created it and only if I install the module the instant it becomes available.

-Hugh

Find more posts tagged with

Comments

Darcy_Casselman

Hi Hugh,

Right now, they need to ship you the compiled module along with the source code. It's the same as what we were talking about earlier about recovering from a broken module: there is no way right now to build a module from scratch from the source.

(There are a couple hacks you could do though. Build OSpace works if it recognizes the parent folder as a module. (It's meant for building unit test ospaces which aren't in the module's ini file). So you can create a new module, put the source there and them build your ospaces. And then munge everything together afterwards).

Is this a huge, regrettable oversight? Yes, probably. In my defence, this is the first time in the 18 months or so people have been using CSIDE that someone's presented me with this problem. Most OScript development (at least at Open Text) is maintenance development of existing modules.

Still, no excuse. I'll see about getting something in the next update (Septemberish).

Darcy.

HFCDev

OK,

Assuming that I will have the compiled module, what should I be doing? Should I have the module installed first or should I import the project first? I've seen it where when I have both, the project and the module don't stay in sync. How can I make sure that they do? At this point, since the work has to get done, hacks are acceptable!

-Hugh

Olivier_De_Pooter

Installing the module will make it selectable for import to source functionality!

Mvg
Olivier De Pooter

Verstuurd vanaf mijn iPhone

Edit: make sure to always make changes in the source, then compile to update theinstalled oll and restart your thread.

Darcy_Casselman

Install the module, then import the project ("Import Existing Projects into Workspace"). Then run a clean build (Project > Clean...). That's probably best.

You don't need to worry about keeping them "in sync" because the ospace is built from the source. Your source is never updated by Content Server.

Except...

*DO NOT* use the Import Source Code from OLL wizard again if you already have the source. At the very least, you'll lose some comments and the indents will be a bit messed up. It's just generally not a good idea. Take care of your source code.

Darcy.

Darcy_Casselman

On second thought, I'm not sure how well "Import existing project into workspace" will work considering there isn't a good way to establish a link to a _server project outside of the create project dialog.

So you probably want to create the project with the create project dialog and then copy the source to the srcmodules folder.

HFCDev

This is what I ended up doing. I got rid of the src project, installed the module, then imported from the OLL into my own project. At that point, I was in sync. I did notice that if you have any other modules that are parts of other projects, those projects need to remain open until your module is uninstalled.

Perhaps there ought to be a Partner Webinar to go through all the finer points of CSIDE project management.

-Hugh

John W. Simon, Jr.

2nded, but don’t limit to just partners. There are a few non-partner oScripters still left ;-)

From: eLink Entry: Content Server IDE Development Forum [mailto:contentserver-ide@elinkkc.opentext.com]
Sent: Wednesday, June 18, 2014 4:45 PM
To: eLink Recipient
Subject: [EXTERNAL]Re RE Importing an Oscript project

Re RE Importing an Oscript project

Posted byhugh@hferguson.ca (Ferguson, Hugh) On 06/18/2014 05:44 PM

Perhaps there ought to be a Partner Webinar to go through all the finer points of CSIDE project management.

-Hugh

[To post a comment, use the normal reply function]
Topic:	Importing an Oscript project
Forum:	Content Server IDE Development Forum
Content Server:	Knowledge Center

Mark_Sherry

Until further notice, don't add OScript source projects to CSIDE via "Import Existing Projects into Workspace". The server project associated with the source project is part of the metadata that's imported, which leads to problems down the road when it tries to start up a CS instance based on a project that doesn't exist in your workspace.

To use somebody else's code, create a folder to store your source files, and copy the srcmodules folder over. Leave the .livelink and .project files - those include bits of information we don't want. Then create a new OScript Project, setting the project location to the folder you created (the one containing the srcmodules folder), and the OTHOME location to your CS instance.

We hope that one day this will no longer be necessary.