April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-709: -------------------------------------------- > Article nearly ready at https://docs.google.com/document/d/1WV3FaJIfT4ovZWE29NLUT_Ji_LH1tVLu4lBpO... > Have to incorporate one code snippet that showed errors earlier > JBDS 9.1 GA: Document a use case for Forge Tooling > -------------------------------------------------- > > Key: TOOLSDOC-709 > URL: https://issues.jboss.org/browse/TOOLSDOC-709 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Forge > Fix For: 9.1 GA > > > Document a use case for Forge tooling. > 1. Draft a potential use case for what users may want to do with forge. > 2. Get review on use case idea from a relevant SME or QE person > 3. Write an intro and flesh out the use case with relevant screenshots > 4. Get QE review > 5. Create upstream and downstream versions of approved content. > a. Add CSP version to customer portal > b. Send Misha upstream version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21746) Too much info shown in log when deploying a docker image to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21746?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21746: ----------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done PR applied in master. Thanks [~scabanovich]! > Too much info shown in log when deploying a docker image to OpenShift > --------------------------------------------------------------------- > > Key: JBIDE-21746 > URL: https://issues.jboss.org/browse/JBIDE-21746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When deploying a docker image to OpenShift 3 server, there is too much logging in eclipse .log (in error log with severity info). For every created resource there is a message "Trying to create resource:" followed up by json of a resource. So for a deployed docker image it creates such info message for a new image stream, service, routing (if was checked) and deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-598) Cannot install JBTIS in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-598?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-598. ------------------------------ Resolution: Done Hey [~apodhrad] I don't mean to ping-pong this Jira but I believe these are the correct steps for the community offline install of JBTIS EA: Start with: eclipse-jee-mars-2-linux-gtk-x86_64.tar.gz 1. jbosstools-4.3.1.CR1b-updatesite-core.zip 2. jbosstoolstarget-4.52.0.Final.zip 3. jbosstools-integration-stack-target-4.3.1.Final-SNAPSHOT-earlyaccess.zip # changed the name 4. jbosstools-integration-stack-4.3.0.CR1a-earlyaccess.zip Does this work for you? > Cannot install JBTIS in offline mode > ------------------------------------ > > Key: JBTIS-598 > URL: https://issues.jboss.org/browse/JBTIS-598 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Beta1 > Environment: Eclipse Mars-2 for JEE developers > jbosstools-4.3.1.Beta2-updatesite-core.zip > jbosstools-integration-stack-4.3.0.Beta1-earlyaccess.zip > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.3.0.CR1 > > > {code} > Missing requirement: org.eclipse.bpmn2.modeler.core 1.2.3.Final-v20160226-1723-B97 requires 'bundle org.eclipse.emf.transaction 0.0.0' but it could not be found > Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.jboss.tools.locus.sf.saxon [9.5.1,10.0.0)' but it could not be found > Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.emf.compare.feature.group 2.1.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-97) Syntax Highighting for template literals [EBZ#488724]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-97?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-97: ---------------------------- Sprint: devex #4 March 2016, devex #6 April 2016 (was: devex #4 March 2016, devex #5 April 2016) > Syntax Highighting for template literals [EBZ#488724] > ----------------------------------------------------- > > Key: ERT-97 > URL: https://issues.jboss.org/browse/ERT-97 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Shane Bryzak > Labels: General, bzira > > Provide highlighting for ES6 Template strings[1] on JSDT editor. > [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Templat... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21112) D&D install is not working with Internet explorer 11 and MS Edge 20

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21112?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21112: --------------------------------------- I can't reproduce the issue on Windows 7, Internet Explorer 11.0.9600.18230, Mars.2 or Neon M6. [~rhopp], I don't have Windows 10 to test, but the issue can be caused using Windows on VirtualBox. Could you test the standard Windows 10? > D&D install is not working with Internet explorer 11 and MS Edge 20 > ------------------------------------------------------------------- > > Key: JBIDE-21112 > URL: https://issues.jboss.org/browse/JBIDE-21112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.0.Final > Environment: Windows 10 > Microsoft Edge 20.10240.16384.0 > Microsoft Internet Explorer 11.0.10240.16384 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: LATER > > > D&D (JBIDE-15499) links to Central from Edge or MS Explorer is not working. > Dropping the same link from Chrome triggers the installation. > The same issue is effecting Eclipse marketplace client. I've opened bug there: https://bugs.eclipse.org/bugs/show_bug.cgi?id=482588 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3753) Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3753?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3753: -------------------------------- Priority: Major (was: Blocker) > Installer forces using detected JDK, tries to install JBDS with the bundled Java anyway > --------------------------------------------------------------------------------------- > > Key: JBDS-3753 > URL: https://issues.jboss.org/browse/JBDS-3753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160401-28 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > Using bundled installer build 28 - confirmation page will not let me use the bundled JDK if it detects a pre-existing JDK somewhere else. > Once the installation is triggered, JDK goes straight to finished (not a problem under these circumstances) but JBDS fails right away and the log says: > {noformat} > Fri, 01 Apr 2016 07:20:44 GMT-INFO: jbds - Execute c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zSE006.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds - > Fri, 01 Apr 2016 07:20:44 GMT-ERROR: jbds failed to install: Error: spawn c:\DeveloperPlatform\jdk8\bin\java.exe ENOENT > {noformat} > So basically, I can't get it to install the bundled JDK but it will still try to use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3718: ------------------------------------- No JDK detection will be provided in first release. > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3718: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3718: -------------------------------- Priority: Major (was: Blocker) > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3718: ----------------------------- > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016