[JBoss JIRA] (JBIDE-22416) Plugins dependency conflict when importing JavaEE7 Sample
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22416?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22416:
-------------------------------
Fix Version/s: 4.5.0.AM1
> Plugins dependency conflict when importing JavaEE7 Sample
> ---------------------------------------------------------
>
> Key: JBIDE-22416
> URL: https://issues.jboss.org/browse/JBIDE-22416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160520-0424-B5396
> Build date: 20160520-0424
> Reporter: Josef Kopriva
> Assignee: Fred Bricon
> Fix For: 4.5.0.AM1
>
> Attachments: import_issue.png
>
>
> When I import JavaEE7 sample sample extra/spock-tests, I cannot install plugin due to plugin conflict issue.
> {code:java}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> Software currently installed: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> Software currently installed: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> Only one of the following can be installed at once:
> Java Development Tools Core 3.12.0.v20160426-1326 (org.eclipse.jdt.core 3.12.0.v20160426-1326)
> Java Development Tools Core 3.11.0.xx-201604081629-e45 (org.eclipse.jdt.core 3.11.0.xx-201604081629-e45)
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Core Features) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.feature.feature.group 10.0.0.Alpha1-v20160520-0424-B5396)
> To: org.eclipse.jdt.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> To: com.jboss.devstudio.core.feature.feature.group [10.0.0.Alpha1-v20160520-0424-B5396]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.compilerless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Headless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.headless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.jdt.patch.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Java Development Tools JUnit support 3.9.0.v20160421-1701 (org.eclipse.jdt.junit 3.9.0.v20160421-1701)
> To: bundle org.eclipse.jdt.core [3.12.0,4.0.0)
> Cannot satisfy dependency:
> From: TestNG Eclipse Support 6.9.11.201604020423 (org.testng.eclipse 6.9.11.201604020423)
> To: bundle org.eclipse.jdt.junit 0.0.0
> Cannot satisfy dependency:
> From: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> To: org.testng.eclipse [6.9.11.201604020423]
> Cannot satisfy dependency:
> From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.9.2.xx-201604081629-e45 Eclipse Java Development Tools 3.12.0.v20160428-0800 (org.eclipse.jdt.feature.group 3.12.0.v20160428-0800)
> To: org.eclipse.jdt.core [3.11.0.xx-201604081629-e45]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23705) no content assist in freemarker templates for interface-based beans
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23705?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23705:
-------------------------------
Fix Version/s: 4.5.0.AM1
> no content assist in freemarker templates for interface-based beans
> -------------------------------------------------------------------
>
> Key: JBIDE-23705
> URL: https://issues.jboss.org/browse/JBIDE-23705
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Ronald Müller
> Fix For: 4.5.0.AM1
>
>
> If your beans in freemarker templates are described by an interface, the code completion (content assist) will not work.
> There two mechanism implemented to provide content suggestion:
> # Bean-Introspection: this doesn't work for interfaces
> # Java Reflections: there are bugs which prevent any suggestions
> My suggestion: use only reflections - it will work for both and isn't that harder to implement.
> I'm working on a pull request for fixing this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23759) Avoid caught NPE in GettingStartedHtmlPage.getLoadProxyWizardsScript
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23759?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23759:
-------------------------------
Fix Version/s: 4.4.4.AM1
> Avoid caught NPE in GettingStartedHtmlPage.getLoadProxyWizardsScript
> --------------------------------------------------------------------
>
> Key: JBIDE-23759
> URL: https://issues.jboss.org/browse/JBIDE-23759
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Priority: Minor
> Fix For: 4.4.4.AM1
>
>
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.getLoadProxyWizardsScript(GettingStartedHtmlPage.java:519)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$10(GettingStartedHtmlPage.java:518)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$4.function(GettingStartedHtmlPage.java:234)
> at org.eclipse.swt.browser.WebSite.Invoke(WebSite.java:833)
> at org.eclipse.swt.browser.WebSite$7.method6(WebSite.java:184)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23835) jbosstools .it.smoke tests fail, abort, or are unstable.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23835?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23835:
-------------------------------
Fix Version/s: 4.5.0.AM1
> jbosstools .it.smoke tests fail, abort, or are unstable.
> --------------------------------------------------------
>
> Key: JBIDE-23835
> URL: https://issues.jboss.org/browse/JBIDE-23835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests
> Affects Versions: 4.4.3.Final
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.5.0.AM1
>
>
> All of the .it.smoke tests listed in this buildflow job [1] result in either an unstable build, a failed build, or an aborted build.
> [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> We need to get these jobs to green or they're meaningless as a measurement tool at the end of every sprint.
> {code}aerogear.it.smoke #14 completed: UNSTABLE
> batch.it.smoke #2 completed: FAILURE
> browsersim.it.smoke #15 completed: FAILURE
> cdi.it.smoke #15 completed: FAILURE
> cdk.devstudio.it.smoke #2 completed: UNSTABLE
> central.it.smoke #184 completed: FAILURE
> docker.it.smoke #192 completed: UNSTABLE
> examples.javaee.it.smoke #30 completed: FAILURE
> forge.it.smoke #24 completed: ABORTED
> freemarker.it.smoke #3 completed: ABORTED
> hibernate.it.smoke #18 completed: ABORTED
> jax-rs.it.smoke #5 completed: ABORTED
> jax-ws.it.smoke #5 completed: ABORTED
> jsf.it.smoke #3 completed: FAILURE
> jst.it.smoke #42 completed: FAILURE
> livereload.it.smoke #8 completed: FAILURE
> maven.it.smoke #33 completed: FAILURE
> vpe.it.smoke #7 completed: FAILURE
> websocket.it.smoke #4 completed: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month