Editing Archive:EclipseEpicPerlDebug (section)

== Set up your code in the IDE ==

=== Making changes to EPrints ===

If you are making changes directly to EPrints, you can start a new "Perl Project" in eclipse, and import the EPrints source code into it from the standard installation directory (something like /usr/share/eprints3/perl_lib).  You need to ensure that there is only one copy of the EPrints source files available to Apache, otherwise there is much scope for confusion.  Therefore, either copy the files in from the EPrints perl library to your IDE, and delete (or move) the original files out of the way, or set up your development environment's working directory as /usr/share/eprints3/perl_lib.  I would strongly recommend the former, as this will keep your EPrints directory free of development clutter.  Later we will configure Apache to point to your development environment for the EPrints source files, so nothing will break.

=== Adding your own modules external to EPrints ===

If you are coding a separate module which will use the EPrints modules as a set of dependencies, you should create a new "Perl Project" for your module, and place all your code in here.  I have found it useful to import the entire EPrints perl module as another Perl Project in Eclipse, and to set that on the "Perl Include Path" (see the next section).  In this way, when you ctrl-click on a package/module name, Eclipse will open the code in a new source tab, but the code which runs will still be the EPrints code in /usr/share/eprints3/perl_lib (unlike in the above section).  Later we will configure Apache to point to your development environment for the source of your new module, so it will be able to run alongside EPrints with no problems.

=== Configuring dependencies ===

To set up any external libraries upon which your project is dependent, right
click on the project name and select "Properties".  Go to "Perl Include Path"
and insert the path to the root of the perl modules which your code will
depend on.  This will allow Eclipse/EPIC to check for modules, functions, and so forth to aid code completion.