November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4148) Run as -> Run on server -> browser might open too early causing http 404

by Josef Ludvicek (JIRA)

Josef Ludvicek created JBDS-4148: ------------------------------------ Summary: Run as -> Run on server -> browser might open too early causing http 404 Key: JBDS-4148 URL: https://issues.jboss.org/browse/JBDS-4148 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Affects Versions: 9.1.0.GA Reporter: Josef Ludvicek -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23399) clean up email generation to avoid invalid addresses

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23399?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23399. -------------------------------- I am not able to verify this ticket I think, so closing without verification. The script will be verified next time we use notification emails. > clean up email generation to avoid invalid addresses > ---------------------------------------------------- > > Key: JBIDE-23399 > URL: https://issues.jboss.org/browse/JBIDE-23399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Last batch of notification emails re: JBT 4.4.2.AM2 release (and the previous ones for staging too) all had these recipients: > {code} > -nboldt(a)redhat.com, > Boldt(a)redhat.com, > -fNick(a)redhat.com, > --(a)redhat.com, > -c(a)redhat.com{code} > Seems like a problem with quotes / commandline. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23364) Two different versions of code recommenders and docker tooling in JBT composite site

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23364?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23364. -------------------------------- Verified in 10.2.0.AM3, Abridged JBoss Tools can be installed without problems. > Two different versions of code recommenders and docker tooling in JBT composite site > ------------------------------------------------------------------------------------ > > Key: JBIDE-23364 > URL: https://issues.jboss.org/browse/JBIDE-23364 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > Attachments: docker_versions.png, snipmatch_versions.png > > > This remediation error occurs when trying to install JBT 4.4.2.AM2 into Eclipse JEE bundle Neon.1a: > {code} > Your original request has been modified. > "JavaScript Development Tools" will be ignored because a newer version is already installed. > "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed. > "WST JSON Core" will be ignored because a newer version is already installed. > Cannot complete the install because of a conflicting dependency. > Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) > Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645) > Only one of the following can be installed at once: > Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609) > Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645) > Cannot satisfy dependency: > From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645) > To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645] > Cannot satisfy dependency: > From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609) > To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1) > Cannot satisfy dependency: > From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) > To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 6 months

1
0
0 / 0

[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 commented on JBIDE-23409: --------------------------------------- I wasn't suggesting to change which servers/runtimes store credentials using credentials API and which don't. I merely suggest to change the UI where it's already present. But I'm not insisting on this. I just thought it would be a nice enhancement. It's not really a very hight priority. > 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 > 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)

7 years, 6 months

1
0
0 / 0

[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 edited comment on JBIDE-23409 at 11/1/16 5:11 AM: ---------------------------------------------------------------- I wasn't suggesting to change which servers/runtimes store credentials using credentials API and which don't. I merely suggest to change the UI where it's already present. But I'm not insisting on this. I just thought it would be a nice enhancement. It's not really a very high priority. was (Author: mmalina): I wasn't suggesting to change which servers/runtimes store credentials using credentials API and which don't. I merely suggest to change the UI where it's already present. But I'm not insisting on this. I just thought it would be a nice enhancement. It's not really a very hight priority. > 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 > 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)

7 years, 6 months

1
0
0 / 0

[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)

7 years, 6 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)

7 years, 6 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)

7 years, 6 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)

7 years, 6 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)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2016