March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22028) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Central]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22028?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22028: -------------------------------------- Assignee: Fred Bricon > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Central] > --------------------------------------------------- > > Key: JBIDE-22028 > URL: https://issues.jboss.org/browse/JBIDE-22028 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Central]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 Central 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22029) For JBIDE 4.3.1.CR1: Prepare for Final/GA [LiveReload]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22029?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22029: -------------------------------------- Assignee: Xavier Coulon > For JBIDE 4.3.1.CR1: Prepare for Final/GA [LiveReload] > ------------------------------------------------------ > > Key: JBIDE-22029 > URL: https://issues.jboss.org/browse/JBIDE-22029 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [LiveReload]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 LiveReload 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22016) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22016?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22016: -------------------------------------- Assignee: Rob Stryker > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server] > -------------------------------------------------- > > Key: JBIDE-22016 > URL: https://issues.jboss.org/browse/JBIDE-22016 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Server]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22017) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Hibernate]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22017?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22017. ---------------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Hibernate] > ----------------------------------------------------- > > Key: JBIDE-22017 > URL: https://issues.jboss.org/browse/JBIDE-22017 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Hibernate]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 Hibernate 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22023) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22023?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22023: ----------------------------------------- Thanks [~akazakov]! > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Forge] > ------------------------------------------------- > > Key: JBIDE-22023 > URL: https://issues.jboss.org/browse/JBIDE-22023 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Forge]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 Forge 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22023) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Forge]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22023?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22023. ---------------------------------- Assignee: George Gastaldi Resolution: Done > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Forge] > ------------------------------------------------- > > Key: JBIDE-22023 > URL: https://issues.jboss.org/browse/JBIDE-22023 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Forge]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final > [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch: > {code} > git checkout jbosstools-4.3.x > {code} > 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch > 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0) > {code} > mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT > {code} > 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2) > {code} > mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. 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 Forge 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3748: ---------------------------------- Dev Platform installer bundle is 1.6G; unpacked and installed it's more than 1.7G. So that's 3.3GB right there, before you've even started up JBDS. Probably want to say minimum 5G, recommended 10G. Lots of breathing room that way, and if the user needs to install any part of the dev platform again they'll need some space to do so. Would also suggest we bump the RAM suggestions to minimum 8GB, recommended 16GB. > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3748: ----------------------------- Description: The latest information that I can find for JBDS is: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... This is not adequate for the CDK, etc. was: The latest information that I can find for JBDS is: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... This is not adequate for the CDK, etc. > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3748: ------------------------------------ More recent doc: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3710) use brackets logo for Developer Platform installer

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-3710: ------------------------------------- [~maxandersen] [~crobson] [~sjcox] can I use the Brackets logo inside the UI? Currently we have Shadowman. > use brackets logo for Developer Platform installer > -------------------------------------------------- > > Key: JBDS-3710 > URL: https://issues.jboss.org/browse/JBDS-3710 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: RedHatDeveloperStudio_Logo_Installer.ico > > > Based on feedback from [~pmuir], [~tmancini] and [~crobson] we'll go for using the brackets logo for the big Developer Platform installers (56M stub and 1.6G bundled). -- 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 March 2016