August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26167: ------------------------------------- Fix Version/s: 4.9.x > Import application: error message when trying to import from binary build config is not helpful > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-26167 > URL: https://issues.jboss.org/browse/JBIDE-26167 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Labels: import_wizard > Fix For: 4.9.x > > Attachments: import-error.png > > > steps: > # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc" > {code}oc login <openshift-server>{code} > # ASSERT: in cmd-line: make sure you that you selected a project in "oc" > {code}oc project <openshift-project-name>{code} > # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > {code} > $ git clone https://github.com/redhat-helloworld-msa/hello > $ cd hello/ > $ oc new-build --binary --name=hello -l app=hello > $ mvn package -Popenshift > $ oc start-build hello --from-dir=. --follow > $ oc new-app hello -l app=hello,hystrix.enabled=true > $ oc expose service hello > {code} > # ASSERT: in Explorer: the application-service "hello" is visible > # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard > RESULT: > The import fails with the following error: > !import-error.png! > The error is correct, the application was created with a binary source type buildconfig, but the error not helpful. > Furthermore we should show up the impossibility *upfront*, before showing up the import wizard - not afterwards, when finishing the wizard. > Here's the build config (notice *"source" > "type" > "Binary"*): > {code} > { > "metadata": { > "name": "hello", > "namespace": "jbide25000-2", > "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello", > "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd", > "resourceVersion": "360688", > "creationTimestamp": "2018-07-01T07:06:26Z", > "labels": { > "app": "hello" > }, > "annotations": { > "openshift.io/generated-by": "OpenShiftNewBuild" > } > }, > "spec": { > "triggers": [ > { > "type": "GitHub", > "github": { > "secret": "N5TaoJVuWp-YBlwSktc3" > } > }, > { > "type": "Generic", > "generic": { > "secret": "ehzK2N2Yv8JDryRFLI5j" > } > } > ], > "runPolicy": "Serial", > "source": { > "type": "Binary", > "binary": {} > }, > "strategy": { > "type": "Docker", > "dockerStrategy": {} > }, > "output": { > "to": { > "kind": "ImageStreamTag", > "name": "hello:latest" > } > }, > "resources": {}, > "postCommit": {}, > "successfulBuildsHistoryLimit": 5, > "failedBuildsHistoryLimit": 5 > }, > "status": { > "lastVersion": 1 > }, > "kind": "BuildConfig", > "apiVersion": "v1" > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26168) Import application: branch label shows "null"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26168?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26168: ------------------------------------- Fix Version/s: 4.9.x > Import application: branch label shows "null" > --------------------------------------------- > > Key: JBIDE-26168 > URL: https://issues.jboss.org/browse/JBIDE-26168 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: import_wizard > Fix For: 4.9.x > > Attachments: checkout-branch-null.png > > > steps: > # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc" > {code}oc login <openshift-server>{code} > # ASSERT: in cmd-line: make sure you that you selected a project in "oc" > {code}oc project <openshift-project-name>{code} > # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > {code} > $ git clone https://github.com/redhat-helloworld-msa/hello > $ cd hello/ > $ oc new-build --binary --name=hello -l app=hello > $ mvn package -Popenshift > $ oc start-build hello --from-dir=. --follow > $ oc new-app hello -l app=hello,hystrix.enabled=true > $ oc expose service hello > {code} > # ASSERT: in Explorer: the application-service "hello" is visible > # EXEC: select the "hello" service and pick "Import Application..." & Look at "Check out branch" label > RESULT: > the label shows *null* > !checkout-branch-null.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26296?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26296: ------------------------------------ Now the question is... who builds m2e-apt, where, and when should a new release be released? cc: [~fbricon] > Remove JBoss from maven.apt feature.properties > ---------------------------------------------- > > Key: JBIDE-26296 > URL: https://issues.jboss.org/browse/JBIDE-26296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: > https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26289) Update version identifier to 5.4.1-SNAPSHOT

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26289?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26289. --------------------------------- > Update version identifier to 5.4.1-SNAPSHOT > ------------------------------------------- > > Key: JBIDE-26289 > URL: https://issues.jboss.org/browse/JBIDE-26289 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26296?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-26296: --------------------------------------- [~nickboldt] I don't think there's any reason for that. You asked on the original JIRA what others suggested and the answer was just "Red Hat". And if I look at a random PR from your JIRA, I can see similar places with only "Red Hat", no Inc: https://github.com/jbosstools/jbosstools-central/pull/434/files > Remove JBoss from maven.apt feature.properties > ---------------------------------------------- > > Key: JBIDE-26296 > URL: https://issues.jboss.org/browse/JBIDE-26296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: > https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26296?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26296: ------------------------------------ Commented. Should use "Red Hat, Inc." for attributions/contributions/copyrights, and "Red Hat" for providerName. > Remove JBoss from maven.apt feature.properties > ---------------------------------------------- > > Key: JBIDE-26296 > URL: https://issues.jboss.org/browse/JBIDE-26296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: > https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Include fix for m2e-core bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in JBT Target Platform

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26146. --------------------------------- Plugin is updated. Verified in: Red Hat Developer Studio Version: 12.9.0.AM2 Build id: AM2-v20180808-0721-B3149 Build date: 20180808-0721 > Include fix for m2e-core bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in JBT Target Platform > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.6.0.Final > > Attachments: Screenshot_2018-07-04_10-39-30.png > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26065) [Red Hat Central] Add connector for nodeclipse

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26065. --------------------------------- Installation is working without errors. Verified in: Red Hat Developer Studio Version: 12.9.0.AM2 Build id: AM2-v20180808-0721-B3149 Build date: 20180808-0721 > [Red Hat Central] Add connector for nodeclipse > ---------------------------------------------- > > Key: JBIDE-26065 > URL: https://issues.jboss.org/browse/JBIDE-26065 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, central-update, updatesite, upstream > Affects Versions: 4.6.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.Final > > Attachments: devstudio12-central.png, eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png > > > Steps to perform: > -a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability- > -b) add that to the 3rd party target platform used for building RH Central- > c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools* > (Mirroring step removed because we don't yet have confirmation from Legal that we are permitted to redistribute. So instead we'll just link to upstream remote site.) > The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2]. > > [1] http://www.nodeclipse.org/updates/ > [2] https://marketplace.eclipse.org/content/nodeclipse > !eclipse-marketplace-nodeclipse.png|thumbnail! > Installed size is about 111M for these 14 features: > {code} > org.nodeclipse_1.0.2.201509250223 > org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223 > org.nodeclipse.pluginslist.feature_1.0.2.201509250223 > com.eclipsesource.jshint.feature_0.10.1.20160216-0911 > de.bastiankrol.startexplorer.feature_1.7.0 > gitaddon.feature_1.0.0.20140303-0606 > markdown.editor.feature_1.2.0.201501260515 > net.mihai-nita.ansicon_1.3.1.201508091828 > pm.eclipse.editbox.feature_0.70.0.201508180438 > org.chromium.debug_0.3.9.201509250223 > org.chromium.sdk_0.3.9.201509250223 > tern-feature_1.1.0.201511082254 > tern-jsdt-feature_1.1.0.201511082254 > tern-server-nodejs-feature_1.1.0.201511082254 > {code} > If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA. > PR to do mirror, if licenses are allowed: > https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4708) Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4708?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-4708. ------------------------------- I have retested with steps provided and remediation has been shown. Closing. > Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently > --------------------------------------------------------------------------- > > Key: JBDS-4708 > URL: https://issues.jboss.org/browse/JBDS-4708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.GA > > Attachments: remediation-1.png, remediation-2.png, remediation-jbt-central.png > > > Problem appears to be a hard upper limit from org.sonatype.m2e.egit 0.15.0.20161027 on egit.core [3.0.0,5.0.0). > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > Software currently installed: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > Only one of the following can be installed at once: > Git integration for Eclipse - Core 4.11.0.201803080745-r (org.eclipse.egit.core 4.11.0.201803080745-r) > Git integration for Eclipse - Core 5.0.0.201805151920-m7 (org.eclipse.egit.core 5.0.0.201805151920-m7) > Git integration for Eclipse - Core 4.10.0.201712302008-r (org.eclipse.egit.core 4.10.0.201712302008-r) > Git integration for Eclipse - Core 5.0.0.201805221745-rc1 (org.eclipse.egit.core 5.0.0.201805221745-rc1) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > To: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpmdeps.feature.feature.group [12.0.0.v20180418-2342,12.0.0.v20180418-2342] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 12.0.0.v20180418-2342 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 12.0.0.v20180418-2342) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [5.0.0.201805151920-m7,5.0.0.201805151920-m7] > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit 0.15.0.201610271523) > To: osgi.bundle; org.eclipse.egit.core [3.0.0,5.0.0) > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit.feature.feature.group 0.15.0.201610271523) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit [0.15.0.201610271523,0.15.0.201610271523]{code} > As such we can either: > * install devstudio (which requires m2e.egit) and uninstall egit and egit.mylyn features to do so, or > !remediation-2.png|thumbnail! > * upgrade to egit 5.0.0.20180522 (rc1) and not be able to install devstudio 12.0.0.AM2. > !remediation-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26275) CDK itests stabilization on multiple platforms

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26275?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26275. --------------------------------- > CDK itests stabilization on multiple platforms > ---------------------------------------------- > > Key: JBIDE-26275 > URL: https://issues.jboss.org/browse/JBIDE-26275 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, integration-tests > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018