October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25221) [jbosstools-openshift] Block PRs for merge untill review (approved by other team members)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25221?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25221. -------------------------------- Resolution: Done As this change done for openshift only, I've changed the Components to reflect that. Resolving as dupe of JBIDE-24671. > [jbosstools-openshift] Block PRs for merge untill review (approved by other team members) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-25221 > URL: https://issues.jboss.org/browse/JBIDE-25221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Jeff MAURY > Fix For: 4.5.1.Final > > Attachments: protected_branch_only_for_review.png > > > There is a possibility in github to "protect" branch from merge based on the approval status, not on the Jenkins status as it is described in JBIDE-24439. See the attached image for details. > [~adietish] and [~jeffmaury] agreed with this idea in the mattermost. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25221) Block PRs for merge untill review (approved by other team members)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25221?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25221: ------------------------------- Component/s: (was: build) (was: server) > Block PRs for merge untill review (approved by other team members) > ------------------------------------------------------------------ > > Key: JBIDE-25221 > URL: https://issues.jboss.org/browse/JBIDE-25221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Jeff MAURY > Fix For: 4.5.1.Final > > Attachments: protected_branch_only_for_review.png > > > There is a possibility in github to "protect" branch from merge based on the approval status, not on the Jenkins status as it is described in JBIDE-24439. See the attached image for details. > [~adietish] and [~jeffmaury] agreed with this idea in the mattermost. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25221) Block PRs for merge untill review (approved by other team members)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25221?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25221: ------------------------------- Fix Version/s: 4.5.1.Final > Block PRs for merge untill review (approved by other team members) > ------------------------------------------------------------------ > > Key: JBIDE-25221 > URL: https://issues.jboss.org/browse/JBIDE-25221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, server > Reporter: Dmitrii Bocharov > Assignee: Jeff MAURY > Fix For: 4.5.1.Final > > Attachments: protected_branch_only_for_review.png > > > There is a possibility in github to "protect" branch from merge based on the approval status, not on the Jenkins status as it is described in JBIDE-24439. See the attached image for details. > [~adietish] and [~jeffmaury] agreed with this idea in the mattermost. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25228: ------------------------------- Fix Version/s: 4.5.1.Final > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25228: ---------------------------------- Summary: target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions Key: JBIDE-25228 URL: https://issues.jboss.org/browse/JBIDE-25228 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.5.1.Final Reporter: Nick Boldt Priority: Blocker With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25228: ---------------------------------- Assignee: Nick Boldt > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.Final > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1172) Move Teiid Designer to EA until it goes .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1172?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1172: ----------------------------------- [~nickboldt] [~apodhrad] Hey Nick - Andrej asked the following question: _ today I realized that I'm not sure about how will be TD available. I know it will be on EA but it will be on staging EA, right? So, my question is, will it be available from Devstudio? I mean the following use case 1. Install Devstudio (without any other configurations such as adding anything to devstudio.ini) 2. Open Red Hat Central 3. Check Early Access 4. WIll we see the Teiid Designer here?_ The plan is for me to release this to 'staging' only after QE review (Oct 26) - and then promote to 'development' on Nov 7. Is there a 4.5.oxygen section planned for ide-config.properties for staging elements where I should modify jboss.discovery.earlyaccess.site.integration-stack.url ? > Move Teiid Designer to EA until it goes .Final > ---------------------------------------------- > > Key: JBTIS-1172 > URL: https://issues.jboss.org/browse/JBTIS-1172 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.5.1.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.5.1.Beta1 > > > Need to make Teiid Designer an early access component for the Beta release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1173) Missing TP for 11.1.0.Beta1 Early Access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1173?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1173: ----------------------------------- [~apodhrad] - correct - a seperate TP wasn't needed for early access. > Missing TP for 11.1.0.Beta1 Early Access > ---------------------------------------- > > Key: JBTIS-1173 > URL: https://issues.jboss.org/browse/JBTIS-1173 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 11.1.0.CR1 > Reporter: Andrej Podhradsky > Priority: Critical > > I noticed that there is no TP for 11.1.0.Beta1 Early Access even though the Teiid Designer is released on Early Access. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25172) CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25172?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25172: ---------------------------------- Steps to Reproduce: 1. EXEC: Have cdk 3.2 downloaded 2. ASSERT: there is no old cdk configuration (check ~/.minishift and ~/.kube do not exist) 3. EXEC: run 'setup-cdk --profile test' 4. EXEC: Add new CDK 3.2+ server adapter with profile 'test' 5. EXEC: Start CDK 3.2+ server adapter 6. ASSERT: Proper OS 3 connection (developer) with project is created Result: Openshift explorer contains openshift-dev connection without project created was: 1. EXEC: Have cdk 3.2 downloaded 2. ASSERT: there is no old cdk configuration (check ~/.minishift and ~/.kube do not exist) 2. EXEC: run 'setup-cdk --profile test' 3. EXEC: Add new CDK 3.2+ server adapter with profile 'test' 4. EXEC: Start CDK 3.2+ server adapter 5. ASSERT: Proper OS 3 connection (developer) with project is created > CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection > ----------------------------------------------------------------------------------- > > Key: JBIDE-25172 > URL: https://issues.jboss.org/browse/JBIDE-25172 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > Attachments: CDK3_2WrongOS3.png > > > CDK 3.2+ server adapter is started sucessfully, one can log in to openshift via browser, but in IDE, OS 3 connection got wrong name (openshift-dev) and no project is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25172) CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25172?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25172: ---------------------------------- Steps to Reproduce: 1. EXEC: Have cdk 3.2 downloaded 2. ASSERT: there is no old cdk configuration (check ~/.minishift and ~/.kube do not exist) 2. EXEC: run 'setup-cdk --profile test' 3. EXEC: Add new CDK 3.2+ server adapter with profile 'test' 4. EXEC: Start CDK 3.2+ server adapter 5. ASSERT: Proper OS 3 connection (developer) with project is created was: 1. EXEC: Have cdk 3.2 downloaded 2. EXEC: run 'setup-cdk --profile test' 3. EXEC: Add new CDK 3.2+ server adapter with profile 'test' 4. EXEC: Start CDK 3.2+ server adapter 5. ASSERT: Proper OS 3 connection (developer) with project is created > CDK 3.2+ adapter started successfully but there is no project under OS 3 Connection > ----------------------------------------------------------------------------------- > > Key: JBIDE-25172 > URL: https://issues.jboss.org/browse/JBIDE-25172 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > Attachments: CDK3_2WrongOS3.png > > > CDK 3.2+ server adapter is started sucessfully, one can log in to openshift via browser, but in IDE, OS 3 connection got wrong name (openshift-dev) and no project is attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017