Nesh has asked for the wisdom of the Perl Monks concerning the following question:

Hello Monks I don't know whether this question can be posted here or not but still I expect some help. I am using EPIC (Eclipse IDE for Perl). Now I have two scripts which are in two different folders. When I open a project in Eclipse and import these two scripts and make any changes then the changes are local to the Eclipse Workspace. So every time I have to copy the scripts from Eclipse workspace back to the respective folders and then test them. Is there a way to import the scripts in Eclipse so that whatever changes I make to the scripts the changes reflect in the respective folders instead of just the Eclipse Workspace. Please help. Thanks

Replies are listed 'Best First'.
Re: Eclipse (EPIC) IDE usage help
by jimbojones (Friar) on Jun 07, 2005 at 02:43 UTC
    Hi

    There are two methods you can use. You can define the project to be in the location where the scripts are.

    1. Select a New Perl Project. Name it
    2. Uncheck "Project Contents -- Use Default".
    3. Browse to the location where your scripts are. Create the project there.
    Your scripts should be available by default in the new project. The only downside is that Eclipse will leave a '.project' file in the folder where the scripts are.

    The second method is to create a folder link from the existing project in your workspace to folder locations.

    1. Highlight your project in the Navigator View
    2. Right-click, select New -> Folder
    3. Name the folder
    4. Click the "Advanced >>>" button
    5. Check the "Link to Folder in the file system" check box.
    6. Browse to the folder where your scripts are.
    This is under Eclipse 3.0, EPIC 0.3.10

    - j

Re: Eclipse (EPIC) IDE usage help
by joelnackman (Beadle) on Jun 07, 2005 at 02:49 UTC
    If you go into the new file dialog, and hit the "Advanced..." button, there is an option called "Link to file in the file system".
    That will let you have the changes effect a file somewhere other than the Eclipse workspace.
    I wasn't sure if that was what you were asking, but if it is, that should work.

    Sorry to repeat, jimbojones replied while I was typing.
      No need to be sorry. Getting the same advice from multiple people helps demonstrate that it's a common solution, which is useful to know.