[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Separate builds for Kepler and Juno

I just tried DLTK 5 and PDT 3.2 nightly on Eclipse 3.8.1 and they worked fine: no dependency errors, no runtime errors when creating PHP project, opening PHP file, using content-assist.

When running PDT 3.2 nightly with DLTK 4, content-assist was not fully working.

Jacek



On Fri, Jan 18, 2013 at 6:56 PM, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:

Whowâ that sounds interesting indeed !

Â

Does anybody know whether the nightly DLKT + PDT builds do actually have a dependency against 4.3 Platform,

Or is there a chance getting these to work on 3.8.2 ?

Â

Thanks,

Martin

--

MartinÂOberhuber, SMTS / Product Architect â Development Tools, Wind River

direct +43.662.457915.85ÂÂfax +43.662.457915.6

Â

From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Tomasz Rakowski
Sent: Monday, January 07, 2013 3:33 AM
To: PDT Developers
Subject: Re: [pdt-dev] Separate builds for Kepler and Juno

Â

Hi all,Â

Â

I've installed Kepler, with nightlyÂDLTK and PDT builds, and I've noticed a majorÂimprovementÂin both speed ( as Robert reported) and ... stability. I worked all day on some pretty heavy and nasty projects, and I did not have a single crash, and things generally worked much faster than with previous (4.2 + stable) stack. I'm on Linux 64bit...

Â

So, just wanted to throw in a big thank you... can't wait for the next release !

Â

Thanks,Â

Â

Tomasz

Â

Â

On Fri, Jan 4, 2013 at 4:20 AM, Jacek PospychaÅa <jacek.p@xxxxxxxx> wrote:

that's great to hear!


On Fri, Jan 4, 2013 at 10:14 AM, Robert GrÃndler <r.gruendler@xxxxxxxxx> wrote:
> I've been comparing it to 4.2, with a fairly large project i'm working on at
> the moment. It seems i'm seeing the
> latest performance improvements implemented in the 4.3 dev builds.
>
> It's hard to say and very subjective, but it feels like the UI is responding
> a lot faster, for example:
>
> - Selecting the project in the explorer and holding the down arrow: this has
> been quite slow in 4.2. Now it's a lot faster
> - Opening large files has been sluggish in 4.2 sometimes, i didn't see this
> in 4.3. Files open instantly, also with a lot of open tabs.
> - Typing in general does not show any lags so far which i encountered in
> 4.2.
>
>
> -robert
>
>
>
>
> On Fri, Jan 4, 2013 at 9:55 AM, Jacek PospychaÅa <jacek.p@xxxxxxxx> wrote:
>>
>> Interesting!
>> Do you have any examples what feels faster? (and you compared to 3.8 or
>> 4.2?)
>> It seems that Eclipse platform 4.3 (Kepler) dev builds were improved a
>> lot in terms of GUI performance. On PDT side we didn't touch lately
>> anything performance-related.
>>
>> Jacek
>>
>>
>> On Fri, Jan 4, 2013 at 9:50 AM, Robert GrÃndler <r.gruendler@xxxxxxxxx>
>> wrote:
>> > thanks Alexey, i got it working now.
>> >
>> > fyi: I don't know if it's the changes in Kepler / DLTK or PDT itself,
>> > but
>> > PDT seems a lot faster running the latest versions under kepler. Great
>> > job!
>> >
>> >
>> > regards
>> >
>> > -robert
>> >
>> >
>> >
>> >
>> > On Thu, Jan 3, 2013 at 11:34 AM, Alexey Panchenko
>> > <alex.panchenko@xxxxxxxxx>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> You need nightly build of DLTK, at the moment available only from
>> >> https://hudson.eclipse.org/hudson/job/dltk-nightly/
>> >>
>> >> Regards,
>> >> Alex
>> >>
>> >>
>> >> On Thu, Jan 3, 2013 at 5:31 PM, Robert GrÃndler <r.gruendler@xxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> Alright thanks.
>> >>>
>> >>> I've tried the Kepler build now, and it seems contentassist is broken
>> >>> (stack trace at the end of the mail).
>> >>>
>> >>> Do i need to upgrade to a specific DLTK version too? Right now the
>> >>> following has been installed during dependency resolution:
>> >>>
>> >>> Â Â Â Dynamic Languages Toolkit - Core Frameworks
>> >>> 4.0.0.201206120848
>> >>> org.eclipse.dltk.core.feature.group  ÂEclipse.org
>> >>>
>> >>>
>> >>> If you think it's a regression, i can file a bug in bugzilla.
>> >>>
>> >>>
>> >>> regards
>> >>>
>> >>> -robert
>> >>>
>> >>>
>> >>>
>> >>> Here's the trace:
>> >>>
>> >>> Caused by: java.lang.NoSuchMethodError:
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposal.setProposalInfo(Lorg/eclipse/dltk/ui/text/completion/ICompletionProposalInfo;)V
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createTypeProposal(PHPCompletionProposalCollector.java:291)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.php.internal.ui.editor.contentassist.PHPCompletionProposalCollector.createScriptCompletionProposal(PHPCompletionProposalCollector.java:119)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposal(ScriptCompletionProposalCollector.java:315)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.processUnprocessedProposals(ScriptCompletionProposalCollector.java:291)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalCollector.getScriptCompletionProposals(ScriptCompletionProposalCollector.java:273)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeScriptCompletionProposals(ScriptCompletionProposalComputer.java:219)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ScriptCompletionProposalComputer.computeCompletionProposals(ScriptCompletionProposalComputer.java:266)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:346)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:276)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:291)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.dltk.ui.text.completion.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:247)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1839)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:566)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:563)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:498)
>> >>> Â Â at
>> >>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:492)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:378)
>> >>> Â Â at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
>> >>> Â Â at
>> >>> org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3965)
>> >>> Â Â at
>> >>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1049)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:939)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
>> >>> Â Â at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:587)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:542)
>> >>> Â Â at
>> >>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
>> >>> Â Â at
>> >>>
>> >>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
>> >>> Â Â at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >>> Â Â at
>> >>>
>> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >>> Â Â at
>> >>>
>> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >>> Â Â at java.lang.reflect.Method.invoke(Method.java:597)
>> >>> Â Â at
>> >>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
>> >>> Â Â at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
>> >>> Â Â at org.eclipse.equinox.launcher.Main.run(Main.java:1443)
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Thu, Jan 3, 2013 at 10:44 AM, Jacek PospychaÅa <jacek.p@xxxxxxxx>
>> >>> wrote:
>> >>>>
>> >>>> It's correct one. Version numbers haven't been updated yet. They
>> >>>> should be shortly...
>> >>>>
>> >>>> On Thu, Jan 3, 2013 at 10:40 AM, Robert GrÃndler
>> >>>> <r.gruendler@xxxxxxxxx>
>> >>>> wrote:
>> >>>> > Using http://download.eclipse.org/tools/pdt/updates/3.2-nightly/
>> >>>> > gives
>> >>>> > me
>> >>>> > the following pdt version
>> >>>> >
>> >>>> > Â Â PHP Development Tools (PDT) Â Â3.1.2.201212311412
>> >>>> >
>> >>>> >
>> >>>> > Is this the correct one? I would have thought it should be 3.2.xxx
>> >>>> >
>> >>>> >
>> >>>> > regards
>> >>>> >
>> >>>> >
>> >>>> > -robert
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > On Thu, Jan 3, 2013 at 9:59 AM, Robert GrÃndler
>> >>>> > <r.gruendler@xxxxxxxxx>
>> >>>> > wrote:
>> >>>> >>
>> >>>> >> thanks for the info Jacek and happy new year ;)
>> >>>> >>
>> >>>> >>
>> >>>> >> -robert
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >> On Fri, Dec 21, 2012 at 2:10 PM, Jacek PospychaÅa
>> >>>> >> <jacek.p@xxxxxxxx>
>> >>>> >> wrote:
>> >>>> >>>
>> >>>> >>> hi,
>> >>>> >>> I just created branch for PDT maintenance builds for Juno SR2
>> >>>> >>> release.
>> >>>> >>>
>> >>>> >>> So if you're using Juno, please use p2 repository:
>> >>>> >>> Âhttp://download.eclipse.org/tools/pdt/updates/3.1-nightly/
>> >>>> >>>
>> >>>> >>> If you're using Kepler developer builds, please use p2
>> >>>> >>> repository:
>> >>>> >>> Âhttp://download.eclipse.org/tools/pdt/updates/3.2-nightly/
>> >>>> >>>
>> >>>> >>> Previously I was hoping that it'd be possible to have just a
>> >>>> >>> single
>> >>>> >>> repository that works for everyone. Unfortunately it doesn't
>> >>>> >>> work,
>> >>>> >>> because other projects that we depend on grow quickly and become
>> >>>> >>> backward incompatible.
>> >>>> >>> The repository url that we used until now
>> >>>> >>> (http://download.eclipse.org/tools/pdt/updates/nightly/) will
>> >>>> >>> point
>> >>>> >>> to
>> >>>> >>> the Juno builds.
>> >>>> >>>
>> >>>> >>> so please update your urls!
>> >>>> >>>
>> >>>> >>> thanks!
>> >>>> >>>
>> >>>> >>> Jacek
>> >>>> >>> _______________________________________________
>> >>>> >>> pdt-dev mailing list
>> >>>> >>> pdt-dev@xxxxxxxxxxx
>> >>>> >>> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >>>> >>
>> >>>> >>
>> >>>> >
>> >>>> >
>> >>>> > _______________________________________________
>> >>>> > pdt-dev mailing list
>> >>>> > pdt-dev@xxxxxxxxxxx
>> >>>> > https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >>>> >
>> >>>> _______________________________________________
>> >>>> pdt-dev mailing list
>> >>>> pdt-dev@xxxxxxxxxxx
>> >>>> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> pdt-dev mailing list
>> >>> pdt-dev@xxxxxxxxxxx
>> >>> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >>>
>> >>
>> >>
>> >> _______________________________________________
>> >> pdt-dev mailing list
>> >> pdt-dev@xxxxxxxxxxx
>> >> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >>
>> >
>> >
>> > _______________________________________________
>> > pdt-dev mailing list
>> > pdt-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/pdt-dev
>> >
>> _______________________________________________
>> pdt-dev mailing list
>> pdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
>
>
> _______________________________________________
> pdt-dev mailing list
> pdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pdt-dev
>
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev

Â


_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev