November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23409) Server editor should allow 'edit...' option for selected username - followup

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23409?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23409: ---------------------------------- Priority: Minor (was: Major) > Server editor should allow 'edit...' option for selected username - followup > ---------------------------------------------------------------------------- > > Key: JBIDE-23409 > URL: https://issues.jboss.org/browse/JBIDE-23409 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, server > Affects Versions: 4.4.2.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.0.AM2 > > Attachments: credentials.png, runtimes.png > > > Today while creating a cdk server adapter, I noticed there is a new Edit button when selecting credentials for the adapter. This was recently added here: JBIDE-23382 > I would like to propose a change to make it consistent with other things like JREs when creating a server adapter. > So in the server editor, we used to have just Add.. and now we also have Edit...: > !credentials.png! > Similar thing in the New Server adapter. > Now look at the New Runtime dialog: > !runtimes.png! > I think it would be nice to do it similarly, wdyt? > Meaning, instead of Edit.. and Add.., we would simply have a button for "Credentials..." which would open the appropriate Preference page (and upon closing, you would need to update the content on the page to show any added credentials). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-971) [BPMN2] Update the way of KnowIssue handling

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-971?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-971: ------------------------------ Summary: [BPMN2] Update the way of KnowIssue handling (was: [BPMN2] Update the way of KnowIssue handliing) > [BPMN2] Update the way of KnowIssue handling > -------------------------------------------- > > Key: JBTIS-971 > URL: https://issues.jboss.org/browse/JBTIS-971 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > Currently are known issue handled only by wrapping caught exception with references to issues which may cause the original exception. But the tester have to check manually if the exception was really caused by the referenced issues. > It should be enhanced in such way that the thrown exception with reference to reported issue is throw if and only if it was really caused by the reported issue. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-971) [BPMN2] Update the way of KnowIssue handliing

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-971: --------------------------------- Summary: [BPMN2] Update the way of KnowIssue handliing Key: JBTIS-971 URL: https://issues.jboss.org/browse/JBTIS-971 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.4.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Currently are known issue handled only by wrapping caught exception with references to issues which may cause the original exception. But the tester have to check manually if the exception was really caused by the referenced issues. It should be enhanced in such way that the thrown exception with reference to reported issue is throw if and only if it was really caused by the reported issue. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-970) [BPMN2] Apply recent changes from master branch into jbtis-4.3.x

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-970?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-970: ------------------------------ Summary: [BPMN2] Apply recent changes from master branch into jbtis-4.3.x (was: Apply recent changes from master branch into jbtis-4.3.x) > [BPMN2] Apply recent changes from master branch into jbtis-4.3.x > ---------------------------------------------------------------- > > Key: JBTIS-970 > URL: https://issues.jboss.org/browse/JBTIS-970 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.3.3.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > For issues which should be assumed to cherry pick see the linked issues. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23330) Forge New and Noteworthy for 4.4.2.AM2

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23330?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23330. --------------------------------- PR is merged. New and Noteworthy are accessible from: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.2.AM2.html > Forge New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23330 > URL: https://issues.jboss.org/browse/JBIDE-23330 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Forge4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-970) Apply recent changes from master branch into jbtis-4.3.x

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-970?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-970: ------------------------------ Description: For issues which should be assumed to cherry pick see the linked issues. > Apply recent changes from master branch into jbtis-4.3.x > -------------------------------------------------------- > > Key: JBTIS-970 > URL: https://issues.jboss.org/browse/JBTIS-970 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.3.3.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > For issues which should be assumed to cherry pick see the linked issues. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-970) Apply recent changes from master branch into jbtis-4.3.x

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-970: --------------------------------- Summary: Apply recent changes from master branch into jbtis-4.3.x Key: JBTIS-970 URL: https://issues.jboss.org/browse/JBTIS-970 Project: JBoss Tools Integration Stack Issue Type: Bug Components: BPMN2, QE Affects Versions: 4.3.3.Final Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-956?page=com.atlassian.jira.plugin.... ] Jozef Marko resolved JBTIS-956. ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.0.Alpha2-TP) Resolution: Done > Update the pom.xml to contain only neccessary versions > ------------------------------------------------------ > > Key: JBTIS-956 > URL: https://issues.jboss.org/browse/JBTIS-956 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4147) Can't install devstudio RPM due to missing rh-nodejs 4-nodejs and rh-nodejs4-runtime

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-4147?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-4147: -------------------------------------- IMHO, you shouldn't use includepkgs= at all. The RHSCL compose repositories are more or less what an end user gets and he or she isn't going to filter the repos via includepkgs= or any other means. You unnecessarily diverge from the target environment if you do any such filtering. The only place where includepkgs= may have sense is where you expect broken or experimental stuff, like the buildroots that RHEL developers use. That might be necessary in very early stages of RHSCL development but once the night builds (http://download.eng.bos.redhat.com/nightly/updates/) or even composes (http://download.eng.bos.redhat.com/rel-eng/) are available, use them and without filtering. > Can't install devstudio RPM due to missing rh-nodejs 4-nodejs and rh-nodejs4-runtime > ------------------------------------------------------------------------------------ > > Key: JBDS-4147 > URL: https://issues.jboss.org/browse/JBDS-4147 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.2.0.AM3 > Environment: 3.10.0-327.el7.x86_64 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.2.0.AM3 > > Attachments: rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo, yum_install.log > > > Installation of Devstudio RPM fails due to unresolved dependencies. RPM unable to find rh-nodejs4-nodejs and rh-nodejs4-runtime. > I am using [yum repository|http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-R...] which I receive from [~vkadlcik] and devstudio RPM [rh-eclipse46-devstudio-10.2-0.20161028.1735.el7.x86_64.rpm|https://devstu...] > This issue may be related to [JBDS-4132|https://issues.jboss.org/browse/JBDS-4132]. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4144) DevStudio Build Results should have content.json with direct link to installer.jar

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4144?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4144. ------------------------------- Verified in latest snapshot build. > DevStudio Build Results should have content.json with direct link to installer.jar > ---------------------------------------------------------------------------------- > > Key: JBDS-4144 > URL: https://issues.jboss.org/browse/JBDS-4144 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > Current content.json has url with 'latest' segment in it, it should be direct link instead with build timestamp. That would help to avoid download problems during devsuite build if latest devstudio build replaced with new one. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 2 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 November 2016