Re: [pdt-dev] Odp.: Build path/ Include path

[Gadi Goldbarg <gadi@xxxxxxxx>]

Hi,
I have to say that it is very confusing to use Java names as in PHP there is no such thing as build path.
A PHP developer just needs to be able to specify which are his files for Include path ( e.g. his used code ). He doesn't really know what build path is !
( Build path is kind of internal for the IDE )
- Although Composer takes care of you most of the time not everyone is using it so we probably still need this way.

My 2 cents , so if you guys want to simplify just leave include path :)

Gadi

-----Original Message-----
From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Gossmann
Sent: Monday, April 25, 2016 11:27 AM
To: PDT Developers <pdt-dev@xxxxxxxxxxx>
Subject: Re: [pdt-dev] Odp.: Build path/ Include path

Hi,

my knowledge on include path (and also libraries) is very limited, I think it just got copied in, when DLTK provided such functionality.
Reducing it to just build path is what would help PDT a lot. Then build path would take 3 different types of entries:

- folder
- library folder
- project (see also [1])

[1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=492187

gossi

Am 24.04.16 um 20:56 schrieb Michal Niewrzal:
> Hi,
>
>
> My knowledge about include path management is very limited but +1 for 
> every simplification around include path/build path &#X1f60a
>
>
> Michal
>
> ----------------------------------------------------------------------
> --
> *Od:* pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> w 
> imieniu użytkownika Dawid Pakuła <zulus@xxxxxxxxx>
> *Wysłane:* 24 kwietnia 2016 18:31
> *Do:* PDT Developers
> *Temat:* [pdt-dev] Build path/ Include path Hi,
>
> I’m playing with bug 444226 [1] and have two concerns.
>
> 1. Do we really need include path management in composer age, when 
> PEAR is mostly dead? If yes can we just throw it away project 
> provisional (see point 2) and keep it simple with “sync with build path” button/switch?
> 2. Rather than creating completly new widget (with ton of code to 
> maintenance), maybe we could “just” migrate to standard DLTK 
> BuildPathPropertyPage? + rename it to validation/index path. After 
> that bug 472758[2] will be much simpler to resolve.
>
> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444226
> [2] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=472758
> --
> Dawid Pakuła
>
>
> _______________________________________________
> pdt-dev mailing list
> pdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/pdt-dev