January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3583: ------------------------------------- I don't have Mac, but will try on Windows and Linux. > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.Beta2, 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installed and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows and error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3583: ------------------------------------ Assignee: Snjezana Peco [~snjeza] could you please take a look? > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.Beta2, 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installed and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows and error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3583: --------------------------------- Fix Version/s: 9.1.0.Beta2 9.1.0.CR1 10.0.0.Alpha1 > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.Beta2, 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installed and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows and error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21464) Delete context menu of OpenShift elements is incorrect

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21464?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21464: ----------------------------------------------- Taken from https://msdn.microsoft.com/en-us/library/windows/desktop/dn742392%28v=vs.... : "Proper use of ellipses is important to indicate that users can make further choices before performing the action, or even cancel the action entirely. The visual cue offered by an ellipsis allows users to explore your software without fear. This doesn't mean you should use an ellipsis whenever an action displays another window—only when additional information is required to perform the action. For example, the commands About, Advanced, Help, Options, Properties, and Settings must display another window when clicked, but don't require additional information from the user. Therefore they don't need ellipses." Here _additional information_ are key words. Confirmation dialog for 'Delete' does not ask for additional information, it warns user and prompts him to check his decision. > Delete context menu of OpenShift elements is incorrect > ------------------------------------------------------ > > Key: JBIDE-21464 > URL: https://issues.jboss.org/browse/JBIDE-21464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta2 > > > Currently OpenShift tree items in OpenShift Explorer view have "Delete" context menu item. Previously it was more natural, because we had "Delete connection(s)..." "Delete domain..." etc., not it is all "Delete". > If just plain "Delete" is considered as a good way to go, at least there should be three dots as suffix, because after click on the context menu Delete there is required user confirmation of deletion. So it should be at least "Delete...". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21479) Explorer: Display deployment details like web console

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21479?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21479: ---------------------------------- Labels: openshift_deployment_view (was: ) > Explorer: Display deployment details like web console > ----------------------------------------------------- > > Key: JBIDE-21479 > URL: https://issues.jboss.org/browse/JBIDE-21479 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21479) Explorer: Display deployment details like web console

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21479: ------------------------------------- Summary: Explorer: Display deployment details like web console Key: JBIDE-21479 URL: https://issues.jboss.org/browse/JBIDE-21479 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Fix For: 4.3.1.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-471: ---------------------------------- And another quick question - is this still current for jboss tools bpel ? http://download.jboss.org/jbosstools/mars/integration/updates/integration... thanks [~bbrodt] (who'd bug you if we didn't???? :) > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21475) Use vagrant.bat to start vagrant

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21475?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-21475: ------------------------------------------- -1, in fact I think just {{vagrant}} should be used under the assumption that the PATH is properly configured. If Vagrant was already installed on the system and subsequently skipped by the user, we need to use the system Vagrant. Subsequently, our installer should not only copy the Vagrant binaries, but also setup the PATH correctly. > Use vagrant.bat to start vagrant > -------------------------------- > > Key: JBIDE-21475 > URL: https://issues.jboss.org/browse/JBIDE-21475 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Environment: Windows > Reporter: Denis Golovin > Priority: Blocker > > CDK adapter uses %VRGANT_PATH%\bin\vagrant to start vagrant on windows, but vargant file is a shell script. vagrant.bat should be used instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-471: ---------------------------------- Oh, and if 1.0.5 is your Mars stream, and 1.0.6 is your Neon stream... what happens if you have to do maintenance on your 1.0.5 stream? You can't call it 1.0.6 because that's your Neon stream. So... I'd suggest either calling your Neon stream 1.0.100, or 1.1.0, so that you have room to increment in the Mars stream. Just in case. > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-471) Unify component versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-471: ---------------------------------- [~bbrodt] I think the question was: Are these two sites equivalent? * http://download.eclipse.org/bpel/updates/mars/1.0.5 (new with full qualifier) * http://download.eclipse.org/bpel/site/1.0.5 (1.0.5.Final, no qualifier) > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016