Re: Problem in Plug-in perspective of WDSC - build path issue with com.ibm.etools.iseries.core

I've got a strange problem with a plug-in project that I am working on. I have the project installed on both work and home PC and sync them using SVN.

On one box, the projects happily builds in the workspace, but on the other computer I get a number of "The import xxxxx cannot be resolved" errors, but only on a bunch of "com.ibm.etools.iseries.core." classes.

Both machines are @ version 7.0.0.4 (Internal Version 7.0.0.20071003_2001) of WDSC

On the box with the errors I can resolve these errors by explicitly adding the iseries.jar and iseriesminers.jar files from the "com.ibm.etools.iseries.core_7.0.3.v200706281458/runtime" folder as external archives to the build path of the project, but I don't believe I should need to do that.

After searching for a long long time I have found one difference between the 2 boxes that is probably causing this issue, but I have no idea how to fix this.

The working box actually lists both the iseries and iseriesminers jar files explicitly in the build path under the "Plug-in Dependencies" but the non-working version does not. In that version it instead has an entry on that list that looks like this:

com.ibm.etools.iseries.core_7.0.3.v200706281458.jar - F:\Program Files\IBM\SDP70Shared\plugins\

(which also contains those 2 jar files)

So it looks like the working box is able to somehow detect those 2 individual jar files, but the other box isn't...but I am lost as to why that may be.

I've used the -clean startup option and all kinds of removal and re-adding of dependencies etc numerous times, but all to no avail. Even created a brand new WDSC installation package, but the problem stays the same

So I am hoping anyone on the list has an idea?