Re: Re: Re: extended Autocompletion in IvyDE ivy editor

[Eugene Sajine <eu...@gmail.com>]

Maarten,

Sorry for delay - i have submitted the JIRA issue IVYDE-243

Thanks,
Eugene

On Thu, Mar 18, 2010 at 4:19 PM, Maarten Coene <ma...@yahoo.com> wrote:
> Seems like a bug to me, could you create a JIRA issue?
> Or maybe you can try again with the upcoming IvyDE 2.1.0 release? An Eclipse update site containing the not-yet-approved plugin is here: http://people.apache.org/~jschneider/staging/updatesite/
>
> thanks,
> Maarten
>
>
>
> ----- Original Message ----
> From: "Euguess@gmail.com" <Eu...@gmail.com>
> To: Maarten Coene <ma...@yahoo.com>; Euguess@gmail.com; Eugene Sajine <eu...@gmail.com>
> Cc: ivy-user@ant.apache.org
> Sent: Tue, March 16, 2010 9:42:35 PM
> Subject: Re: Re: Re: extended Autocompletion in IvyDE ivy editor
>
> I see where you're going and I double checked what i see:
>
> Please note that in all described cases the ivyDE plugin and Ivy itself are parsing existing files ok and resolving dependencies correctly.
>
> 1. Configuration autocompletion.
> our configurations file which we include into the ivy.xml has configurations defined like that (example):
>
> <configurations confmappingoverride="true" defaultconfmapping="api->api(default);compile->api(default);runtime->runtime(default)">
>
> <conf name="api"/>
> <conf name="compile" extends="api"/>
> <conf name="runtime" extends="compile"/>
> </configurations>
>
> in ivy.xml we have it included
> <configurations>
> <include file=ivy.config.xml>
> </configurations>
>
> 2 problems here:
>
> The only way i can get IVyDE autocomplete to work with configurations is to specify them directly in the file. In addition to that the only acceptable format is *without* default mapping. The default mapping causes autocomplette to show only "*" and "default" as possible conf values, when i should see *, api, compile and runtime.
>
> Secondly, the include is not supported for editor even direct. When i'm using it autocomplete gives me only "*"
>
> 2. org and rev.
> With my current set up when I'm hitting CTRL+Space to get autocomplete for <org> or <rev> I'm getting a NullPointerException. Please, see the stack trace in the end of the mail.
>
>
> 3. When I'm hitting Ctrl+Space for <name> I'm actually getting a list of artifacts! and I believe i see artifacts from all of our repos...
>
> Hope that helps!
>
> Thanks,
> Eugene
>
> here is the exception for p.2
> java.lang.NullPointerException
> at
> org.apache.ivyde.common.model.IvyTag.getPossibleValuesForAttribute(IvyTag.java:163)
> at
> org.apache.ivyde.common.ivyfile.IvyModuleDescriptorModel$12.getPossibleValuesForAttribute(IvyModuleDescriptorModel.java:268)
> at
> org.apache.ivyde.common.completion.IvyCodeCompletionProcessor.computeValueProposals(IvyCodeCompletionProcessor.java:129)
> at
> org.apache.ivyde.common.completion.IvyCodeCompletionProcessor.computeCompletionProposals(IvyCodeCompletionProcessor.java:50)
> at
> org.apache.ivyde.eclipse.ui.editors.xml.IvyContentAssistProcessor.computeCompletionProposals(IvyContentAssistProcessor.java:70)
> at
> org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1832)
> at
> org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556)
> at
> org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553)
> at
> org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at
> org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482)
> at
> org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1660)
> at
> org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:835)
> at
> org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at
> org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185)
> at
> org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> at
> org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at
> org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510)
> at
> org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1175)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1212)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:706)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2837)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:703)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1570)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4587)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4191)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:7588)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1185)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1860)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3110)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
> 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:368)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:592)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>
>
>
>
>
>
> On Mar 16, 2010 3:44pm, Maarten Coene <ma...@yahoo.com> wrote:
>> How do you define those $properties? Do you define them in your ivysettings.xml file?
>
>> And is IvyDE able to resolve your dependencies correctly, or doesn't
>
>> that work neither?
>
>
>
>> Maarten
>
>
>
>
>
>> ________________________________
>
>> From: "Euguess@gmail.com" Euguess@gmail.com>
>
>> To: Eugene Sajine euguess@gmail.com>; Euguess@gmail.com
>
>> Cc: Maarten Coene maarten_coene@yahoo.com>; ivy-user@ant.apache.org
>
>> Sent: Tue, March 16, 2010 7:54:24 PM
>
>> Subject: Re: Re: extended Autocompletion in IvyDE ivy editor
>
>
>
>> Maarten,
>
>
>
>
>
>> I'm 99% sure i know what the problem is.
>
>
>
>> IvyDE editor doesn't know how to parse XML includes and $properties while ivy itself does that with no problem.
>
>
>
>> I mean that we have ivy.settings which doesn't have repositories listed in chain resolver directly in the file, but includes the file with this information:
>
>
>
>
>
>
>
>> or even something like this:
>
>
>
>
>
>
>
>
>
>> We also *don't* use direct addresses in patterns like:
>
>
>
>
>
>
>
>
>
>
>
>
>
>> but we use
>
>
>
>
>
>
>
>
>
>
>
>
>
>> As i said - Ivy works with this fine, but IVYDE Editor doesn't.
>
>
>
>> Thanks,
>
>> Eugene
>
>
>
>> On Mar 15, 2010 7:16pm, Eugene Sajine euguess@gmail.com> wrote:
>
>> >
>
>> > No,no I'm using the ivy editor as it even changes the color schema of the code coloring... so that's not it
>
>> >
>
>> > On Mar 15, 2010 4:24 PM, "Maarten Coene" maarten_coene@yahoo.com> wrote:
>
>> >
>
>> > Maybe you did open the ivy.xml with the standard Eclipse "XML Editor"?
>
>> >
>
>> >
>
>> > Did you try to open the ivy.xml file with the special "Ivy Editor"?
>
>> >
>
>> >
>
>> >
>
>> > Maarten
>
>> >
>
>> >
>
>> >
>
>> >
>
>> >
>
>> >
>
>> >
>
>> >
>
>> >
>
>> > ________________________________
>
>> >
>
>> > From: Eugene Sajine euguess@gmail.com>
>
>> >
>
>> > To: Maarten Coene maarten_coene@yahoo.com>
>
>> >
>
>> > Cc: Euguess@gmail.com; ivy-user@ant.apache.org
>
>> >
>
>> > Sent: Mon, March 15, 2010 5:55:11 PM
>
>> >
>
>> > Subject: Re: extended Autocompletion in IvyDE ivy editor
>
>> >
>
>> >
>
>> >
>
>> >
>
>> > Maarten,
>
>> > Unfortunately, it doesn't work as it should so far. We have no maven compatibility flags ...
>
>
>
>