Initially I planned to implement the PDT Extension Discovery wizard for Luna, but then my schedule became pretty tight. Most probably I will be able to work on this for SR1.
The MPC public API is indeed a helpful improvement. On Mon, Apr 28, 2014 at 1:30 PM, Jacek Pospychała < jacek.pospych...@gmail.com> wrote: > In the past we did code freeze and then rebuild per-request only. > That is we would add a new p2 repository for 3.3 > (.../updates/3.3-release), put there latest nightly build (from May > 9th) and also update simrel repository with release repository url. > Then we'd keep running nightly builds and copy nightly to release when > requested. > Finally we'd end up with one of nighly builds becoming a 3.3 release. > Makes sense? > > On Mon, Apr 28, 2014 at 10:41 AM, Dawid Pakuła <zu...@w3des.net> wrote: > > Hi, > > > > I want refresh this thread, because latest luna milestone will be at 9 > may. > > Next builds in theory should be RC. > > Any plan for this? > > > > Besides MPC have now public api [1] > > > > [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803 > > > > -- > > Dawid Pakuła > > +48 795 996 064 > > > > > > From: Kaloyan Raev kaloya...@zend.com > > Reply: PDT Developers pdt-dev@eclipse.org > > Date: 18 grudnia 2013 at 22:30:32 > > > > To: PDT Developers pdt-dev@eclipse.org > > Subject: Re: [pdt-dev] preliminary Eclipse PHP package > > > > Hi Dawid, > > > >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin > >> list (only some plugins from pdt-extensions.org). > >> Any suggestions? > >> Is the chosen document format ok? > > > > Thanks for starting this wiki. The format is good for start, we can > adjust > > it later as needed. > > > > I added just a few of the features of Zend Studio that can be listed. > > > > So far, I can see that we will have around 10 categories with a number of > > features (between 1 and 20) in each of them. There will be both open > source > > and commercial features, and even some features (e.g. PHPUnit) will have > an > > open source and commercial alternatives. > > > > This looks pretty similar to the Mylyn case. Please, have a look at the > > Mylyn Connector Discovery. It seems to me like a good fit for our case > too. > > We can use the same technology for "PDT Extension Discovery". > > > > Greetings, > > Kaloyan > > > > > > On Wed, Dec 18, 2013 at 7:56 PM, Dawid Pakuła <zu...@w3des.net> wrote: > >> > >> Hi > >> > >> Here https://wiki.eclipse.org/PDT/Extensions is draft version of plugin > >> list (only some plugins from pdt-extensions.org). > >> Any suggestions? > >> Is the chosen document format ok? > >> -- > >> Dawid Pakuła > >> +48 795 996 064 > >> ________________________________ > >> From: Dawid Pakuła Dawid Pakuła > >> Reply: Dawid Pakuła zu...@w3des.net > >> Date: 18 grudnia 2013 at 14:09:43 > >> > >> To: PDT Developers pdt-dev@eclipse.org > >> Subject: Re: [pdt-dev] preliminary Eclipse PHP package > >> > >> Hi, > >> > >> I think we can copy-paste plugins from PDT Extension Group [1] if they > are > >> available on Eclipse Marketplace. > >> > >> @Kaloyan I will try tonight > >> > >> [1] http://p2-dev.pdt-extensions.org/ > >> -- > >> Dawid Pakuła > >> +48 795 996 064 > >> ________________________________ > >> From: Kaloyan Raev Kaloyan Raev > >> Reply: PDT Developers pdt-dev@eclipse.org > >> Date: 18 grudnia 2013 at 13:50:41 > >> To: PDT Developers pdt-dev@eclipse.org > >> Subject: Re: [pdt-dev] preliminary Eclipse PHP package > >> > >> Adding an “Extend your PHP IDE” link on the Welcome screen that launches > >> an arbitrary UI is easy. > >> > >> I guess we now need to build the list of all potential plugins that > would > >> end in this plugin browser. Then we can start experimenting with the > browser > >> design so it fits to the complexity of the list we have. > >> > >> How about collecting all the plugins on a wiki page first, e.g. > >> http://wiki.eclipse.org/PDT/Extensions ? > >> Dawid, do you want to take the first round? > >> > >> Greetings, > >> Kaloyan > >> > >> > >> On Wed, Dec 18, 2013 at 12:57 PM, Dawid Pakuła <zu...@w3des.net> wrote: > >>> > >>> I think about this: > >>> > >>> On welcome screen special button with for ex text: “Extend your PHP > IDE” > >>> After click on it, widget/window will be opened with simple (but user > >>> friendly) plugin browser (categories, tags etc). > >>> On each plugin lead will be two buttons: Read more (open full market > >>> place info), Install (start install process) > >>> > >>> But how, where and by who data for this widget should be stored and > >>> collected I have no idea: > >>> > >>> Option 1: > >>> Probably as XML stored somewhere in eclipse infrastructure (in > >>> appropriate git repo?). > >>> Would be nice to read as many as we can information directly from > >>> marketplace (stars, description, comments > >>> > >>> Option 2: > >>> Use appropriate list of tags/categories/special markets and read all > >>> informations from marketplace (example tags: PHP, JavaScript, CSS, > HTML). > >>> But in this model, we will be without control on content. > >>> > >>> -- > >>> Dawid Pakuła > >>> +48 795 996 064 > >>> ________________________________ > >>> From: Kaloyan Raev Kaloyan Raev > >>> Reply: PDT Developers pdt-dev@eclipse.org > >>> Date: 18 grudnia 2013 at 10:10:56 > >>> To: PDT Developers pdt-dev@eclipse.org > >>> Subject: Re: [pdt-dev] preliminary Eclipse PHP package > >>> > >>> Yes, there is a number of plugins, which are not hosted at eclipse.org > >>> and hence not included in the EPP package that can really enhance the > >>> experience of PHP developers. > >>> > >>> It would be great if we can somehow promote them on the Welcome screen. > >>> If we have them all registered at the Eclipse Marketplace, perhaps it > will > >>> be possible to make them easily discovered from the PHP EPP package. > >>> > >>> Eclipse Foundation tdoes not prohibit (and even encourages) promoting > >>> Eclipse extensions (both open-source or proprietary) as long as all > parties > >>> are treated equally (a.k.a. vendor neutrality). > >>> > >>> Dawid, Jacek, do you have an opinion how such promotion can be designed > >>> in the EPP package? > >>> > >>> Greetings, > >>> Kaloyan > >>> > >>> > >>> On Tue, Dec 17, 2013 at 10:22 PM, Dawid Pakuła <zu...@w3des.net> > wrote: > >>>> > >>>> Hi > >>>> > >>>> interesting logo ;) > >>>> > >>>> Would be nice to add special welcome page with shortcuts to install > most > >>>> popular plugins like jQuery, EclipseColorThemes etc. > >>>> If this is possible, and allowed be the rules of the Eclipse > Foundation. > >>>> As I remember this was suggested by Kaloyan Raev on PDT Extensions > >>>> Platform discussion group. > >>>> > >>>> I think that also RSE (Remote System Explorer) should be bundled with > >>>> this package. > >>>> > >>>> -- > >>>> Dawid Pakuła > >>>> +48 795 996 064 > >>>> > >>>> ________________________________ > >>>> From: Jacek Pospychała Jacek Pospychała > >>>> Reply: PDT Developers pdt-dev@eclipse.org > >>>> Date: 17 grudnia 2013 at 20:27:04 > >>>> To: PDT Developers pdt-dev@eclipse.org > >>>> Subject: [pdt-dev] preliminary Eclipse PHP package > >>>> > >>>> hi, > >>>> we're looking at having a PHP package on www.eclipse.org/downloads > >>>> page for Luna release (June 2014): a downloadable and executable > >>>> Eclipse preconfigured exclusively for PHP devs. > >>>> > >>>> There's an initial package available for testing, so if there's > >>>> anybody willing to give it a try and share their feedback, please go > >>>> to > >>>> https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/ > >>>> > >>>> and look for Eclipse PHP product package, e.g. direct link to > >>>> currently latest build #30: > >>>> > >>>> > https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/30/artifact/org.eclipse.epp.packages/packages/org.eclipse.epp.package.php.product/target/products/ > >>>> > >>>> Jacek > >>>> _______________________________________________ > >>>> pdt-dev mailing list > >>>> pdt-dev@eclipse.org > >>>> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >>>> > >>>> > >>>> _______________________________________________ > >>>> pdt-dev mailing list > >>>> pdt-dev@eclipse.org > >>>> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >>>> > >>> > >>> _______________________________________________ > >>> pdt-dev mailing list > >>> pdt-dev@eclipse.org > >>> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >>> > >>> > >>> _______________________________________________ > >>> pdt-dev mailing list > >>> pdt-dev@eclipse.org > >>> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >>> > >> > >> _______________________________________________ > >> pdt-dev mailing list > >> pdt-dev@eclipse.org > >> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >> > >> > >> _______________________________________________ > >> pdt-dev mailing list > >> pdt-dev@eclipse.org > >> https://dev.eclipse.org/mailman/listinfo/pdt-dev > >> > > > > _______________________________________________ > > pdt-dev mailing list > > pdt-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > > > _______________________________________________ > > pdt-dev mailing list > > pdt-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > _______________________________________________ > pdt-dev mailing list > pdt-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/pdt-dev >
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/pdt-dev
