Hi, here are working procedures [1][2].
Should be possible to improve maven pom.xml, and compile importer only with eclipse-next. Later insted of pdt-master and eclipse-next, we could change our jobs to pdt-master and eclipse-prev. ;) [1] - https://wiki.eclipse.org/PDT/Developers_Working_Procedures [2] - https://wiki.eclipse.org/PDT/Target_Environment -- Dawid Pakuła From: Michal Niewrzal <micha...@zend.com> Reply: PDT Developers <pdt-dev@eclipse.org> Date: 25 April 2016 at 11:43:37 To: PDT Developers <pdt-dev@eclipse.org> Subject: [pdt-dev] Odp.: Odp.: Smart Import Hi, I created patch for smart import[1]. Now I'm thinking how infrastructure should be configured because for now patch cannot be merged, it's using Neon API. I don't remember, when we can switch builds to Neon as an main repository? [1] https://git.eclipse.org/r/#/c/71304/ Michal Od: pdt-dev-boun...@eclipse.org <pdt-dev-boun...@eclipse.org> w imieniu użytkownika Michal Niewrzal <micha...@zend.com> Wysłane: 24 kwietnia 2016 20:26 Do: PDT Developers Temat: [pdt-dev] Odp.: Smart Import Ok, I think "**/index.php" + "**/composer.json" will be enough for initial implementation. Other cases like Symfony projects we can add later. Because smart project import is part of new Neon API this feature should be separate bundle and separate entry in update site. Of course we can add it to EPP package also I will update bug report and prepare implementation. Michal Od: pdt-dev-boun...@eclipse.org <pdt-dev-boun...@eclipse.org> w imieniu użytkownika Dawid Pakuła <zu...@w3des.net> Wysłane: 22 kwietnia 2016 18:03 Do: PDT Developers Temat: Re: [pdt-dev] Smart Import Hi, how about **/index.php? , will be much faster than *.php and probably will find correct project. But for example symfony projects haven’t index.php (even in vendor). They use web/app.php file. -- Dawid Pakuła From: Kaloyan Raev <kaloya...@zend.com> Reply: PDT Developers <pdt-dev@eclipse.org> Date: 22 April 2016 at 17:37:07 To: PDT Developers <pdt-dev@eclipse.org> Subject: Re: [pdt-dev] Smart Import Hi, Great! This was in my TODO list for research, but I've never found the time I think having 'public/index.php' is also quite popular for PHP projects. 'index.php' in the project root might be also a good criterion. Kaloyan From: pdt-dev-boun...@eclipse.org <pdt-dev-boun...@eclipse.org> on behalf of Michal Niewrzal <micha...@zend.com> Sent: Friday, April 22, 2016 6:29 PM To: PDT Developers Subject: [pdt-dev] Smart Import Hi All, I'm thinking about implementing smart import support[1] for PHP projects. The main challenge is to define best strategy for project detection. First and easiest to detect is 'composer.json'. Framework gives option to scan whole project but I wonder if just searching for *.php files will not be to general. Let me know what do you think about it Thanks, Michal [1] https://wiki.eclipse.org/E4/UI/Smart_Import E4/UI/Smart Import - Eclipsepedia wiki.eclipse.org Smarter import framework Purpose. Currently, when importing a project, users are facing the difficult choices of What project they're importing and How to import it. _______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org 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@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/pdt-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/pdt-dev
