September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18293?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18293: ----------------------------------- Labels: (was: respin-b) > New seam with new version is not selected as a default runtime envirnment for its version > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18293 > URL: https://issues.jboss.org/browse/JBIDE-18293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Priority: Optional > Fix For: 4.2.0.CR1 > > > If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version. > However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18293?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18293: ----------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.CR1) > New seam with new version is not selected as a default runtime envirnment for its version > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18293 > URL: https://issues.jboss.org/browse/JBIDE-18293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Priority: Optional > Fix For: 4.3.x > > > If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version. > However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18293) New seam with new version is not selected as a default runtime envirnment for its version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18293?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18293: ----------------------------------- Priority: Optional (was: Major) > New seam with new version is not selected as a default runtime envirnment for its version > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18293 > URL: https://issues.jboss.org/browse/JBIDE-18293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Priority: Optional > Fix For: 4.2.0.CR1 > > > If there is a seam runtime environment, then there has to be also defined a default runtime environment for its version. > However, when a new seam is being added, which has a version that has not defined runtime environment, then the seam will be added but it will not be checked (marked as default for its version). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12108) BrowserSim is not visible when installed individually

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12108?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-12108: --------------------------------------- [~ibuziuk], look at JBoss Central button in toolbar, it seems to do what we want for BrowserSim - https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... > BrowserSim is not visible when installed individually > ------------------------------------------------------ > > Key: JBIDE-12108 > URL: https://issues.jboss.org/browse/JBIDE-12108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: JBT 3.3.0.CR1b, L64, Ubuntu 12.04 > Reporter: Jiri Peterka > Assignee: Ilya Buziuk > Fix For: 4.2.0.CR2 > > Attachments: browsersim-enabled.png, customize-perspective.png, enable-browsersim.png, mobile-browser.bmp > > > Unable to access BrowserSIM when installed as single feature from JBT CR1. Additional steps are required. This is confusing for a users. BrowserSIM should be accessible and visible after installation if possible. > *These additional steps are:* > # Right click on the Eclipse toolbar→Customize Perspective...: > !customize-perspective.png! > # Go to the Command Group Availability tab and select BrowserSim command group: > !enable-browsersim.png! > # BrowserSim icon will appear on the toolbar: > !browsersim-enabled.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3002) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems

by Alexey Pakseykin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3002?page=com.atlassian.jira.plugin.... ] Alexey Pakseykin commented on JBDS-3002: ---------------------------------------- OK, I'll verify it with 8.0.0.CR1. By "default choice" and "zero config" I mean that it should be relatively easy to automate and catch in CI. 8.0.0.beta3 or 7.1.1.GA are simply the only latest packages available for download from: http://www.jboss.org/products/devstudio/download/ F20 is the first OS which came into my mind when I wanted to install JBDS (IMHO, it's likely common idea as both are sponsored by Red Hat). > JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3002 > URL: https://issues.jboss.org/browse/JBDS-3002 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, updatesite > Affects Versions: 7.1.1.GA > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: respin-a > Fix For: 8.0.0.CR1 > > > We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert: > {code}One or more certificates rejected. Cannot proceed with installation.{code} > Full details: https://community.jboss.org/message/866868 > *Platform details:* > {code} > Debian Jessie 64 bit > $ uname -a: > Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux > $ java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2) > OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) > {code} > Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :) > [0] http://www.debian.org/releases/jessie/ > [1] http://www.debian.org/releases/ > [2] http://www.debian.org/releases/wheezy/ > [3] https://release.debian.org/ > *Steps to repro on the above platform:* > 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru > 3. Install failed with an error re certificates not being trusted > 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows: > !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061 > !MESSAGE One or more certificates rejected. Cannot proceed with installation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Daniel Azarov edited comment on JBIDE-18083 at 9/9/14 2:57 PM: --------------------------------------------------------------- If you press button "Environments..." then press "Installed JREs" you will see: !InstalledJREs.png! instead Installed JREs was (Author: dazarov): If you press button "Environments..." then you will see: !InstalledJREs.png! instead Installed JREs > Issues in the new "Edit server runtime environment" window > ---------------------------------------------------------- > > Key: JBIDE-18083 > URL: https://issues.jboss.org/browse/JBIDE-18083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu 14.04, Eclipse 64 bit, Java 1.7 > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > Attachments: InstalledJREs.png, InstalledJREs2.png, server_runtime.png > > > See attached screenshot: there are three problems in the "Edit Server runtime environment" window. > a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused > b) same for the button "Installed JREs" > c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18275) Visual Editor: remove option of showing VPE toolbar in Eclipse toolbar

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18275?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18275: --------------------------------------- +1 > Visual Editor: remove option of showing VPE toolbar in Eclipse toolbar > ---------------------------------------------------------------------- > > Key: JBIDE-18275 > URL: https://issues.jboss.org/browse/JBIDE-18275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.CR1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18209) Autoapply new default JS/CSS library preferences

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18209?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18209: ---------------------------------------- We should fix it in 4.2.0 since it affects old workspaces. So the new JS/CSS libraris (Ionic for example) won't appear in new palette wizards for old workspaces. > Autoapply new default JS/CSS library preferences > ------------------------------------------------ > > Key: JBIDE-18209 > URL: https://issues.jboss.org/browse/JBIDE-18209 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: respin-b > Fix For: 4.2.0.CR1 > > > Preferences JBossTools->Web->JS/CSS are initially set to default versions declared in extension point org.jboss.tools.jst.web.ui.jscssLibs. User can change some of them and leave some default libraries. New version of JBossTools may change some default libraries and add new. > With current implementation, user would have to go to preferences and use 'Restore Defaults' to get new default libraries. That is not good, new default libraries should replace old default libraries automatically. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18083) Issues in the new "Edit server runtime environment" window

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18083?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-18083: --------------------------------------- My PR fixes this !InstalledJREs2.png! [~rob.stryker], please review it > Issues in the new "Edit server runtime environment" window > ---------------------------------------------------------- > > Key: JBIDE-18083 > URL: https://issues.jboss.org/browse/JBIDE-18083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Environment: Windows 7x6, Eclipse 64 bit version, java 1.7, Ubuntu 14.04, Eclipse 64 bit, Java 1.7 > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR1 > > Attachments: InstalledJREs.png, InstalledJREs2.png, server_runtime.png > > > See attached screenshot: there are three problems in the "Edit Server runtime environment" window. > a) clicking the button "Environments" opens the "Execution Environments" preference window behind the current window, it cannot be focused > b) same for the button "Installed JREs" > c) the "Configuration base directory" is defaulted to "C:standalone". This does probably not make sense ;-). For WildFly7 server types, it is "standalone". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18209) Autoapply new default JS/CSS library preferences

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18209?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18209: ----------------------------------- Issue Type: Bug (was: Enhancement) > Autoapply new default JS/CSS library preferences > ------------------------------------------------ > > Key: JBIDE-18209 > URL: https://issues.jboss.org/browse/JBIDE-18209 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: respin-b > Fix For: 4.2.0.CR1 > > > Preferences JBossTools->Web->JS/CSS are initially set to default versions declared in extension point org.jboss.tools.jst.web.ui.jscssLibs. User can change some of them and leave some default libraries. New version of JBossTools may change some default libraries and add new. > With current implementation, user would have to go to preferences and use 'Restore Defaults' to get new default libraries. That is not good, new default libraries should replace old default libraries automatically. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014