May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- I guess anything's possible... :) So - it stands to reason that the person who picks the 1.5Gb JBDSIS stand-alone installer with Fuse runtime wants to install Fuse Tooling. Should this installer have *just* Fuse Tooling + Fuse Runtime (or minimally pre-select Fuse Tooling). What about BRMS and Data Virt runtimes? SHould they also have a tooling-specific + runtime stand-alone installer? > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-654: ----------------------------------------- Yes, that's kind of what we're going for I think. One installer is JBDS + JBDSIS to simplify that down to one step. And it would be great to have a second installer that includes JBDS + JBDSIS + a Fuse server as well. I understand Lars' concern that the second one will be huge - the installer without the runtime right now is already nearly 1 gig (972,159 KB). I'm sure it will be well over a gigabyte with the runtime included. But as you say - "Some users like it simply to work when installed." I think that as an evaluator, having the whole enchilada just download and install at once would be exactly what I'm looking for. That doesn't mean that EVERY user is going to want to go that route. And it doesn't mean that it's the only runtime we support. It just means they have a single point to download, install, and try our stuff out. Space is fairly cheap I would hope. I do worry about testing time with QE, but if we can automate that as much as possible I'd hope that QE would see less impact with regular releases. So Paul, would it be possible to have a tooling-only installer and a tooling-plus-runtime installer? > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-710) Fix Ldap Import test

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-710: ---------------------------------- Summary: Fix Ldap Import test Key: JBTIS-710 URL: https://issues.jboss.org/browse/JBTIS-710 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.3.0.Final, 4.2.6.Final Reporter: Matus Makovy Assignee: Matus Makovy Fix For: 4.3.1.Final, 4.2.7.Final I deleted some files that were actually important for Ldap import tests. I have to add them back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-654: ------------------------------------------- btw. aren't you also saying it is annoying having to install Fuse after installing devstudio despite it has builtin support to automatically download it when users start the Fuse wizard - does the same reasoning not apply for runtimes ? Some users like it simply to work when installed. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-654: ------------------------------------------- you guys seem to miss we provide *two* installers already, one with and one without. The one with are great for trainings and for getting started experiences since when downloaded you have enough to start. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-166) Chromium Debug context menu's enabled for everything [EBZ#491480]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-166?page=com.atlassian.jira.plugin.sy... ] Shane Bryzak resolved ERT-166. ------------------------------ Resolution: Done > Chromium Debug context menu's enabled for everything [EBZ#491480] > ----------------------------------------------------------------- > > Key: ERT-166 > URL: https://issues.jboss.org/browse/ERT-166 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: Debug, bzira > > The context menu "V8 Debugging" is available for any type of selection. > I tracked this menu contribution to: "org.eclipse.wst.jsdt.chromium.debug.ui.ChromiumSourceFileActionsId.MenuId" > Should filter to only *.js files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22371) Allow users easily manage environment variables of OpenShift application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22371?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22371: --------------------------------------- [~adietish] you are right. This is not something directly related to Burr's demo. It's more like nice to have feature which can ease working with tooling. That is also a reason why I had set lower priority to this issue. > Allow users easily manage environment variables of OpenShift application > ------------------------------------------------------------------------ > > Key: JBIDE-22371 > URL: https://issues.jboss.org/browse/JBIDE-22371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.x > > > At the moment to add a new environment variable/edit an existing one. Environment variables are located at deployment configuration. At the moment it requires to open Properties view, select a deployment config, open context menu Edit... and find in json where the spot with env. vars is located and add more key:value pair or edit existing ones. It would be nice if we would have some dialog/wizard to easily manage variables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22376: ------------------------------------------ [~tmader] I see OpenShiftServerUtils#isEapStyle [looking for "eap" or "wildfly"|https://github.com/adietish/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.core/src/org/jboss/tools/openshift/core/server/OpenShiftServerUtils.java#L460] in the [docker image name|https://github.com/adietish/jbosstools-openshift/blob/master/plugins...] or [build config labels|https://github.com/adietish/jbosstools-openshift/blob/master/plugi...] [~jcantrill] [~kconner] do you know of a better way to know whether we're talking to a wildfly server on openshift? We could also try to talk to the wildfly mgmt-service (most likely requires those ports to be forwarded/exposed I guess) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Thomas Mäder > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21885) Properties: Remove "()" from context-menu name of Start Build

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21885: ------------------------------------------ [~scabanovich] yes that was my thought too (this being caused by the cmd parameter), but then I have no clue who's causing it. If your workaround works I'd go for it and if you have any chance to spot the culprit and notice Eclipse being at fault I'd file this to Eclipse bugzilla. > Properties: Remove "()" from context-menu name of Start Build > -------------------------------------------------------------- > > Key: JBIDE-21885 > URL: https://issues.jboss.org/browse/JBIDE-21885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: build-config-properties-menu.png, start-build.png > > > The "()" from context-menu name of Start Build should be removed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22243: ------------------------------------------ [~jcantrill] Isnt refreshing a build essential to watch the progress of a build (when you have problems in automatic refreshes)? > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016