April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22255: ------------------------------------- Seems like eventually, OpenShift delegates to https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or..., that that should be a Server issue. cc [~rob.stryker]. > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22260: -------------------------------- Description: When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: 1- click the manage project link 2- click the New button in the manage projects wizards to open the New project wizard 3- fill in the project name 4- click ok to close the new project wizard 5- click ok to close the manage projects wizards => project list is reloaded This could really be more streamlined to 1- click the New button in the root wizard to open the New project wizard 2- fill in the project name 3- click ok to close the new project wizard was: When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: 1- click the manage project link 2- click the New button in the manage projects wizards to open the New project wizard 3- fill in the project name 4- click ok to close the new project wizard 5- click ok to close the manage projects wizards => project list is reloaded This could really be more streamlined to 1- click the New button in the manage projects wizards to open the New project wizard 2- fill in the project name 3- click ok to close the new project wizard > Change 'Manage projects...' links to "New Project" buttons > ---------------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22260: ----------------------------------- Summary: Change 'Manage projects...' links to "New Project" buttons Key: JBIDE-22260 URL: https://issues.jboss.org/browse/JBIDE-22260 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Final Reporter: Fred Bricon When creating a new application or deploying a new docker image, if the user want to create a new project, he has to: 1- click the manage project link 2- click the New button in the manage projects wizards to open the New project wizard 3- fill in the project name 4- click ok to close the new project wizard 5- click ok to close the manage projects wizards => project list is reloaded This could really be more streamlined to 1- click the New button in the manage projects wizards to open the New project wizard 2- fill in the project name 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22260: -------------------------------- Fix Version/s: 4.4.x > Change 'Manage projects...' links to "New Project" buttons > ---------------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user want to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the manage projects wizards to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22260: -------------------------------- Description: When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: 1- click the manage project link 2- click the New button in the manage projects wizards to open the New project wizard 3- fill in the project name 4- click ok to close the new project wizard 5- click ok to close the manage projects wizards => project list is reloaded This could really be more streamlined to 1- click the New button in the manage projects wizards to open the New project wizard 2- fill in the project name 3- click ok to close the new project wizard was: When creating a new application or deploying a new docker image, if the user want to create a new project, he has to: 1- click the manage project link 2- click the New button in the manage projects wizards to open the New project wizard 3- fill in the project name 4- click ok to close the new project wizard 5- click ok to close the manage projects wizards => project list is reloaded This could really be more streamlined to 1- click the New button in the manage projects wizards to open the New project wizard 2- fill in the project name 3- click ok to close the new project wizard > Change 'Manage projects...' links to "New Project" buttons > ---------------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the manage projects wizards to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22244) BZ-JIRA job configuration does not take timezones into account

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22244?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22244. ------------------------------ Fix Version/s: 4.4.0.Alpha1 Assignee: Nick Boldt (was: Max Rydahl Andersen) Resolution: Won't Fix Closing as workaround works for now. If we start running this in other timezones, we could reopen this. > BZ-JIRA job configuration does not take timezones into account > -------------------------------------------------------------- > > Key: JBIDE-22244 > URL: https://issues.jboss.org/browse/JBIDE-22244 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Final > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > it seems like the default {{HOURS}} value ('2') for the job that copies bugzilla issues into JIRA (in the ERT project) is not enough to catch the changes. This might be due to the timezones, since the script run by the job and the job itself do not use the same timezone. > for example: > - I created an issue in BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=492420 on 2016-04-26 03:07:04 EDT > - I then manually kicked the job with the {{HOURS}} value set to {{2}} (Build #2073 - Apr 26, 2016 3:19:03 AM). (I assume the TZ is EDT here, too.) > - The script output contains the following lines: > {{code}} > 03:19:10 [DEBUG] Current datetime: 2016-04-26 07:19:09.521272 (UTC) > 03:19:10 [DEBUG] xmlrpc post: {'status_whiteboard': 'RHT', 'last_change_time': '2016-04-26 04:19'} > 03:19:10 [DEBUG] buglist get: https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT&chfieldfr... > 03:19:10 [DEBUG] Found 0 bugzillas to process > {{code}} > In the mean time, setting the {{HOURS}} value to '6', I was able to get the issue created in JIRA. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22244) BZ-JIRA job configuration does not take timezones into account

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22244?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22244: ------------------------------------ Suspect the reason I don't see this is that I live in the same timezone as the Eclipse Bugzilla server. :D So, I've bumped the value of HOURS = 6 to HOURS = 8, which should give 5 or 6 timezones (daylight savings) of offeset from UTC + 2 hrs of overlap to ensure we grab everything. Also kicked the job again to refresh the last 250 hours, just in case anything was missed. I could spend time making the script run in UTC instead of local TZ, but we have more pressing matters. > BZ-JIRA job configuration does not take timezones into account > -------------------------------------------------------------- > > Key: JBIDE-22244 > URL: https://issues.jboss.org/browse/JBIDE-22244 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > > it seems like the default {{HOURS}} value ('2') for the job that copies bugzilla issues into JIRA (in the ERT project) is not enough to catch the changes. This might be due to the timezones, since the script run by the job and the job itself do not use the same timezone. > for example: > - I created an issue in BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=492420 on 2016-04-26 03:07:04 EDT > - I then manually kicked the job with the {{HOURS}} value set to {{2}} (Build #2073 - Apr 26, 2016 3:19:03 AM). (I assume the TZ is EDT here, too.) > - The script output contains the following lines: > {{code}} > 03:19:10 [DEBUG] Current datetime: 2016-04-26 07:19:09.521272 (UTC) > 03:19:10 [DEBUG] xmlrpc post: {'status_whiteboard': 'RHT', 'last_change_time': '2016-04-26 04:19'} > 03:19:10 [DEBUG] buglist get: https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT&chfieldfr... > 03:19:10 [DEBUG] Found 0 bugzillas to process > {{code}} > In the mean time, setting the {{HOURS}} value to '6', I was able to get the issue created in JIRA. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-173) Need to find a better solution for npm dependencies content assistant [EBZ#492192]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-173: --------------------------------------- Summary: Need to find a better solution for npm dependencies content assistant [EBZ#492192] Key: ERT-173 URL: https://issues.jboss.org/browse/ERT-173 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot In order to show content assist proposals for npm dependencies a 3rd party web service was used. It was a really problematic due to its unstable work, slowness and a tendency to change an URL for requests and formats of response. I do believe, we should not provide any content assist for dependencies in case no search pattern is provided (typed in) by a user because of really huge memory requirements and network overload in such case: - Native "npm search" command fails to list all the available packages on my environment after about 5 minutes of downloading packages Given this, IMHO, we have not to show *all* available packages in content assistant, but show package list only if at least first letter (or a couple of beginning letters) of package name is typed in by a user. Also the way to get the proposals itself is also a question: we cannot rely on 3rd party services as they are not enough stable and fast. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-170) Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-170: --------------------------------------- Summary: Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735] Key: ERT-170 URL: https://issues.jboss.org/browse/ERT-170 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot The normal scenario for starting a chomium debugger process includes both launching the main js runtime (Node), and also starting the V8 debugger process... Users will expect the same when terminating (both are killed). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-171) [ES6] Define a way to enable module parsing [EBZ#492130]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-171: --------------------------------------- Summary: [ES6] Define a way to enable module parsing [EBZ#492130] Key: ERT-171 URL: https://issues.jboss.org/browse/ERT-171 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot By default JSDT uses "script" source type parsing, which causes import/exports to be marked as erors. JSDT needs to define a way for projects to opt-int to use "module" parsing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016