September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-919) Update bpmn2 meta-data model for neon

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-919: -------------------------------- Summary: Update bpmn2 meta-data model for neon Key: JBTIS-919 URL: https://issues.jboss.org/browse/JBTIS-919 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: BPMN2 Affects Versions: 10.0.0.Alpha1 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 10.0.0.GA ref: https://issues.jboss.org/browse/JBTIS-912 Update BPMN2 meta-data model to 1.3.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4054: ---------------------------------- I've added a README.html to the yum_repo folder. https://github.com/jbdevstudio/jbdevstudio-product/commit/36b51c99b4d6557... Should be available in about 20 mins when the next master build is done: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/1... https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/la... https://devstudio.jboss.com/10.0/snapshots/rpms/10.2.0/x86_64/ > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... > * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-912) Some BPMN2 bundles have incorrect versions

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-912?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt resolved JBTIS-912. -------------------------------------- Resolution: Done Done. Here's the new updatesite: http://download.eclipse.org/modeling/mdt/bpmn2/updates/neon/1.3.1 > Some BPMN2 bundles have incorrect versions > ------------------------------------------ > > Key: JBTIS-912 > URL: https://issues.jboss.org/browse/JBTIS-912 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2 > Affects Versions: 10.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > > Some BPMN2 bundles have incorrect versions (missing build number) > {code} > org.eclipse.bpmn2_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.edit_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.editor_1.3.0.Final-v20160119-1832 > org.eclipse.bpmn2.modeler.core_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.help_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm_1.3.1.Final-v20160831-1132-B55 > org.eclipse.bpmn2.modeler.ui_1.3.1.Final-v20160831-1132-B55 > {code} > Notice that the last 4 bundles have correct version with a build number. But the first 3 of them are missing the build number. > EDIT: Note that all BPMN2 bundles in JBDS-IS 9.0.2.CR1 have correct versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23062) Update arquillian bot tests to run on Central CI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23062?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-23062. ---------------------------------- Resolution: Done Changes committed to master:: https://github.com/jbosstools/jbosstools-integration-tests/pull/1614 > Update arquillian bot tests to run on Central CI > ------------------------------------------------ > > Key: JBIDE-23062 > URL: https://issues.jboss.org/browse/JBIDE-23062 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.AM3 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23277) Update arquillian bot integration tests - to resolve intermittent timing issue

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23277?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-23277: --------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1622) > Update arquillian bot integration tests - to resolve intermittent timing issue > ------------------------------------------------------------------------------ > > Key: JBIDE-23277 > URL: https://issues.jboss.org/browse/JBIDE-23277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Minor > > Recent updates to tests have exposed another timing issue that had been masked - need to increase the timeout for Central to load as this is causing intermittent timeouts and test failures: > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: Waiting for Central to load > at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183) > at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56) > at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:44) > at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:35) > at org.jboss.tools.arquillian.ui.bot.test.cruiserView.BasicArquilliaCruiserTest.setup(BasicArquilliaCruiserTest.java:48) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22803: ------------------------------------------ [~jcantrill] [~adietish] [~jeffmaury] tried to find out how to get the version of the OpenShift Origin Server, but found nothing implemented yes and it seems not-so-easy-to-solve problem. I tried watching projects with [the latest v1.3.0|https://github.com/openshift/origin/releases/tag/v1.3.0] and it works! That's great! I also tried with https://console.engint.openshift.com and the version of OS installed there doesn't support this feature (in spite of OpenShift Master: v3.2.1.15-8-gc402626). I tried to debug and what i notices is that org.jboss.tools.openshift.internal.core.WatchManager.WatchListener error method is called without stopping (because it tries to restart(); all the time). And i have an idea how solve the question of whether the feature is available or not. If we look at response variable of com.openshift.internal.restclient.okhttp.WatchClient.WatchEndpoint.onFailure(IOException, Response) then we'll see the following: Response{protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} I understand that it's a dirty hack, but we can retrieve this url (by response.request().url()) and analyze the code. And, for example, if this response repeats, say, 3 times, then we understand that the feature is not available. I see how cheaty it is, but it should work > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen issues. > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4059 at 9/30/16 11:13 AM: ------------------------------------------------------------ Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen JBIDE and JBDS issues. was (Author: nickboldt): Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen issues. > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22966: ------------------------------------ Currently there are 7 RHT BZ, but they're all resolved. So still no immediate urgency here. > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM2 > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ Jobs updated, ready for the next time we need them: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 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 September 2016