[JBoss JIRA] (JBIDE-17410) Old Cordova version for default Mobile Hybrid Engine
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17410?page=com.atlassian.jira.plugi... ]
Karel Piwko resolved JBIDE-17410.
---------------------------------
Resolution: Cannot Reproduce Bug
I can't reproduce this issue anymore. It must have been fixed by importing project as Cordova project.
> Old Cordova version for default Mobile Hybrid Engine
> ----------------------------------------------------
>
> Key: JBIDE-17410
> URL: https://issues.jboss.org/browse/JBIDE-17410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: Environment:
> RHEL7 latest, 64bit
> JBDS 8.0.0.Beta1
> MHT installed
> Reporter: Karel Piwko
> Fix For: 4.2.0.Beta2
>
>
> If I install JBDS and MHT, without adding Android SDK and selecting Mobile Hybrid Engine, Cordova version used is 3.1.0.
> It should be 3.4.0, [~maschmid] to confirm.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17405) Visual editor does not work in RHEL7
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17405?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-17405:
-------------------------------------
Verified in Beta2.
> Visual editor does not work in RHEL7
> ------------------------------------
>
> Key: JBIDE-17405
> URL: https://issues.jboss.org/browse/JBIDE-17405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Environment: RHEL7 latest, 64bit
> JBDS 8.0.0.Beta1
> MHT installed
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
>
> When an html file is opened, if fails with an exception and later it asks for closing the workbench as SWT error is considered severe.
> Here is the log:
> {code}
> !SESSION 2014-05-23 14:27:10.952 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.vpe 4 0 2014-05-23 14:27:34.476
> !MESSAGE Could not open the Visual Page Editor:
> No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> !STACK 0
> org.eclipse.swt.SWTError: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.browser.MozillaDelegate.<init>(MozillaDelegate.java:58)
> at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:684)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:118)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128)
> at org.jboss.tools.vpe.editor.mozilla.XulRunnerEditor2.<init>(XulRunnerEditor2.java:23)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:606)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:812)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:282)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1083)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:510)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:358)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:137)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:98)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:318)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:125)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:958)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1227)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:96)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$6.run(PartRenderingEngine.java:527)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:512)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:61)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:958)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:642)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveRenderer.processContents(PerspectiveRenderer.java:59)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:103)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:77)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:67)
> at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:659)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:654)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:744)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:715)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:709)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:694)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1051)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> 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:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> !ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2014-05-23 14:28:18.431
> !MESSAGE Unexpected error loading extension: org.eclipse.equinox.p2.metadata.repository.compositeRepository
> !STACK 0
> java.lang.IllegalStateException: BundleContext is no longer valid
> at org.eclipse.osgi.internal.framework.BundleContextImpl.checkValid(BundleContextImpl.java:983)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.getServiceReference(BundleContextImpl.java:559)
> at org.eclipse.equinox.internal.p2.core.helpers.ServiceHelper.getService(ServiceHelper.java:63)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.getSharedPreferences(AbstractRepositoryManager.java:512)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.restoreRepositories(AbstractRepositoryManager.java:1016)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.getRepositoryProperty(AbstractRepositoryManager.java:564)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:686)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.getAvailableRepositories(UpdateChecker.java:151)
> at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.checkForUpdates(UpdateChecker.java:129)
> at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker$UpdateCheckThread.run(UpdateChecker.java:73)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBTIS-280) Update JBT IS TP build to latest tycho (and discover missing dependencies!)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-280?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-280:
----------------------------------
No, I assumed it was intentional. Can you report it? Steps to reproduce:
a) given a .target file with version="0.0.0", eg., https://github.com/jbosstools/jbosstools-integration-stack/blob/d7e995042...
b) mvn install -Pisbtp2repo -Dmirror-target-to-repo.includeSources=true
> Update JBT IS TP build to latest tycho (and discover missing dependencies!)
> ---------------------------------------------------------------------------
>
> Key: JBTIS-280
> URL: https://issues.jboss.org/browse/JBTIS-280
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.2.0.Alpha1-TP
> Reporter: Nick Boldt
>
> Wanted to see if the JBT IS TP could fetch sources, and it can. As it was building, I noticed that you're using Tycho 0.18.1 (not 0.20.0 or 0.21.0-SNAPSHOT) and a very old version of org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0.CR2.
> So, I bumped you up to 0.20.0 and 0.19.0-SNAPSHOT, and got this error:
> {code}
> Unable to satisfy dependency from
> org.springframework.osgi.io 1.2.1 to
> package org.springframework.util [2.5.6,4.0.0).;
> No solution found because the
> problem is unsatisfiable.
> {code}
> Attached is a PR which shows what I tried, how it failed, and what I tried to do to fix it.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17497) Servertools plugin heirarchy causes issues for clients
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17497?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17497:
--------------------------------
Summary: Servertools plugin heirarchy causes issues for clients (was: Servertools plugin heirarchy has large problem)
> Servertools plugin heirarchy causes issues for clients
> ------------------------------------------------------
>
> Key: JBIDE-17497
> URL: https://issues.jboss.org/browse/JBIDE-17497
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
> Priority: Critical
> Attachments: 2014-06-02 19.07.bmml, 2014-06-02 19.07.png
>
>
> The plugin heirarchy of ASTools is better than it used to be, but not good enough for what current consumers of ASTools need it for.
> The problem is simple. There are 3 types of clients using ASTools API:
> 1) Those who need all of ASTools installed (including server adapter)
> 2) Those who only want access to interfaces, to use *if* server adapters is installed (do NOT want as.core force installed)
> 3) Those who create their own server adapters, want to use interfaces and some impl classes, but do not want as.core (server adapters) installed.
> Those of group 1 are no problem.
> Those of group 2 want as.wtp.core and as.wtp.ui to be minimal implementations with very few (near-zero) dependencies
> Those of group 3 want as.wtp.core and as.wtp.ui to provide as much functionality as possible, including things like zipping archives, or integration with download runtimes.
> An example of group 1 is jbosstools-central.
> An example of group 2 is ESB / BPEL
> An example of group 3 is FuseIDE
> Currently, there are classes in plugins positioned above as.core (ie, depend on as.core) that would be useful to FuseIDE (integration with stacks / runtimes / archives), but pushing these classes down into as.wtp.core / as.wtp.ui would mean the as.wtp.* plugins now require archives / stacks / yaml, and then so does bpel / esb.
> There needs to be another set of core/ui plugins for extenders or implementers that do NOT bring in the server adapters.
> Alternatively, we could move the server adapters out of as.core / as.ui and into two new higher-level plugins, as.serveradapter.core / as.serveradapter.ui, leaving as.core/as.ui as the new plugins to be extended by fuse-ide.
> There are of course other possible solutions, but all possible solutions basically require new plugins with substantial class movement.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17453:
-------------------------------------
After "unsigning" my tc, I am able to replicate this
> Error while validating credentials in Download Runtime dialog
> -------------------------------------------------------------
>
> Key: JBIDE-17453
> URL: https://issues.jboss.org/browse/JBIDE-17453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta2
> Reporter: Radoslav Rábara
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.Beta2
>
> Attachments: credentials validation error.jpg
>
>
> After validation of valid credentials, the following error message appears
> {code}
> "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200"
> {code}
> I was able to reproduce this issue only with one of mine jboss.org accounts.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17404) Cordova Sim cannot be launched on RHEL7
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-17404:
-------------------------------------
In Beta 2:
Default behavior says: {code}
Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
Stack trace:
org.eclipse.swt.SWTError: To use CordovaSim please install webkitgtk 1.2.0 or higher or run CordovaSim with Oracle Java 7u7 and higher.
at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:107)
at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89)
org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 47801 was stopped
{code}
I have both GTK2 and GTK3 webkits installed, running on OpenJDK. Switching to Oracle JDK fixes the issue.
I can't run on GTK3 anymore. Should I reopen or create a new bug?
> Cordova Sim cannot be launched on RHEL7
> ---------------------------------------
>
> Key: JBIDE-17404
> URL: https://issues.jboss.org/browse/JBIDE-17404
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Environment: RHEL7 latest, 64bit
> Installed webkitgtk3-devel 0:2.0.4-6-el7
> TicketMonster Cordava example from latest WFK
> JBDS 8.0.0.Beta1
> OpenJDK 7
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta2
>
>
> Launching BrowserSim fails with NPE, adding information from workspace log
> Before webkitgtk3-devel is installed
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162
> !MESSAGE BrowserSim is failed to start with the following error:
> "No more handles"
> Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
> If not, use your package manager to install libwebkitgtk.
> Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84)
> {code}
> After:
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395
> !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17408) jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17408?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-17408 at 6/2/14 11:47 AM:
----------------------------------------------------------------
Nick, after playing with features to restrict the tern version I got to the same decision :) but I used closed range
{code}[0.2.0.201405210810,0.2.0.201405210811){code}
to be sure it is working.
probably open range with version with qualifier you suggested above has the same effect, but we have to test it to be sure.
was (Author: dgolovin):
Nick, after playing with features to restrict the tern version I got to the same decision :) but I usd closed range
{code}[0.2.0.201405210810,0.2.0.201405210811){code}
to be sure it is working.
probably open range with version with qualifier you suggested above has the same effect, but we have to test it to be sure.
> jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17408
> URL: https://issues.jboss.org/browse/JBIDE-17408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Beta3
>
>
> Max says (paraphrasing):
> "The JSDT stuff should be locked down so that it depends on a specific version of tern.java, not just any version. We want it so that users can only install the version of tern.java we include in our TP."
> Currently, this is 0.2.0.201405210810.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17408) jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17408?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17408:
---------------------------------------
PR looks good to me. It was originally for Beta3, so I didn't push it, because I don't know how version range with qualifier works in updates.
> jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17408
> URL: https://issues.jboss.org/browse/JBIDE-17408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Beta3
>
>
> Max says (paraphrasing):
> "The JSDT stuff should be locked down so that it depends on a specific version of tern.java, not just any version. We want it so that users can only install the version of tern.java we include in our TP."
> Currently, this is 0.2.0.201405210810.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months