June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22569) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Freemarker]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22569?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22569: ----------------------------------- Story Points: 1 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Freemarker] > ------------------------------------------------------------- > > Key: JBIDE-22569 > URL: https://issues.jboss.org/browse/JBIDE-22569 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Freemarker]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22563) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22563?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22563. ---------------------------------- Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JavaEE] > --------------------------------------------------------- > > Key: JBIDE-22563 > URL: https://issues.jboss.org/browse/JBIDE-22563 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [JavaEE]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22569) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Freemarker]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22569?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22569: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Freemarker] > ------------------------------------------------------------- > > Key: JBIDE-22569 > URL: https://issues.jboss.org/browse/JBIDE-22569 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Freemarker]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22558) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22558?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22558: ------------------------------------- https://github.com/jbosstools/jbosstools-server/pull/427 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Server] > --------------------------------------------------------- > > Key: JBIDE-22558 > URL: https://issues.jboss.org/browse/JBIDE-22558 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Server]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3932) Pre-existing VAGRANT_DETECTED_OS env setting causes installation to fail

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3932?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3932: -------------------------------- Story Points: 2 Sprint: devex #115 May 2016 > Pre-existing VAGRANT_DETECTED_OS env setting causes installation to fail > ------------------------------------------------------------------------ > > Key: JBDS-3932 > URL: https://issues.jboss.org/browse/JBDS-3932 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Environment: development-suite-10.0.0-GA-20160606-166-bundle-installer.exe > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > > Having a pre-existing VAGRANT_DETECTED_OS env setting (for example VAGRANT_DETECTED_OS = cygwin), causes the installer to fail to install the CDK. > The error written to the install log is: > Mon, 06 Jun 2016 16:00:03 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\DevelopmentSuite\cdk\boxes\rhel-vagrant-virtualbox.box" > [0;31mThe executable 'cygpath' Vagrant is trying to run was not > found in the %PATH% variable. This is an error. Please verify > this software is installed and on the path. [0m > > Mon, 06 Jun 2016 16:00:03 GMT-ERROR: cdk - [0;31mThe executable 'cygpath' Vagrant is trying to run was not > found in the %PATH% variable. This is an error. Please verify > this software is installed and on the path. [0m > > Mon, 06 Jun 2016 16:00:03 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\DevelopmentSuite\cdk\boxes\rhel-vagrant-virtualbox.box" > [0;31mThe executable 'cygpath' Vagrant is trying to run was not > found in the %PATH% variable. This is an error. Please verify > this software is installed and on the path. [0m -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3933) Platform installer - If the installer is run while (inadvertently) off the network, the error message only indicates an invalid password

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3933?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3933: ------------------------------- Attachment: error.png > Platform installer - If the installer is run while (inadvertently) off the network, the error message only indicates an invalid password > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3933 > URL: https://issues.jboss.org/browse/JBDS-3933 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Environment: development-suite-10.0.0-GA-20160607-173-bundle-installer.exe > Reporter: Len DiMaggio > Attachments: error.png > > > A more informative error message ("network failure", etc.) would be helpful - see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22564) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22564?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22564. ---------------------------------- Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JST] > ------------------------------------------------------ > > Key: JBIDE-22564 > URL: https://issues.jboss.org/browse/JBIDE-22564 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [JST]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22563) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22563?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22563: -------------------------------------- Story Points: 1 Assignee: Alexey Kazakov > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [JavaEE] > --------------------------------------------------------- > > Key: JBIDE-22563 > URL: https://issues.jboss.org/browse/JBIDE-22563 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [JavaEE]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3933) Platform installer - If the installer is run while (inadvertently) off the network, the error message only indicates an invalid password

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3933: ---------------------------------- Summary: Platform installer - If the installer is run while (inadvertently) off the network, the error message only indicates an invalid password Key: JBDS-3933 URL: https://issues.jboss.org/browse/JBDS-3933 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.GA Environment: development-suite-10.0.0-GA-20160607-173-bundle-installer.exe Reporter: Len DiMaggio A more informative error message ("network failure", etc.) would be helpful - see the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22549) "Result" dialog enhancements

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22549?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22549: ------------------------------------- https://github.com/jbosstools/jbosstools-server/pull/426 - PR to add ctrl+c and copy context menu to jmx result window > "Result" dialog enhancements > ---------------------------- > > Key: JBIDE-22549 > URL: https://issues.jboss.org/browse/JBIDE-22549 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.0.Final > Reporter: Xavier Coulon > Attachments: Screenshot 2016-06-07 11.35.28.png > > > When executing a JMX remote operation, the "Result" dialog displays a single column that cannot be expanded, and the row content cannot be copied into the clipboard. > See the attached screenshot for visual explanations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016