November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-20945: ------------------------------------------- Fix Version/s: 4.4.x > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > Labels: ui-scaling > Fix For: 4.4.x > > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Component-install job is not reliable

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-21145: ---------------------------------- Summary: Component-install job is not reliable Key: JBIDE-21145 URL: https://issues.jboss.org/browse/JBIDE-21145 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 Reporter: Pavol Srna We have often seen old artifacts on nightly sites (mars and neon too). It seems that the composite-install job is not reliable. The build is not triggered automatically with every new change in the repository. Please investigate. Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21144) Invalid local template path validation is not shown correctly

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21144: ------------------------------------- Summary: Invalid local template path validation is not shown correctly Key: JBIDE-21144 URL: https://issues.jboss.org/browse/JBIDE-21144 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda Attachments: invalid_value_local_template_tab.png, invalid_value_server_template_tab.png In New OpenShift Application wizard on first wizard page where selection of a template is, there are two tabs, one for server and one for local template validation. If I put an invalid path to local template by typing/pasting value into text widget for local template path !invalid_value_local_template_tab.png! the path is not validated until I select server template tab. Then there is shown an error on the wizard page !invalid_value_server_template_tab.png! We should at least validate path to its existence and shown appropriate validation error mark on the first wizard page while local template tab is active. Processing of template is good as it is (it is processed after clicking next button), only validation need refining. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- >> Yes, that saves time for the download but not for unzipping of the runtime. >If one is using the unpack mojo of maven-depedency-plugin or the wget mojo or download-maven-plugin with unpack param >set to true, then the fetch and unzip are part of the same mojo, and skipping fetch also skip unzip. >Do you have an example of bundles where skipping download doesn't skip unpack? No, what I was referring to was that we still need the skip flag since even if download is cached unpacking is not. > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- [~nickboldt] Would you mind to take care of it? Can I assign it to you? > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20717) Inconsistent upper casing in New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20717?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20717. --------------------------------- Resolution: Done Fixed "Save Token" casing in 4.3.x and master > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-20717 > URL: https://issues.jboss.org/browse/JBIDE-20717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21111) [connection wizard] empty password should not be allowed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21111?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21111: -------------------------------- Summary: [connection wizard] empty password should not be allowed (was: [connection wizard] empty password should be allowed) > [connection wizard] empty password should not be allowed > -------------------------------------------------------- > > Key: JBIDE-21111 > URL: https://issues.jboss.org/browse/JBIDE-21111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21111) [connection wizard] empty password should not be allowed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21111?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21111. --------------------------------- Resolution: Done commit reverted in master > [connection wizard] empty password should not be allowed > -------------------------------------------------------- > > Key: JBIDE-21111 > URL: https://issues.jboss.org/browse/JBIDE-21111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21110) [connection wizard] empty password should not be allowed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21110?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21110: -------------------------------- Summary: [connection wizard] empty password should not be allowed (was: [connection wizard] empty password should be allowed) > [connection wizard] empty password should not be allowed > -------------------------------------------------------- > > Key: JBIDE-21110 > URL: https://issues.jboss.org/browse/JBIDE-21110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21110) [connection wizard] empty password should not be allowed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21110?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21110. --------------------------------- Resolution: Done commit reverted in 4.3.x > [connection wizard] empty password should not be allowed > -------------------------------------------------------- > > Key: JBIDE-21110 > URL: https://issues.jboss.org/browse/JBIDE-21110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 2015