[pdt-dev] Build path/ Include path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[pdt-dev] Build path/ Include path

From: Dawid Pakuła <zulus@xxxxxxxxx>
Date: Sun, 24 Apr 2016 18:31:31 +0200
Delivered-to: pdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/pdt-dev>
List-help: <mailto:pdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/pdt-dev>, <mailto:pdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/pdt-dev>, <mailto:pdt-dev-request@eclipse.org?subject=unsubscribe>

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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Follow-Ups:
- [pdt-dev] Odp.: Build path/ Include path
  - From: Michal Niewrzal

Prev by Date: Re: [pdt-dev] Smart Import
Next by Date: [pdt-dev] Odp.: Smart Import
Previous by thread: [pdt-dev] Smart Import
Next by thread: [pdt-dev] Odp.: Build path/ Include path
Index(es):
- Date
- Thread

Breadcrumbs