April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22143) Changes done to OpenShift application are thrown away when debugging is enabled

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22143: ---------------------------------------- Summary: Changes done to OpenShift application are thrown away when debugging is enabled Key: JBIDE-22143 URL: https://issues.jboss.org/browse/JBIDE-22143 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Rob Stryker Priority: Critical Fix For: 4.3.1.CR1 When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different. I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-648) Improve the tracking of BPMN2 issues

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-648: -------------------------------- Assignee: Robert (Bob) Brodt > Improve the tracking of BPMN2 issues > ------------------------------------ > > Key: JBTIS-648 > URL: https://issues.jboss.org/browse/JBTIS-648 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2 > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > > Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/). > Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles. > In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla). > Other solutions could be > * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ) > * or move the whole project to the Jira JBoss Tools > What do you think? Do you have any ideas how to improve the process? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-646. ------------------------------ Fix Version/s: 9.0.0.CR1a Resolution: Done BPMN2 components removed from fuse tooling category https://github.com/jbosstools/jbosstools-integration-stack/commit/0b455da... > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.0.CR1a > > Attachments: bpmn2-1.png, jbdsis_ea_categories.png, jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-650) Check all the failing drools tests and mark all known issues

by Tomas David (JIRA)

Tomas David created JBTIS-650: --------------------------------- Summary: Check all the failing drools tests and mark all known issues Key: JBTIS-650 URL: https://issues.jboss.org/browse/JBTIS-650 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: drools/ jBPM, QE Reporter: Tomas David Assignee: Tomas David -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-646: ------------------------------------ Attachment: jbdsis_ea_categories.png > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: bpmn2-1.png, jbdsis_ea_categories.png, jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-646: ----------------------------------------- I think it is ok now, thx Paul! > Do not include BPMN2 features in the JBoss Fuse category > -------------------------------------------------------- > > Key: JBTIS-646 > URL: https://issues.jboss.org/browse/JBTIS-646 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Environment: JBDS-IS 9.0.0.CR1a > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: bpmn2-1.png, jbdsis_fuse_category.png > > > The category JBoss Fuse Development should contain only the following features > - Fuse tooling > - SwitchYard tooling (+ BPEL/BPMN2 support) > All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-649) Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-649: --------------------------------------- Summary: Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final Key: JBTIS-649 URL: https://issues.jboss.org/browse/JBTIS-649 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 9.0.0.CR1 Reporter: Andrej Podhradsky Priority: Minor Currently, JBDS-IS 9.0.0.CR1 (and also the snapshot of CR1a) contains org.jboss.tools.foundation.security.linux 1.2.1.Beta2-v20160127-2129-B77 but the JBDS 9.1.0.CR1a contains org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160401-0436-B108 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Xia Zhao commented on JBIDE-22133: ---------------------------------- I was trying to get the trace logs from JBDS, need some more time to address... > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Assignee: Jeff Cantrill > Labels: openshift_v3 > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22139?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22139: ------------------------------------- Labels: test (was: ) > 20% of openshift tests are not run > ---------------------------------- > > Key: JBIDE-22139 > URL: https://issues.jboss.org/browse/JBIDE-22139 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: test > Fix For: 4.4.0.Alpha1 > > > I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run. > This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite. > As a developer I just write my test class and expect the build to pick it up automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22142) Watches should not try to reconnect when a project has been deleted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22142?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22142: ---------------------------------- Summary: Watches should not try to reconnect when a project has been deleted (was: Watchers should not try to reconnect when a project has been deleted) > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22142 > URL: https://issues.jboss.org/browse/JBIDE-22142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- 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 April 2016