[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-18422 at 9/24/14 9:35 AM:
--------------------------------------------------------------
Test results using locally built JBT from [~dgolovin]:
Installed plugins:
- org.eclipse.angularjs.* version 0.6.0.201409231617
- org.jboss.tools.jst.angularjs version 3.6.0.CR2-v20140923-2244
- tern.* version 0.6.0.201409231610
- org.jboss.tools.jst.jsdt version 3.6.0.CR2-v20140923-2244
Test scenario:
1. Import jboss-kitchensink-angularjs project from JBoss Central
- project has jsNature no need/posibility to convert it to JavaScript project
2. Open Angular Explorer
3. Open home.html page in VPE
- application appears in Angular explorer with all modules displayed
- Angular code highlight works
- ng-* code assist works
- code assist for ng-app="| works
- open on for ng-app="kitchensink" on kitchensink opens app.js
4. Open home.html in VPE
5. Select webapp > modules > membersService > MembersCtrl and click on Link to controller context menu
6. Add {{}} to home.html and invoke code assist for {{ | }}
- there is no orderBy property in code assist. orderBy property is defined in controllers.js MembersCtrl.
7. Add <h1>{{ orderBy }}</h1> to home.html page anr run application on server.
- value of orderBy property is correctly displayed in web browser
8. Select webapp > modules > membersService and click on Link to controller context menu
9. Add {{}} to home.html and invoke code assist for {{ | }}
ERROR:
{noformat}
!ENTRY org.eclipse.angularjs.ui 4 0 2014-09-24 10:23:27.513
!MESSAGE Error while tern completion.
!STACK 0
tern.TernException: TypeError: Cannot call method 'indexOf' of null
at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:87)
at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:170)
at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:232)
at tern.eclipse.ide.internal.core.IDETernProject.request(IDETernProject.java:532)
at tern.eclipse.ide.internal.core.IDETernProject.request(IDETernProject.java:502)
at org.eclipse.angularjs.ui.contentassist.HTMLAngularTagsCompletionProposalComputer.populateAngularProposals(HTMLAngularTagsCompletionProposalComputer.java:347)
at org.eclipse.angularjs.ui.contentassist.HTMLAngularTagsCompletionProposalComputer.computeCompletionProposals(HTMLAngularTagsCompletionProposalComputer.java:442)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:169)
at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284)
at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290)
at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484)
at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255)
at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127)
at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1861)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.handleRepeatedInvocation(CompletionProposalPopup.java:558)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:523)
at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1687)
at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:488)
at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$JSPStructuredTextViewer.doOperation(JSPTextEditor.java:663)
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:519)
at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1574)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1387)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269)
at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
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:9074)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
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:2473)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{noformat}
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3101) Differences in 3rd party time stamps between builds
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3101?page=com.atlassian.jira.plugin.... ]
Martin Malina resolved JBDS-3101.
---------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.CR2)
Resolution: Out of Date
This disappeared in CR1, so resolving. Reopen if it reappears.
> Differences in 3rd party time stamps between builds
> ---------------------------------------------------
>
> Key: JBDS-3101
> URL: https://issues.jboss.org/browse/JBDS-3101
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: build
> Affects Versions: 8.0.0.Beta3
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 8.0.0.CR1
>
> Attachments: dist-diff-grepped.log, dist-diff.log
>
>
> Hi Nick, perhaps you can clear this up.
> Sometimes I run the dist-diff tool between builds of JBDS to see what changed.
> You can see the latest report between JBDS 8.0.0.Beta3b B193 and Beta3c B194 here:
> http://machydra.brq.redhat.com/dist-diff/8.0.0.Beta3b-Beta3c/
> What is certainly expected are the changes in Forge2 and Webservices - those had fixes in them.
> But then you can see many differences like these:
> {code}
> [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/MANIFEST.MF
> [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.SF
> [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!META-INF/ECLIPSE_.RSA
> [dist-diff] org.eclipse.datatools.sqltools.parsers.sql_1.0.2.v201107221520.jar!about.mappings
> {code}
> What triggers these is usually a change in the about.mappings file:
> {code}
> nattura:dist-diff rasp$ diff 1/about.mappings 2/about.mappings
> 6c6
> < 0=1.7.2.v20140606-1324
> \ No newline at end of file
> ---
> > 0=1.7.2.v20140307-0500
> \ No newline at end of file
> {code}
> See the different time stamp. In case you wondered, that 0 property is used in the about.properties for build id:
> {code}
> blurb=Eclipse Data Tools Platform Model Base\n\
> \n\
> Version: {featureVersion}\n\
> Build id: {0}\n\
> \n\
> (c) Copyright Eclipse contributors and others 2005, 2007. All rights reserved.\n\
> Visit http://www.eclipse.org/datatools
> {code}
> Do you know why this is happening? Does every build take the dependencies from upstream again and potentially from a different mirror? Is this ok?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17940) JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17940?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-17940:
-----------------------------------
So AFAICS you need to click in the Java editor at least once before they show up in the details view.
> JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17940
> URL: https://issues.jboss.org/browse/JBIDE-17940
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3, GNU/Linux 64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> JPA Details view is not working for entities in autodiscovery mode. It only works when entities are added into Managed Classes entities list. It's expected when JPA project is configured with "Discover annotated classes automatically" it should without manual listing entities in persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18394) Luna SR1 target-platform
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18394?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18394:
----------------------------------------
What you say is contradicatory, either it looks ok, or it's missing something. I don't think it can be both at the same time ;)
I don't see where sapphire still uses the old Luna RC4 site. Can you give a link?
Or maybe you're speaking about discovery target files? A PR should come after we agreed on this one.
> Luna SR1 target-platform
> ------------------------
>
> Key: JBIDE-18394
> URL: https://issues.jboss.org/browse/JBIDE-18394
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
>
> Consume Luna SR1 in JBT 4.2.0/JBDS 8.0.0
> p2diff:
> {code}
> mistria@mistria--rh:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff -mode=ignoreVersions http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:/home/mistria/git/jboss
> tools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/
> < org.apache.httpcomponents.httpclient.source [4.2.6.v201311072007]
> < org.apache.commons.logging.source [1.1.1.v201101211721]
> < org.apache.commons.codec.source [1.6.0.v201305230611]
> < org.apache.httpcomponents.httpcore.source [4.2.5.v201311072007]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 4 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 0 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16071:
---------------------------------------------
anything moved here ? In any case - not important enough for blocking cr2 so moving off.
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16071:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months