June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21615) Cannot save changes for launch configuration in CDK Adapter Configuration Editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21615?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21615: -------------------------------- Sprint: (was: devex #115 May 2016) > Cannot save changes for launch configuration in CDK Adapter Configuration Editor > -------------------------------------------------------------------------------- > > Key: JBIDE-21615 > URL: https://issues.jboss.org/browse/JBIDE-21615 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, server > Affects Versions: 4.4.0.Alpha1 > Environment: Windows 10 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > Attachments: CDK launch config changes are not saved.mp4 > > > Launch configuration changes discarded in CDK Server Configuration Editor see attached video -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- [~maxandersen]: I just tried submitted this PR https://github.com/jbosstools/jbosstools-target-platforms/pull/219. jboss-jenkins from the big Jenkins instances manages to comment it., however rhdevelopers-ci on the Central CI fails with {code} FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo. java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"} {code} See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... for more details. Using a token of mine with only repo_status on Central CI works. [~ppitonak] told that the token on Central CI for rhdevelopers-ci should have a good token and reported this configuration still manages to comment PR for some other GitHub repositories. Is there anything different on the way jboss-jenkins and rhdevelopers-ci accounts are configured in the jbosstools-target-platforms repository? > 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.Final > > > 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-22411) update TPs to latest Docker/Vagrant tooling

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22411. --------------------------------- Docker tooling are updated to RC3 - 2.0.0.201606010301. Verified in: Version: 10.0.0.GA Build id: GA-v20160602-0541-B5497 Build date: 20160602-0541 > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22499?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22499: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > Read CDK's Docker Registry url from service manager plugin > ---------------------------------------------------------- > > Key: JBIDE-22499 > URL: https://issues.jboss.org/browse/JBIDE-22499 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.x > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22441) Hard-code default Docker Registry url when CDK starts

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22441?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22441: -------------------------------- Summary: Hard-code default Docker Registry url when CDK starts (was: Read and store CDK's Docker Registry url from service manager plugin) > Hard-code default Docker Registry url when CDK starts > ----------------------------------------------------- > > Key: JBIDE-22441 > URL: https://issues.jboss.org/browse/JBIDE-22441 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-22499: ----------------------------------- Summary: Read CDK's Docker Registry url from service manager plugin Key: JBIDE-22499 URL: https://issues.jboss.org/browse/JBIDE-22499 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk Affects Versions: 4.4.0.Final Reporter: Fred Bricon Assignee: Rob Stryker Priority: Blocker Fix For: 4.4.0.Final we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-727) Extend Server requirement for Runtime Execution

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-727?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík commented on JBTIS-727: ------------------------------------ Test this with Fuse Tooling tests: * DataTransformationDeploymentEAPTest * DeploymentEAPTest > Extend Server requirement for Runtime Execution > ----------------------------------------------- > > Key: JBTIS-727 > URL: https://issues.jboss.org/browse/JBTIS-727 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > for more info see https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/734... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-719) Fix 'DeploymentEAPTest'

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-719: ------------------------------- Summary: Fix 'DeploymentEAPTest' (was: Fix 'DataTransformationDeploymentEAPTest') > Fix 'DeploymentEAPTest' > ----------------------- > > Key: JBTIS-719 > URL: https://issues.jboss.org/browse/JBTIS-719 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Environment: Fuse on EAP 6.3.0.ER1 > JBDS 9.1.0.GA > JBDSIS 9.0.0.GA > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > > Fuse on EAP log was slightly changed. > {code} > ...file://src/data) Creating JAXBContext... > {code} > to > {code} > ...file://src/data) Created XMLInputFactory... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22440) update to latest m2e-mavenarchiver

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22440?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22440. --------------------------------- New m2e-mavenarchiver is present in 10.0.0.GA. Verified in: Version: 10.0.0.GA Build id: GA-v20160602-0541-B5497 Build date: 20160602-0541 > update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-22440 > URL: https://issues.jboss.org/browse/JBIDE-22440 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > new m2e-mavenarchiver version is coming (issue was discovered friday with maven-jar-plugin 3.0.0) https://github.com/tesla/m2eclipse-mavenarchiver/issues/8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22434) Properties not showing whole Docker image ID

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22434?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22434. --------------------------------- Image ID is complete now. Closing issue. Verified in: Version: 10.0.0.GA Build id: GA-v20160602-0541-B5497 Build date: 20160602-0541 > Properties not showing whole Docker image ID > -------------------------------------------- > > Key: JBIDE-22434 > URL: https://issues.jboss.org/browse/JBIDE-22434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.0.Alpha2 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160525-0422-B5425 > Build date: 20160525-0422 > Reporter: Josef Kopriva > Assignee: Jeff Johnston > Fix For: 4.4.0.Final > > Attachments: Dockerfile, Docker_Image_ID.png > > > Image ID in properties tab is not complete, but Parent ID is complete. -- 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 June 2016