November 2016 - jbosstools-issues

[JBoss JIRA] (ERT-462) Fix copy from container to support stopped containers and to allow copying of whole directories [EBZ#508233]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-462: --------------------------------------- Summary: Fix copy from container to support stopped containers and to allow copying of whole directories [EBZ#508233] Key: ERT-462 URL: https://issues.jboss.org/browse/ERT-462 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.2 (4.6) The copy from container feature slated for 5.2.0 only supports copying files but not an entire directory. As well, it only supports copying when the container is running. When a user specifies a directory by clicking on it, then copy the whole directory to the target. Support copying when the container is stopped but do not offer the container browser. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by cube 00 (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] cube 00 updated JBDS-4204: -------------------------- Attachment: jboss3.PnG > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Reporter: cube 00 > Attachments: jboss1.png, jboss2.png, jboss3.PnG > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by cube 00 (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] cube 00 updated JBDS-4204: -------------------------- Description: The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. (was: The window either cuts the top off, bottom off or overdraws into space near the window.) Steps to Reproduce: Start JBoss, maximise the window (title bar disappears), click to another window (title bar appears bottom status bar disappears). Open a dialog OK/Cancel buttons are cut off and inaccessible. was:Start JBoss, maximise the window (title bar disappears), click to another window (title bar appears bottom status bar disappears) Summary: JBoss IDE and dialogs not sizing correctly under Fedora 25 (was: JBoss IDE window not sizing correctly under Fedora 25) > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Reporter: cube 00 > Attachments: jboss1.png, jboss2.png > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE window not sizing correctly under Fedora 25

by cube 00 (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] cube 00 updated JBDS-4204: -------------------------- Summary: JBoss IDE window not sizing correctly under Fedora 25 (was: JBoss IDE window not sizing correctly unded Fedora 25) > JBoss IDE window not sizing correctly under Fedora 25 > ----------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Reporter: cube 00 > Attachments: jboss1.png, jboss2.png > > > The window either cuts the top off, bottom off or overdraws into space near the window. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE window not sizing correctly unded Fedora 25

by cube 00 (JIRA)

cube 00 created JBDS-4204: ----------------------------- Summary: JBoss IDE window not sizing correctly unded Fedora 25 Key: JBDS-4204 URL: https://issues.jboss.org/browse/JBDS-4204 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Reporter: cube 00 Attachments: jboss1.png, jboss2.png The window either cuts the top off, bottom off or overdraws into space near the window. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23475: ------------------------------------ I've got a pom.xml and a python script that can do per-segment (staging, snapshots, development, stable) file manipulation to swap in/out versions of JBT and devstudio from within the new .fragment files, then merge them into an ide-config.properties file that Cental will read. It's still a work in progress -- want to be able to run it from commandline w/o having to edit the pom.xml but ran out of time today. So, going forward, if you make changes to ide-config.properties itself, they may be overwritten if someone runs the maven build to do the python transform. Instead, you should edit these fragment files [1] as required, and the pom.xml [2] (to enable/disable regex transformations), then run the build to re-merge them into a new ide-config.properties file. [1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... [1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > split ide-config.properties into multiple files > ------------------------------------------------- > > Key: JBIDE-23475 > URL: https://issues.jboss.org/browse/JBIDE-23475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, central-update > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation. > So, rather than 1 big file [1] we could split this into 5 files: > * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA) > * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3) > * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA) > * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA) > * ide-config.properties - contains all the other properties for 4.3.x and earlier releases > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value. > From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23555) Arquillian New and Noteworthy for 4.4.2.Final

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23555?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-23555. --------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.4.2.Final > ----------------------------------------------------- > > Key: JBIDE-23555 > URL: https://issues.jboss.org/browse/JBIDE-23555 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian 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 Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian 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 Arquillian4.4.2.Final #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 Arquillian for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Arquillian, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4128) Missing a checkbox for creating a server in New EAP Runtime wizard

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-4128?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-4128: -------------------------------- Fix Version/s: 10.3.0.AM1 (was: 10.2.0.GA) > Missing a checkbox for creating a server in New EAP Runtime wizard > ------------------------------------------------------------------ > > Key: JBDS-4128 > URL: https://issues.jboss.org/browse/JBDS-4128 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: runtime > Affects Versions: 10.2.0.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.AM2 > Build id: AM2-v20161014-1657-B6205 > Build date: 20161014-1657 > Reporter: Andrej Podhradsky > Assignee: Snjezana Peco > Fix For: 10.3.0.AM1 > > Attachments: new_server_checkbox.png > > > There is no checkbox for creating a server in New EAP Runtime wizard. > !new_server_checkbox.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23518) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23518?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23518. ------------------------------ Resolution: Done > For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [aerogear-hybrid] > ---------------------------------------------------------------------------- > > Key: JBIDE-23518 > URL: https://issues.jboss.org/browse/JBIDE-23518 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.2.Final > > > For JBIDE 4.4.2.Final [aerogear-hybrid]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests cordova cordovasim feedhenry pom.xml pom.xml.orig README.md site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23520) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [foundation]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23520?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23520. ------------------------------ Resolution: Done > For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-23520 > URL: https://issues.jboss.org/browse/JBIDE-23520 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.Final > > > For JBIDE 4.4.2.Final [foundation]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: all-tests common foundation pom.xml pom.xml.orig README.md runtime site stacks tests usage *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: all-tests common foundation pom.xml pom.xml.orig README.md runtime site stacks tests usage *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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