April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22245) Application Wizard: Resource label key has wrong label

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22245?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22245: -------------------------------- Story Points: 1 > Application Wizard: Resource label key has wrong label > ------------------------------------------------------ > > Key: JBIDE-22245 > URL: https://issues.jboss.org/browse/JBIDE-22245 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3, ux > Fix For: 4.4.x > > > In New Application wizard on the page with labels, if I select to create/edit an existing label there is opened a dialog with label details. Label consists of key:value pair (it comes from kubernetes concept), but in this labels of text widgets are "Label:" and "Value:". I think we should have it labeled as "Key:" and "Value:" instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-167) Node.js launch is still available for closed / deleted projects [EBZ#492478]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-167: --------------------------------------- Summary: Node.js launch is still available for closed / deleted projects [EBZ#492478] Key: ERT-167 URL: https://issues.jboss.org/browse/ERT-167 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot If the project is closed / removed the launch configuration is still runable via Run Configurations -> Node.js Application. It is expected that all project launches will be unavailable though. Basically, the "Project" field should be created for Node.js Launch configuration in order to tight launches to appropriate projects -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21785: ------------------------------- Priority: Blocker (was: Major) > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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: ------------------------------- Priority: Blocker (was: Major) > 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: Blocker > Fix For: 4.4.0.Alpha1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22226: ---------------------------------- Component/s: project-examples upstream (was: forge) > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Reporter: Burr Sutter > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha2 > > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22226) Forge Wizard Cheatsheet Line Bug when moving backwards

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22226?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-22226: --------------------------------------- I can't reproduce the issue on Windows and Linux. Suppose, it is an upstream bug related to SWT links on Mac. [~burrsutter], Could you try to reproduce the issue using the latest Neon build? > Forge Wizard Cheatsheet Line Bug when moving backwards > ------------------------------------------------------ > > Key: JBIDE-22226 > URL: https://issues.jboss.org/browse/JBIDE-22226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Burr Sutter > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha2 > > > See the video > http://screencast.com/t/xmTabea5I -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19911: ---------------------------------------- Alternative approach: * Generating the change ** Job mirrors sourceSite ** job publishes mirror (scp) it to targetMirror ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** Job generates PR * Verifying and annotating PR ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** p2diff Those 2 parts can be implemented sepearately. The part about verification is/should be a subset of the actual TP build, the only difference is that it doesn't upload new snapshot Maven artifacts nor site. > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.4.x > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2044: ----------------------------------- Patch has been merged into upstream m2e > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-2044: --------------------------------- Assignee: Nick Boldt (was: Fred Bricon) > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.0.0.Alpha1 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21863. --------------------------------- > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21863 > URL: https://issues.jboss.org/browse/JBIDE-21863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016