[egrubaugh]

We’re currently noticing two issues with the SuiteCloud IDE plugin.

First Issue – Creating NetSuite Projects from Existing Source appends Project name to Path

Our normal process for creating Projects in the SuiteCloud IDE is this: Create JavaScript Project from Existing Source
Convert to SuiteScript Project
Develop SuiteScript!

We do it this way rather than creating a SuiteScript project directly because of some unexpected (to us) behavior in the NetSuite Project creation wizard. We create all of our projects based on Customer and Environment from existing source in our SVN repository. Let’s say I have a brand new customer that I’m about to start a new project for in Sandbox. We’ll create a new folder in the repository, say it’s C:trunkNewCustomerSandbox, that will store all of the source for that customer’s Sandbox environment. Create a NetSuite Project
Project Name: “NewCustomer SB”
Location: C:trunkNewCustomerSandbox

I would expect this to create a new project with all of the source code that lives under C:trunkNewCustomerSandbox. Instead, it sets the project to look under “C:trunkNewCustomerSandboxNewCustomer SB”; the project name is appended to the path, which is undesired behavior for us. The project name should not have to have anything to do with the path of the source.

For now, we work around the issue by naming the project “Sandbox” and setting the Location to C:trunkNewCustomer, then renaming the project afterwards to be clearer.

Second Issue – Converting to SuiteScript Project seems broken in latest plugin version

In trying to follow our normal process outlined above, we’re encountering the following issue: Create JavaScript Project from Existing Source
Right click on project
Expand NetSuite context menu
Observe that the only menu option is “Revoke Master Password”

The same behavior exhibits when the project is simply a General Project instead of a Javascript Project.

We’re seeing this inability to convert projects in the following Eclipse and plugin version combinations on both Windows and Linux OS:Eclipse Kepler with plugin v2014.1_e3
Eclipse Kepler with plugin v2014.1_e4
Eclipse Luna with plugin v2014.1_e3
Eclipse Luna with plugin v2014.1_e4
This is a cached copy. Click here to see the original post.

[smehta]

The first issue seems like the standard Eclipse behavior. For the second issue it seems that you have installed the SuiteCloud IDE plugin for both versions of Eclipse 3.7 & 4.3. It is likely that because of the presence of the multiple versions of our plugin Eclipse may be having trouble. I suggest that you remove both the plugin and restart IDE (to ensure that cache, if any, is cleared) and then install the correct plugin version for your Eclipse.

Let me know if the problem persist.

[egrubaugh]

The last portion about installed versions was not saying I had them installed in the same version. Those were all separate installations of Eclipse, so I had two clean installations of Kepler one with e3 and one with e4, and likewise for versions of Luna. The issues were reproducible in all installations.

[kcng]

There’s a workaround to convert your JavaScript project into a SuiteScript project.

There should be a .project file in the project, modify it to look something like below, this should convert your project into a NetSuite project.

TEST_WOLF

org.eclipse.wst.jsdt.core.javascriptValidato r

com.netsuite.ide.eclipse.builder.suiteScript

com.netsuite.ide.eclipse.app.suiteScriptNa ture

org.eclipse.wst.jsdt.core.jsNature

[egrubaugh]

@kcng – Thanks; I’ll give that a shot ASAP and post back here with the result.

[egrubaugh]

kcng ‘s solution did work. The issue also appears to be resolved in the latest version of SuiteCloud IDE. I have not had any reported issues converting projects in months.

[Author]

Posts