August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24803: --------------------------------------- I was trying to find out who wanted the DV download there in the first place. Radim found this: JBIDE-19402 It was requested by Max. But apparently in the past DV, just like FSW, included EAP in the installation. So it made sense somehow. But now that they only install on top of EAP, I'm not so sure anymore. > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4499) Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4499: ---------------------------------- Summary: Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher Key: JBDS-4499 URL: https://issues.jboss.org/browse/JBDS-4499 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: rpm Affects Versions: 11.0.0.GA Environment: DevTools repository: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-1.0-rh-ecli... Devstudio repository: https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Minor Fix For: 11.1.0.AM1 I have installed last staged build \[1\] and now I have this error message in the log after start: {code} !ENTRY org.eclipse.linuxtools.jdt.docker.launcher 4 0 2017-08-07 12:04:20.933 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.jdt.docker.launcher [1118] Another singleton bundle selected: osgi.identity; osgi.identity="org.eclipse.linuxtools.jdt.docker.launcher"; type="osgi.bundle"; version:Version="1.0.0.201708031854"; singleton:="true" at org.eclipse.osgi.container.Module.start(Module.java:444) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) {code} \[1\] https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... Content of /opt/rh/rh-eclipse47 {code} find /opt/rh/rh-eclipse47/ -iname "*org.eclipse.linuxtools.jdt.docker.launcher*" /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher.source_1.0.0.201708031854.jar /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708031854.jar /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708010032.jar {code} I don't see any impact to the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24519: --------------------------------------- [~apodhrad], can this JIRA be closed? > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fusetools > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24803: --------------------------------------- [~rob.stryker], I have a side question: Why do we even have the dv download in devstudio? Did someone requested it in the past? In stacks.yaml, it says it's a server of type eap. But it's not true. And so the result of the download workflow is a bit strange: 1. Go to Preferences -> Download runtime 2. Select JBoss DV 6.2 3. Where to download? It's a jar installer that I only need temporarily, so I'll use ~/tmp. installer jar is downloaded and started 4. Install JBoss DV over an existing EAP 6.4 installation - this will not affect whether or not said EAP 6.4 server is added to devstudio or not, you need to do that separately. 5. Finish JBoss DV installer, you're taken back to the download dialog in Eclipse 6. Now ~/tmp is added to runtime detection, but that doesn't have any effect - only the installer jar is located there. There is nothing to be added since dv just installed itself into your existing EAP 6.4 server - again, whether or not this server is setup in Eclipse is completely separate from this. DV has tooling in JBDSIS - Teiid designer. But there's still probably no notion of a server or runtime for DV there, is there? Or if there is, is there any way this download would only be available when JBDSIS is installed? > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20996: --------------------------------------- In the meantime, JBoss DV 6.2 was released (2016-08-10), so I created new JIRAs to have that added: JBIDE-24803 JDF-867 TBH, the value of having this available for download is a bit questionable - there is no runtime detector for dv is there? The warning is there, but I wonder how it works - it's not controlled by stacks.yaml: https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.y... So is it hardcoded somehow? What happens when the new dv requires eap 7? > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, upstream > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20996. --------------------------------- Closing, nothing to be done here. > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, upstream > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24803: ---------------------------------- Description: JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. I've also created JDF-867. was: JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. I've also created JDF-852. > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-867. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24803: ---------------------------------- Description: JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. I've also created JDF-852. was: JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. I've also created JDF-852. > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > > JBoss DV 6.3 has been released for some time now. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24803?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24803: ---------------------------------- Reporter: Martin Malina (was: Radim Hopp) > Add JBoss DV 6.3 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-24803 > URL: https://issues.jboss.org/browse/JBIDE-24803 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Reporter: Martin Malina > Assignee: Rob Stryker > > JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24803) Add JBoss DV 6.3 to Download Runtimes Wizard

by Martin Malina (JIRA)

Martin Malina created JBIDE-24803: ------------------------------------- Summary: Add JBoss DV 6.3 to Download Runtimes Wizard Key: JBIDE-24803 URL: https://issues.jboss.org/browse/JBIDE-24803 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection Reporter: Radim Hopp Assignee: Rob Stryker JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. I've also created JDF-852. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017