Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Composer and Build Paths

Hi Kaloyan,

it could be a bug, maybe it's worth to open a bug report with your faulty workspace as demo ;)


De : pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> de la part de Kaloyan Raev <kaloyan.r@xxxxxxxx>
Envoyé : mercredi 31 mai 2017 12:59
À : pdt-dev@xxxxxxxxxxx
Objet : Re: [pdt-dev] Composer and Build Paths
 
Hi again,

It is strange, but when a switched to a fresh new workspaces, all the build paths are created as expected. I am still not sure what's the issue with the other workspace.
--
Kaloyan Raev | Zend Studio Team Lead
Rogue Wave Software, Inc.
Innovate with Confidence
M +359 887 648 663
www.roguewave.com / kaloyan.raev@xxxxxxxxxxxxx


On 05/31/2017 10:21 AM, Kaloyan Raev wrote:
Hi,

I am on Oxygen RC1 now and I noticed something strange when creating a new project with the PHP Project from Composer Package wizard.

After the project (e.g. laravel) is created I get just a few build paths: /src and /vendor/composer. I need to explicitly call Composer > Update Build Path to have the "autoload" section of dependencies scanned and added to the build path. In PDT 4.3 this was done automatically as part of the project creation.

Is this change intentional?
--
Kaloyan Raev | Zend Studio Team Lead
Rogue Wave Software, Inc.
Innovate with Confidence
M +359 887 648 663
www.roguewave.com / kaloyan.raev@xxxxxxxxxxxxx 



_______________________________________________
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

Back to the top