March 2016 - jbosstools-issues - Jboss List Archives

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

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-21863. ----------------------------------- Resolution: Done Should be fixed as part of JBIDE-21449 > 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)

10 years

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: ------------------------------- Fix Version/s: (was: 4.3.1.CR1) > 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 > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21847: ----------------------------------------------- [~mlabuda], and if after this message appears you quickly flip 'Use free ports' on and off, will StartAll button get enabled? > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21847 > URL: https://issues.jboss.org/browse/JBIDE-21847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: video.ogg-2.ogv > > > In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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.3.1.CR1) > 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 > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21796) [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21796?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21796: ------------------------------- Fix Version/s: (was: 4.3.1.CR1) > [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21796 > URL: https://issues.jboss.org/browse/JBIDE-21796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: bzira.log.txt > > > Was reported today that Eclipse bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=488373 was not created as an ERT issue. > So I re-ran bzira like this: > {code} > python -W ignore bzira.py -u JIRA_USER -p JIRA_PWD -s https://issues.jboss.org -S 2016-02-24 -v > {code} > And got this when creating ERT-82: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-82 > JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > Curiously, the same error was thrown when creating ERT-88: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-88 > > Jira ERT-82 gave following errors: > Could not perform transition{'id': '4'} error: JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > full log: [^bzira.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21705) update tools.jboss.org/usage with error reporting tracking details

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21705?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21705: ------------------------------------ Threw some edits onto the PR; we can wait until QE confirms & closes JBDS-3566, JBDS-3600 on supported platforms (not my ancient FC20 box). :D > update tools.jboss.org/usage with error reporting tracking details > ------------------------------------------------------------------ > > Key: JBIDE-21705 > URL: https://issues.jboss.org/browse/JBIDE-21705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, usage > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > usage page should not just talk about Google analytics, but aslo about error reporting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3671: -------------------------------- Fix Version/s: 9.1.0.GA > sshd needs to be installed and started > -------------------------------------- > > Key: JBDS-3671 > URL: https://issues.jboss.org/browse/JBDS-3671 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 9.1.0.CR1, 9.1.0.GA > > > As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container. > docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues. > An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that > * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg... > * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH > I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach. > Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3637) Bundled installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3637?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3637: -------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > Bundled installer > ----------------- > > Key: JBDS-3637 > URL: https://issues.jboss.org/browse/JBDS-3637 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.GA > > > Provide a version of the installer with all pieces already included, so no downloads are required, for all pieces that have an appropriate license. > VirtualBox will always need to be downloaded, unless we build from source. > JBDS can not be bundled until https://issues.jboss.org/browse/JBDS-3557 is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Marián Labuda reassigned JBDS-3552: ----------------------------------- Assignee: Marián Labuda (was: Fred Bricon) > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, openshift > Reporter: Max Rydahl Andersen > Assignee: Marián Labuda > Priority: Critical > Fix For: 9.1.0.CR1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-571: ----------------------------------------- Nicolas, what is the SwitchYard version of the project that you are having issues getting to start in the workbench? 2.0.0.Final? > Error loading file switchyard.xml. Unable to load the generated resource. > ------------------------------------------------------------------------- > > Key: JBTIS-571 > URL: https://issues.jboss.org/browse/JBTIS-571 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: nicolas duminil > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: jbtis-571_1.png, jbtis-571_2.png, Screencast_JBDS900GA_JBDSISAlpha2.webm > > > After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process. > Tested on Windows 7 and Windows 10 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016