July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24568) Review all tests for Docker Tooling in upstream

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24568?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24568: ---------------------------------- Description: Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519932 > Review all tests for Docker Tooling in upstream > ----------------------------------------------- > > Key: JBIDE-24568 > URL: https://issues.jboss.org/browse/JBIDE-24568 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.Final > > > Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=519932 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23308) Include Show in Terminal for CDK server adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23308?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23308. --------------------------------- Mm, ok, but in that case Show In Console should work, right? And it's currently disabled (since cdk 2). So I created JBIDE-24748 for that. > Include Show in Terminal for CDK server adapter > ----------------------------------------------- > > Key: JBIDE-23308 > URL: https://issues.jboss.org/browse/JBIDE-23308 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.0.Final > > > As a follow up of JBIDE-21611 I noticed that Show in Console is now disabled for cdk server. That is correct as we've switched to the Terminal view for cdk. Would it be possible at all to add Terminal to the show in menu? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24748) Enable Show In Console for cdk 3

by Martin Malina (JIRA)

Martin Malina created JBIDE-24748: ------------------------------------- Summary: Enable Show In Console for cdk 3 Key: JBIDE-24748 URL: https://issues.jboss.org/browse/JBIDE-24748 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.5.0.AM2 Reporter: Martin Malina Assignee: Rob Stryker CDK 2 used the Terminal view, CDK 3 switched back to usiong Console view. So Show In Console on the server adapter should be enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24747) Left menu with versions gets broken after clicking on older item

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24747: ------------------------------------- Summary: Left menu with versions gets broken after clicking on older item Key: JBIDE-24747 URL: https://issues.jboss.org/browse/JBIDE-24747 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.5.0.AM2 Reporter: Josef Kopriva Attachments: image-2017-07-20-10-48-34-111.png, image-2017-07-20-10-49-14-391.png Left menu with versions in Whats New part of documentation is not working correctly. Menu before clicking on version 4.4.3.Final: !image-2017-07-20-10-48-34-111.png|thumbnail! After: !image-2017-07-20-10-49-14-391.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24690) For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools-extras]

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24690?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24690: ----------------------------------------- for the version, 2 versions are changed: {quote}[INFO] --- tycho-versions-plugin:0.26.0:set-version (default-cli) @ fuse-extras --- [INFO] Making changes in C:\git\jbosstools-fuse-extras [INFO] pom.xml//project/version: 1.0.0-SNAPSHOT => 10.0.0-SNAPSHOT [INFO] Making changes in C:\git\jbosstools-fuse-extras\jboss-fuse-sap-tool-suite [INFO] pom.xml//project/parent/version: 1.0.0-SNAPSHOT => 10.0.0-SNAPSHOT{quote} Seems that these versions were kept to 1.0.0 since the beginning and only submodules were updated to 10.0.0-SNAPSHOT Not sure of the impact to update them (I see none for now) > For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools-extras] > ----------------------------------------------------------------------------- > > Key: JBIDE-24690 > URL: https://issues.jboss.org/browse/JBIDE-24690 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Aurélien Pupier > Priority: Blocker > Labels: task > Fix For: 4.5.0.Final > > > For JBIDE 4.5.0.Final [fusetools-extras]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-24682: ------------------------------------------- I created https://issues.jboss.org/browse/CDK-150 on the CDK side. Can we go ahead with the approach of aligning CDK's version string with Minishift's current format? > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-24682: ------------------------------------------- {quote} Escalating this issue. Ondrej Dockal Really good catch. Thanks for being so on-the-ball here. {quote} +1. This is really a regression on side of the Minishift/CDK team. We need to see what the best way forward is on this one. For what it's worth, the change comes from this issue - https://github.com/minishift/minishift/issues/924 - which originated from the community. The version output of Minishift differed cute substantially from the version output of related tools like Minikube, oc, OpenShift, etc. We aligned the Minishift version string, forgetting that it is used by JBIDE server adapter. We had no unit test (and/or comment) which warned us from making a change without reaching out first. The unit test exists now (against the new format) and we will for sure add a comment to the code moving forward. {quote} Output of 'minishift version' was (and is) expected to follow a consistent format at the bare minimum. {quote} Correct. {quote} If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... {quote} That would be my suggestion as well. Right now the format is not consistent, but it should be. It seems people prefer the format without colon, so I suggest to make the CDK version string consistent with the current Minshift format. For the server adapter it would probably mean to split the lines at the whitespace, in order to get the key value pairs. > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1144) Cannot install SwitchYard Tooling with a standalone installer nor from update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1144?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1144: ------------------------------------- Summary: Cannot install SwitchYard Tooling with a standalone installer nor from update site (was: Cannot install SwitchYard Tooling with a standalone installer) > Cannot install SwitchYard Tooling with a standalone installer nor from update site > ---------------------------------------------------------------------------------- > > Key: JBTIS-1144 > URL: https://issues.jboss.org/browse/JBTIS-1144 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.GA > Reporter: Andrej Podhradsky > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: 1500536110156.log, devstudiois-error.txt > > > Cannot install SwitchYard Tooling with a standalone installer. > {code} > Missing requirement: SwitchYard 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) requires 'org.jboss.ide.eclipse.freemarker.feature.feature.group 1.2.0' but it could not be found > {code} > Please see the attachments for full error messages. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1144) Cannot install SwitchYard Tooling with a standalone installer nor from update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1144?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1144: ------------------------------------------ The following error occurs when installing SY from update site {code} Cannot complete the install because one or more required items could not be found. Software being installed: SwitchYard BPEL Support 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.bpel.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) Missing requirement: SwitchYard 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) requires 'org.jboss.ide.eclipse.freemarker.feature.feature.group 1.2.0' but it could not be found Cannot satisfy dependency: From: SwitchYard BPEL Support 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.bpel.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) To: org.switchyard.tools.feature.feature.group 0.0.0 {code} > Cannot install SwitchYard Tooling with a standalone installer nor from update site > ---------------------------------------------------------------------------------- > > Key: JBTIS-1144 > URL: https://issues.jboss.org/browse/JBTIS-1144 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.GA > Reporter: Andrej Podhradsky > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: 1500536110156.log, devstudiois-error.txt > > > Cannot install SwitchYard Tooling with a standalone installer. > {code} > Missing requirement: SwitchYard 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) requires 'org.jboss.ide.eclipse.freemarker.feature.feature.group 1.2.0' but it could not be found > {code} > Please see the attachments for full error messages. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1144) Cannot install SwitchYard Tooling with a standalone installer

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1144: ---------------------------------------- Summary: Cannot install SwitchYard Tooling with a standalone installer Key: JBTIS-1144 URL: https://issues.jboss.org/browse/JBTIS-1144 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 11.0.0.GA Reporter: Andrej Podhradsky Priority: Blocker Fix For: 11.0.0.GA Attachments: 1500536110156.log, devstudiois-error.txt Cannot install SwitchYard Tooling with a standalone installer. {code} Missing requirement: SwitchYard 2.4.0.CR1-v20170717-1303-B16 (org.switchyard.tools.feature.feature.group 2.4.0.CR1-v20170717-1303-B16) requires 'org.jboss.ide.eclipse.freemarker.feature.feature.group 1.2.0' but it could not be found {code} Please see the attachments for full error messages. -- 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 July 2017