May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ] Josef Kopriva updated JBDS-4703: -------------------------------- Steps to Reproduce: 1. Import project in eclipse (e.g. org.jboss.tools.openshift.ui.bot.test) (install necessary plugins: tycho(dialog for install should open after import) and RedDeer) 2. Run test suite 3. Wait until test run finishes or kill run 4. Edit suite class (comment or delete some tests classes) FAIL: Same tests classes in suite are run(even with commented tests) EXPECTED: Only uncommented tests or not deleted tests classes are run was: 1. Import project in eclipse (e.g. openshift itests) (install necessary plugins, e.g. tycho...) 2. Run test suite suite 3. Wait until test run finishes or kill run 4. Edit suite class (comment or delete some tests classes) FAIL: Same tests classes in suite are run(even with commented tests) EXPECTED: Only uncommented tests or not deleted tests classes are run > Auto build is not working for maven project > ------------------------------------------- > > Key: JBDS-4703 > URL: https://issues.jboss.org/browse/JBDS-4703 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: maven > Affects Versions: 12.0.0.AM1 > Environment: F27, F28, Win10 > Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180508-1631-B2428 > Build date: 20180508-1631 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Fix For: 12.0.0.AM3 > > Attachments: test.zip > > > Auto build is not working. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26015?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26015: ------------------------------- Sprint: (was: devex #149 May 2018) > write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI > ------------------------------------------------------------------------ > > Key: JBIDE-26015 > URL: https://issues.jboss.org/browse/JBIDE-26015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM2 > > > Need new doc(s) in https://github.com/jbosstools/jbosstools-devdoc/ > * get and build maven tool from https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > * configure keystore per https://github.com/nickboldt/maven-plugins/blob/master/hudson-job-sync-pl... > * jenkins crumbs - https://stackoverflow.com/questions/16738441/how-to-request-for-crumb-iss... > * set up bash & pom-sync.xml scripts (with examples) > * pull jobs (one by one or batch modes) > * edit jobs / save changes to github repo > * push jobs back to server (one by one or batch push mode) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Sprint: devex #148 April 2018 (was: devex #148 April 2018, devex #149 May 2018) > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM3, 4.6.0.Final > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26015?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26015: ------------------------------- Sprint: devex #149 May 2018 > write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI > ------------------------------------------------------------------------ > > Key: JBIDE-26015 > URL: https://issues.jboss.org/browse/JBIDE-26015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM2 > > > Need new doc(s) in https://github.com/jbosstools/jbosstools-devdoc/ > * get and build maven tool from https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-sync-pl... > * configure keystore per https://github.com/nickboldt/maven-plugins/blob/master/hudson-job-sync-pl... > * jenkins crumbs - https://stackoverflow.com/questions/16738441/how-to-request-for-crumb-iss... > * set up bash & pom-sync.xml scripts (with examples) > * pull jobs (one by one or batch modes) > * edit jobs / save changes to github repo > * push jobs back to server (one by one or batch push mode) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ] Mickael Istria resolved ERT-623. -------------------------------- Resolution: Done Done. See link for demo http://www.screencast.com/t/vksX3uZm1aj As for the immediate effect, working on this demo has generated: * new feature and improved UX in DockerTools (Thanks a lot to Jeff and Roland for their assistance in fixing Docker Tools to make this demo work) * bug reports and some fixes in LSP4E * bug reports to LSP4J: https://github.com/eclipse/lsp4j/issues/192 * Discussion with LSPHub: https://dev.eclipse.org/mhonarc/lists/lsphub-dev/ * relevant enhancement request to LSP spec: https://github.com/Microsoft/language-server-protocol/issues/483 About restrictions: * It should be noted that relying on Docker on a workstation is a bad idea. It take a lot of hard drive, it's slower, than a regular process. Moreover, I bet most users of Eclipse IDE actually don't have docker daemon started to have this approach viable for this majority of users. * Just a LS in Eclipse IDE seem too little. User will also want syntax highlighting as much as LS, so the flow of dynamically adding support of languages in Eclipse IDE needs to also take TextMate into account (but it's already partially covered in tm4e). * Again, we're all talking about edition, which is just the 2nd step of the typical 4 steps process (provision/import, edit, run, deploy). If we want to keep digging on this topic: * Next would be the discovery of Language Server and TextMate grammars. I already have an issue and some proposals described to dynamically discover and install TextMate grammar from GitHub; and I think a similar thing could be done with Language Servers as docker image from DockerHub. I think the proposal of LSPHub is overkill and that if we want Docker containers for LS, it's never going to be as successful as DockerHub can be. But DockerHub search engine sucks too much to be usable so far (seems to miss a perfect match research to look for specific tags). * Make LS Docker Image assume that entry point starts the LS without any option. So each client can add the option they want without tweaking the entry point. If we can standardize options as proposed in https://github.com/Microsoft/language-server-protocol/issues/483 , then it becomes quite easy to automate configuration with almost no extra-metadata. > Evaluate combination of Docker images of LS (from Che?) with LSP4E > ------------------------------------------------------------------ > > Key: ERT-623 > URL: https://issues.jboss.org/browse/ERT-623 > Project: Eclipse Release Train > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > > LSP4E offers a way to dynamically associate a Launch configuration representing a language server (communicating over stdio) with a content type to enable LS-based edition assistance in editor. > It would be interesting to try this using a Docker Launch Configuration with LSP4E, more particularly, it'd be nice to test the Docker LS images that are created for Eclipse Che. > cc [~rgrunber] : any obvious concern about it? > cc [~flbe] : are the image for Language Server in Che streaming the LS messages over stdio? Or is it using another channel? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ] Mickael Istria updated ERT-623: ------------------------------- Sprint: devex #149 May 2018 > Evaluate combination of Docker images of LS (from Che?) with LSP4E > ------------------------------------------------------------------ > > Key: ERT-623 > URL: https://issues.jboss.org/browse/ERT-623 > Project: Eclipse Release Train > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > > LSP4E offers a way to dynamically associate a Launch configuration representing a language server (communicating over stdio) with a content type to enable LS-based edition assistance in editor. > It would be interesting to try this using a Docker Launch Configuration with LSP4E, more particularly, it'd be nice to test the Docker LS images that are created for Eclipse Che. > cc [~rgrunber] : any obvious concern about it? > cc [~flbe] : are the image for Language Server in Che streaming the LS messages over stdio? Or is it using another channel? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ] Mickael Istria reassigned ERT-623: ---------------------------------- Assignee: Mickael Istria > Evaluate combination of Docker images of LS (from Che?) with LSP4E > ------------------------------------------------------------------ > > Key: ERT-623 > URL: https://issues.jboss.org/browse/ERT-623 > Project: Eclipse Release Train > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > > LSP4E offers a way to dynamically associate a Launch configuration representing a language server (communicating over stdio) with a content type to enable LS-based edition assistance in editor. > It would be interesting to try this using a Docker Launch Configuration with LSP4E, more particularly, it'd be nice to test the Docker LS images that are created for Eclipse Che. > cc [~rgrunber] : any obvious concern about it? > cc [~flbe] : are the image for Language Server in Che streaming the LS messages over stdio? Or is it using another channel? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1224) invalid composite child site in http://download.jboss.org/jbosstools/oxygen/stable/updates/integration-stack/discovery

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1224?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1224. ------------------------------- Resolution: Done Corrected in the stable discovery composites - added one more level of indirection. I'll bade the photon ones off of the oxy ones - should be ok going forward. > invalid composite child site in http://download.jboss.org/jbosstools/oxygen/stable/updates/integration-st... > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-1224 > URL: https://issues.jboss.org/browse/JBTIS-1224 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.5.3.Final > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.5.3.Final > > > The link to *../../../../targetplatforms/jbtistarget/4.5.3.Final/jbtis/REPO/* is invalid in http://download.jboss.org/jbosstools/oxygen/stable/updates/integration-st... > You can verify composite sites are valid using this job [1] - see the section where a 404 is logged for this line: > {code}http://download.jboss.org/jbosstools/oxygen/stable/updates/integration-stack/discovery//../../../../targetplatforms/jbtistarget/4.5.3.Final/jbtis/REPO/ : NO {code} > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Please fix the link. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4708) Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4708?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4708: ---------------------------------- Similar issue installing everything in RH Central - can't install m2e.egit feature. !remediation-jbt-central.png|thumbnail! > Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently > --------------------------------------------------------------------------- > > Key: JBDS-4708 > URL: https://issues.jboss.org/browse/JBDS-4708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.AM3 > > Attachments: remediation-1.png, remediation-2.png, remediation-jbt-central.png > > > Problem appears to be a hard upper limit from org.sonatype.m2e.egit 0.15.0.20161027 on egit.core [3.0.0,5.0.0). > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > Software currently installed: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > Only one of the following can be installed at once: > Git integration for Eclipse - Core 4.11.0.201803080745-r (org.eclipse.egit.core 4.11.0.201803080745-r) > Git integration for Eclipse - Core 5.0.0.201805151920-m7 (org.eclipse.egit.core 5.0.0.201805151920-m7) > Git integration for Eclipse - Core 4.10.0.201712302008-r (org.eclipse.egit.core 4.10.0.201712302008-r) > Git integration for Eclipse - Core 5.0.0.201805221745-rc1 (org.eclipse.egit.core 5.0.0.201805221745-rc1) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > To: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpmdeps.feature.feature.group [12.0.0.v20180418-2342,12.0.0.v20180418-2342] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 12.0.0.v20180418-2342 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 12.0.0.v20180418-2342) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [5.0.0.201805151920-m7,5.0.0.201805151920-m7] > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit 0.15.0.201610271523) > To: osgi.bundle; org.eclipse.egit.core [3.0.0,5.0.0) > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit.feature.feature.group 0.15.0.201610271523) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit [0.15.0.201610271523,0.15.0.201610271523]{code} > As such we can either: > * install devstudio (which requires m2e.egit) and uninstall egit and egit.mylyn features to do so, or > !remediation-2.png|thumbnail! > * upgrade to egit 5.0.0.20180522 (rc1) and not be able to install devstudio 12.0.0.AM2. > !remediation-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4708) Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4708?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4708: ----------------------------- Attachment: remediation-jbt-central.png > Remediation prevents installation of devstudio 12 AND egit 5.0 concurrently > --------------------------------------------------------------------------- > > Key: JBDS-4708 > URL: https://issues.jboss.org/browse/JBDS-4708 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 12.0.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 12.0.0.AM3 > > Attachments: remediation-1.png, remediation-2.png, remediation-jbt-central.png > > > Problem appears to be a hard upper limit from org.sonatype.m2e.egit 0.15.0.20161027 on egit.core [3.0.0,5.0.0). > {code} > Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > Software currently installed: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > Only one of the following can be installed at once: > Git integration for Eclipse - Core 4.11.0.201803080745-r (org.eclipse.egit.core 4.11.0.201803080745-r) > Git integration for Eclipse - Core 5.0.0.201805151920-m7 (org.eclipse.egit.core 5.0.0.201805151920-m7) > Git integration for Eclipse - Core 4.10.0.201712302008-r (org.eclipse.egit.core 4.10.0.201712302008-r) > Git integration for Eclipse - Core 5.0.0.201805221745-rc1 (org.eclipse.egit.core 5.0.0.201805221745-rc1) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 12.0.0.v20180525-1013 (com.jboss.devstudio.core.feature.feature.group 12.0.0.v20180525-1013) > To: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpmdeps.feature.feature.group [12.0.0.v20180418-2342,12.0.0.v20180418-2342] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Feature Dependencies) 12.0.0.v20180418-2342 (com.jboss.devstudio.core.rpmdeps.feature.feature.group 12.0.0.v20180418-2342) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit.feature.feature.group 0.0.0 > Cannot satisfy dependency: > From: Git integration for Eclipse 5.0.0.201805151920-m7 (org.eclipse.egit.feature.group 5.0.0.201805151920-m7) > To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [5.0.0.201805151920-m7,5.0.0.201805151920-m7] > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit 0.15.0.201610271523) > To: osgi.bundle; org.eclipse.egit.core [3.0.0,5.0.0) > Cannot satisfy dependency: > From: Maven SCM Handler for EGit 0.15.0.201610271523 (org.sonatype.m2e.egit.feature.feature.group 0.15.0.201610271523) > To: org.eclipse.equinox.p2.iu; org.sonatype.m2e.egit [0.15.0.201610271523,0.15.0.201610271523]{code} > As such we can either: > * install devstudio (which requires m2e.egit) and uninstall egit and egit.mylyn features to do so, or > !remediation-2.png|thumbnail! > * upgrade to egit 5.0.0.20180522 (rc1) and not be able to install devstudio 12.0.0.AM2. > !remediation-1.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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