Re: How can I setup a dev environment for OTRS?

Hello Iosif, i hope to help I took a doc that I realized, after a hard 
work, which describes the steps necessary to get to debugging modules of 
OTRS in ECLIPSE whith EPIC.
I'm sorry but the doc is the automatic translation of google (Italian-> 
English).
Goo

Take this opportunity to ask if anyone has implemented or has been 
required to develop code to integrate in ITSM data  OCS Inventory 
(especially accuntinfo of OCS)

Bye
Rocco


I attach a doc that I realized, after a hard work, which describes the 
steps necessary to get to debugging modules OTRS.
I'm sorry but the doc is the automatic translation of google (Italian-> 
English)
Hello

Il 11/09/2012 9.56, Bogdan Iosif ha scritto:
> Thanks, I'll look into it.
>
> On Tue, Sep 11, 2012 at 10:40 AM, Rocco Tocci <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     Hello, following this guide I was able to debug OTRS.
>
>
>     http://www.epic-ide.org/downloads/EPIC_User's_Guide.pdf
>     <http://www.epic-ide.org/downloads/EPIC_User%27s_Guide.pdf>
>
>     I agree that it is important to have a debugging because perl has
>     a number of environment variables difficult to know the contents
>     of the trace or with logs or other
>
>     Bye
>     Rocco
>
>
>     Il 11/09/2012 9.09, Bogdan Iosif ha scritto:
>>     Thanks for the input.
>>
>>     I was "afraid" of that. I'm familiar with this type of debugging
>>     from writing shell scripts running under Jenkins but I've never
>>     done debugging like that for a code base as large as OTRS seems
>>     to be.
>>
>>     With shell scripts it was, kind of, simple to assess if the code
>>     is valid because I knew exactly where the script will be invoked
>>     from and my only concern was to explore the context of the call
>>     (mainly env vars). With these Perl scrips, without an IDE that
>>     halts execution on a breakpoint or a possibility to statically
>>     explore all callers on an object's method, I find it hard to
>>     imagine how I can ensure a change I make on some of the code OTRS
>>     ships with will not break some code paths or, worse, produce
>>     undesirable side effects.
>>
>>     I assume you mean Apache HTTPD's STDERR. I'll try to setup Fred.
>>     I hope this info is still valid
>>     (http://lists.otrs.org/pipermail/dev/2007-October/001728.html)
>>     because I haven't found much else in the form of a guide on how
>>     to use / install it.
>>
>>     /bogdan
>>
>>     On Mon, Sep 10, 2012 at 12:40 PM, Michiel Beijen
>>     <[email protected] <mailto:[email protected]>> wrote:
>>
>>         Hi,
>>
>>         Setting up the 'dev' environment is pretty much the same as
>>         setting up
>>         a 'regular' OTRS environment; you would set up an OTRS
>>         environment
>>         including database and web server on your local machine.
>>
>>         For editing the files you can use pretty much any editor,
>>         some people
>>         use complete IDE's such as ActiveState's Komodo IDE, Eclipse
>>         EPIC or
>>         similar, or Padre, some people prefer to use text editors
>>         such as vim
>>         with lots of plugins, or even simply Notepad++.
>>
>>         If you do OTRS development you typically do not use a
>>         debugger all
>>         day; and inspecting elements can be achieved by printing them to
>>         STDERR and looking in the server error log and/or using Fred
>>         (http://ftp.otrs.org/pub/otrs/develtools/packages/); or by
>>         logging
>>         them to the LogObject in OTRS.
>>
>>         Hope this helps.
>>
>>         --
>>         Mike
>>
>>         On Mon, Sep 10, 2012 at 11:12 AM, Bogdan Iosif
>>         <[email protected] <mailto:[email protected]>> wrote:
>>         > Hi,
>>         >
>>         > I'm trying to setup a dev env for OTRS on Windows and I'm
>>         new to Perl. After
>>         > some poking around for a few days trying to understand Perl
>>         distributions
>>         > and development, I'm still pretty much where I started.
>>         >
>>         > If a guide for setting up a specific dev env is available,
>>         can someone
>>         > please provide me with its URL?
>>         >
>>         > If such a guide is not available, please help with the
>>         following direct
>>         > questions:
>>         >
>>         > Is OTRS dev normally done via an IDE, and if so what is the
>>         preferred one? I
>>         > tried to find an ide-project like grouping in the OTRS
>>         sources and couldn't
>>         > spot one.
>>         > Is it possible to load all the source files in an editor
>>         capable of finding
>>         > method / object definitions? (I don't mean full text search
>>         but something
>>         > like Intellisense)
>>         > Is interactive debugging possible for OTRS? By this I mean
>>         setting
>>         > breakpoints and exploring values for variables when a
>>         breakpoint is hit.
>>         > Is there such a thing as syntax check, source compilation
>>         or unit testing so
>>         > that I can be as sure as possible that changes I've made do
>>         not immediately
>>         > crash when they are executed?
>>         >
>>         > I'm familiar with the dev workflow from Visual Studio (C#)
>>         and Eclipse
>>         > (Java) and hoping to achieve something similar with OTRS,
>>         if possible. If
>>         > someone can answer and is also familiar with those IDEs,
>>         please use them for
>>         > comparison.
>>         >
>>         > Thanks,
>>         > Bogdan
>>         >
>>         > What I've already done:
>>         >
>>         > - Got the sources from a zip package
>>         > (http://ftp.otrs.org/pub/otrs/otrs-3.1.9.zip) because a
>>         direct CVS link
>>         > doesn't work from my organization (port 2401 is blocked).
>>         >
>>         > - Looked over the dev manual
>>         >
>>         (http://ftp.otrs.org/pub/otrs/doc/doc-admin/3.1/en/pdf/otrs_admin_book.pdf)
>>         > and Searched the mailing lists
>>         (http://lists.otrs.org/pipermail/dev/) with
>>         > Google. Couldn't find any references to an IDE.
>>         >
>>         > - Found info about debugging a running OTRS env by enabling
>>         a debug mode
>>         > where I would get a lot of info logged to files.
>>         >
>>         > _______________________________________________
>>         > OTRS mailing list: dev - Webpage: http://otrs.org/
>>         > Archive: http://lists.otrs.org/pipermail/dev
>>         > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
>>         _______________________________________________
>>         OTRS mailing list: dev - Webpage: http://otrs.org/
>>         Archive: http://lists.otrs.org/pipermail/dev
>>         To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
>>
>>
>>
>>
>>     _______________________________________________
>>     OTRS mailing list: dev - Webpage:http://otrs.org/
>>     Archive:http://lists.otrs.org/pipermail/dev
>>     To unsubscribe:http://lists.otrs.org/cgi-bin/listinfo/dev
>
>     -- 
>     Rocco Tocci
>     Application Architect
>     Strada Prov. 1 BariModugno n. 4
>     70123 Bari  Italy
>     Tel.+39 0803855483  <tel:%2B39%200803855483>
>
>     TBS IT -- Telematic & Biomedical Services Srl a socio unico
>     Sede Legale : Via Giacinto Gallina, 4 -- 34122 Trieste
>     Tel. 040 - 92291
>     Sede Operativa : Via Francesco Bettini, 13 -- 06034 Foligno
>     Tel. 0742- 32661
>     C.F., P.IVA e Registro Imprese (TS) : 01165260322
>     Cap.Soc. EUR 8.000.000,00 i.v.
>     una società di TBS Group SpA
>       
>     Ai sensi del D.Lgs. 196/2003 e della normativa internazionale, vi informiamo che questo messaggio è riservato esclusivamente al destinatario. Se esso vi fosse pervenuto per errore, vi invitiamo a eliminarlo immediatamente e a darcene comunicazione. Grazie.
>     According to the Italian and international laws in force, we inform you that this message is reserved only for the addressee. If you are not the addressee, please delete it immediately and notify us. Thank you.
>       P Per favore, pensa all'ambiente prima di stampare questo messaggio. Please, consider the environment before printing this e-mail.
>
>
>
>
>     _______________________________________________
>     OTRS mailing list: dev - Webpage: http://otrs.org/
>     Archive: http://lists.otrs.org/pipermail/dev
>     To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
>
>
>
>
> _______________________________________________
> OTRS mailing list: dev - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/dev
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

-- 
Rocco Tocci
Application Architect
Strada Prov. 1 BariModugno n. 4
70123 Bari  Italy
Tel. +39 0803855483

TBS IT -- Telematic & Biomedical Services Srl a socio unico
Sede Legale : Via Giacinto Gallina, 4 -- 34122 Trieste
Tel. 040 - 92291
Sede Operativa : Via Francesco Bettini, 13 -- 06034 Foligno
Tel. 0742- 32661
C.F., P.IVA e Registro Imprese (TS) : 01165260322
Cap.Soc. EUR 8.000.000,00 i.v.
una società di TBS Group SpA
  
Ai sensi del D.Lgs. 196/2003 e della normativa internazionale, vi informiamo che questo messaggio è riservato esclusivamente al destinatario. Se esso vi fosse pervenuto per errore, vi invitiamo a eliminarlo immediatamente e a darcene comunicazione. Grazie.
According to the Italian and international laws in force, we inform you that this message is reserved only for the addressee. If you are not the addressee, please delete it immediately and notify us. Thank you.
  P Per favore, pensa all'ambiente prima di stampare questo messaggio. Please, consider the environment before printing this e-mail.

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev