[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Odp.: Build path/ Include path


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


Am 24.04.16 um 20:56 schrieb Michal Niewrzal:

My knowledge about include path management is very limited but +1 for every simplification around include path/build path &#X1f60a


*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

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