I created a java project. Near as I can tell I associated it with our IFS network drive. When I open source through the same IFS filter, I still have the same issue. I go to the project and try to browse for source there and I see a src folder but it doesn't open. I tried selecting Source > Organize Imports. That gives me the following errors:
Problems while organizing imports on some compilation units. See 'Details' for more information.
IFS Java Source/Java/get_template.java: Compilation unit has parse errors. No changes applied.
IFS Java Source/Java/EMail.java: Compilation unit contains ambiguous references. User interaction required.
IFS Java Source/Java/msgsend.java: Compilation unit contains ambiguous references. User interaction required.
I am kind of worried that this is going to be copying the java source to my workspace instead of using it on the IFS.
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Thursday, May 20, 2010 9:08 AM
Subject: Re: [WDSCI-L] Using WDSCi to edit Java
On 5/19/2010 1:37 PM, David Gibbs wrote:
Kurt Anderson wrote:
Every so often I need to edit a java source (through a filter over
the IFS). However the context assistant doesn't working, I'm getting
the following error message: "This compilation unit is not on the
build path of a Java project." Well, I'm not working within a
project. Does anyone have any tips?
Try mapping the IFS location to a network drive and then create a java project there.
Then use the java perspective to edit, compile, & debug your code.
I'm with David - making a project over your existing code is much nicer
than the way I usually hack this up. I use Windows File Explorer to
navigate to the folder, open a command window (Windows Power Tools) and
edit via Code/400. Use the command window to javac and possibly test.
Do it David's way. The hairs on your head will thank you.
As an Amazon Associate we earn from qualifying purchases.