May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22380) New Application wizard: project is not preselected (nor can you select any) if launched from explorer

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22380?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22380: ----------------------------------------------- [~adietish], [~jcantrill], please take a look. My guess how to reproduce this issue is: ASSERT: have a connection and project in OpenShift explorer EXEC: in OpenShift explorer: select a project and pick 'Deploy Docker Image...' from the context menu EXEC: close deploy docker wizard (try 2 use cases, either with cancel, or with finish) EXEC: in OpenShift explorer: on the same project pick 'New > Application' from the context menu CHECK: If this issue is reproduced. > New Application wizard: project is not preselected (nor can you select any) if launched from explorer > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22380 > URL: https://issues.jboss.org/browse/JBIDE-22380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > Attachments: project-not-preselected.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22380) New Application wizard: project is not preselected (nor can you select any) if launched from explorer

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22380?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22380 at 5/20/16 2:28 PM: ------------------------------------------------------------------------ [~adietish], [~jcantrill], please take a look at the pull request. My guess how to reproduce this issue is: ASSERT: have a connection and project in OpenShift explorer EXEC: in OpenShift explorer: select a project and pick 'Deploy Docker Image...' from the context menu EXEC: close deploy docker wizard (try 2 use cases, either with cancel, or with finish) EXEC: in OpenShift explorer: on the same project pick 'New > Application' from the context menu CHECK: If this issue is reproduced. was (Author: scabanovich): [~adietish], [~jcantrill], please take a look. My guess how to reproduce this issue is: ASSERT: have a connection and project in OpenShift explorer EXEC: in OpenShift explorer: select a project and pick 'Deploy Docker Image...' from the context menu EXEC: close deploy docker wizard (try 2 use cases, either with cancel, or with finish) EXEC: in OpenShift explorer: on the same project pick 'New > Application' from the context menu CHECK: If this issue is reproduced. > New Application wizard: project is not preselected (nor can you select any) if launched from explorer > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22380 > URL: https://issues.jboss.org/browse/JBIDE-22380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > Attachments: project-not-preselected.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22355: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing BUILD_ALIAS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22372: ------------------------------- Fix Version/s: 4.4.0.Alpha3 > Publish CI snapshots to a directory containing BUILD_ALIAS > ---------------------------------------------------------- > > Key: JBIDE-22372 > URL: https://issues.jboss.org/browse/JBIDE-22372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > To avoid even more "crossing streams", we could consider also adding the BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a new version wouldn't require to cleanup the /4.4.neon branch for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22369) Move parent pom to 4.4.0.Alpha2-SNAPSHOT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22369?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22369: ------------------------------- Fix Version/s: 4.4.x > Move parent pom to 4.4.0.Alpha2-SNAPSHOT > ---------------------------------------- > > Key: JBIDE-22369 > URL: https://issues.jboss.org/browse/JBIDE-22369 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.x > > > Now that we're past 4.4.0.Alpha1, shouldn't the parent pom be moved to Alpha2? That's what we're currently working on in this sprint, right? > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3611) update tools.jboss.org for developers.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3611?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3611: ---------------------------------- Unclear what needs to be done here. [~xcoulon] [~maxandersen] [~akazakov] can you flesh out where this branding change would happen on tools.jboss.org? Will we just change the "JBoss Tools" header [1] to the new one on devstudio.redhat.com [2] ? [1] http://tools.jboss.org/downloads/ [2] https://devstudio.jboss.com/10.0/staging/updates/ Or is there more we need to do here? > update tools.jboss.org for developers.redhat.com branding > ---------------------------------------------------------- > > Key: JBDS-3611 > URL: https://issues.jboss.org/browse/JBDS-3611 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3611) update tools.jboss.org for developers.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3611?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-3611: -------------------------------- Assignee: Nick Boldt > update tools.jboss.org for developers.redhat.com branding > ---------------------------------------------------------- > > Key: JBDS-3611 > URL: https://issues.jboss.org/browse/JBDS-3611 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3611) update tools.jboss.org for developers.redhat.com branding

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3611?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3611: ----------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > update tools.jboss.org for developers.redhat.com branding > ---------------------------------------------------------- > > Key: JBDS-3611 > URL: https://issues.jboss.org/browse/JBDS-3611 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Fix Version/s: 4.4.0.Alpha3 > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Fix Version/s: (was: 4.4.0.Alpha2) > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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