May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21163) cdk server adapter dumps out adbinfo to console

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21163?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21163. --------------------------------- Verified in JBDS 10.0.0.Alpha2 > cdk server adapter dumps out adbinfo to console > ----------------------------------------------- > > Key: JBIDE-21163 > URL: https://issues.jboss.org/browse/JBIDE-21163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1, 4.4.0.Alpha1 > > > is it intended that if the cdk is running the console shows up with dump that contains: > {quote} > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > export DOCKER_CERT_PATH=/Users/max/code/cdk/openshift-vagrant/cdk-v2/.vagrant/machines/default/virtualbox/.docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_MACHINE_NAME=9dc5acb > # run following command to configure your shell: > # eval "$(vagrant adbinfo)" > {quote} > it is a bit confusing it pops up with no info and gets to be in front of everything. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22120) CDK plugin description is outdated

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22120?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22120: ---------------------------------- Attachment: cdk-blurb.png As you can see below, there is still one mention of Vagrant there: !cdk-blurb.png! Fixed here: https://github.com/jbosstools/jbosstools-openshift/pull/1187 But it's really a tiny thing, so it's not stopping me from closing this jira ;) > CDK plugin description is outdated > ---------------------------------- > > Key: JBIDE-22120 > URL: https://issues.jboss.org/browse/JBIDE-22120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > Attachments: cdk-blurb.png > > > JBIDE-22047 changed the cdk feature to tech preview. > While verifying that, I noticed that the cdk plugin has a very much different name and description - see that JIRA for screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22120) CDK plugin description is outdated

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22120?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22120. --------------------------------- > CDK plugin description is outdated > ---------------------------------- > > Key: JBIDE-22120 > URL: https://issues.jboss.org/browse/JBIDE-22120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > Attachments: cdk-blurb.png > > > JBIDE-22047 changed the cdk feature to tech preview. > While verifying that, I noticed that the cdk plugin has a very much different name and description - see that JIRA for screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22380?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22380: ------------------------------------------ [~mlabuda] ok, so I'll keep this opened at least for this iteration and close in the end if we still cant reproduce. > 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 > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > Attachments: project-not-preselected.png > > Original Estimate: 8 minutes > Remaining Estimate: 8 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20839) FetchSourcesFromManifests creates invalid paths when github repos defined with colons and ats

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20839?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20839. --------------------------------- No reaction from Denis, so I assume it works for him ;) Closing. > FetchSourcesFromManifests creates invalid paths when github repos defined with colons and ats > --------------------------------------------------------------------------------------------- > > Key: JBIDE-20839 > URL: https://issues.jboss.org/browse/JBIDE-20839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > As reported by Denis: > {quote}jbds sources download fails 8 out of 10 builds > {code} > [INFO] [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.23.1:fetch-sources-from-manifests (fetch-sources) on project com.jboss.devstudio.core.site: Error cloning from /home/eskimo/Projects/jbdevstudio/4.4.x/releng/jbdevstudio-product to /tmp/git@github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip: /tmp/git@github.com:dgolovin/jbdevstudio-product-2537718c95d2ab24548eadb00174cf639ec1dd99.zip (No such file or directory) > {code} > {quote} > Affected source: > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... > Solution: > ensure paths don't include colons, ats, or other special chars. (Replace with underscores?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21068) Project wizard: Set maximum length for display name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21068?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21068: ------------------------------------- Description: Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. The maximum length can be derived from the maximum lenght for OpenShift annotations. was:Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. > Project wizard: Set maximum length for display name > --------------------------------------------------- > > Key: JBIDE-21068 > URL: https://issues.jboss.org/browse/JBIDE-21068 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Dmitry Bocharov > Priority: Minor > Labels: openshift_v3, project_wizard > Fix For: 4.4.0.Alpha3 > > > Currently the 'Display Name' text field has no length limit. OpenShift on the other hand will only allow fields of length up to 65536 characters. Would be nice to let the user only input a valid length string. > The maximum length can be derived from the maximum lenght for OpenShift annotations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22439: ---------------------------------------- And by the way, I'm -1 for adding this in Jenkins. Indeed, contributors must be able to see the failure locally if they cause it, putting logic in Jenkins makes that contributors won't even be aware of the quality constraints when contributing. Also, you could consider enabling FindBugs nature in your .project and committing the .settings; so people who have FindBugs plugin installed would get the feedback from FindBugs in their IDE directly, so they can work on it as they're coding. > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha3 > > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-746) JBDS 9.0 - OpenShift Online article missing from access.redhat.com

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-746?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-746: -------------------------------------------- WIP: converting adoc file to markdown > JBDS 9.0 - OpenShift Online article missing from access.redhat.com > ------------------------------------------------------------------ > > Key: TOOLSDOC-746 > URL: https://issues.jboss.org/browse/TOOLSDOC-746 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Supriya Bharadwaj > Assignee: Misha Ali > Labels: OpenShift2 > > Convert article from asciidoc to MD and add to access.redhat.com for OS 2 > http://tools.jboss.org/documentation/howto/openshift_deployproj.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22439: ---------------------------------------- Such checkers are only useful if they'll make the build fail. If you only get reports produced by the way, and BUILD SUCCESS anyway even if code got wrong, then those side reports would be as easily forgotten as SonarQube. > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha3 > > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- Thanks a lot Martin. It seems like this instance is using the redhatdevelopers-ci GitHub account to push feedback on the build. So we'd need to make this account authorized to push on the jbosstools-* repositories. [~maxandersen] Is it OK to use this account? > 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)

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