March 2016 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------- [~pmuir] in the header of the Installer. I would be on every page. Currently it is 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

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBDS-3710?page=com.atlassian.jira.plugin.... ] Pete Muir commented on JBDS-3710: --------------------------------- [~maxandersen] No, the installer is part of devstudio - that is in the product definition deck. [~jowilson] in what context do you want to use the Brackets logo? > 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

[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22004: ------------------------------------- Hi Hardy: The primary purpose of this file is to designate what is or is not a cdk. It has other secondary purposes which help us in creating our openshift and docker connections, but this is primary. Without this marker file, all we'd have is Vagrantfile. When a user wants to 'scan' a folder recursively to locate any cdk instances, we'd probably end up claiming every folder with a VagrantFile in it is a cdk, because there's no real way to parse the VagrantFile to determine if it's actually referencing the CDK or not. Instead, we ask the installer or other distributions to include a .cdk file so that we can separate it from other vagrant instances. Does this need to be in a raw cdk distribution? Only if we want the tools to autodetect it when a user scans a folder. > Runtime detection unable to detect CDK > -------------------------------------- > > Key: JBIDE-22004 > URL: https://issues.jboss.org/browse/JBIDE-22004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Hardy Ferentschik > Fix For: 4.4.x > > > Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it. > Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22035) Stopping of J2EE module does not work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22035: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Stopping of J2EE module does not work > ------------------------------------- > > Key: JBIDE-22035 > URL: https://issues.jboss.org/browse/JBIDE-22035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following > {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec > total size is 8,523,390 speedup is 6,180.85 > sending incremental file list > ROOT.war.isdeploying > sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec > total size is 8,523,390 speedup is 5,404.81{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22035) Stopping of J2EE module does not work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22035: -------------------------------------- Assignee: Rob Stryker > Stopping of J2EE module does not work > ------------------------------------- > > Key: JBIDE-22035 > URL: https://issues.jboss.org/browse/JBIDE-22035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following > {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec > total size is 8,523,390 speedup is 6,180.85 > sending incremental file list > ROOT.war.isdeploying > sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec > total size is 8,523,390 speedup is 5,404.81{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3738: -------------------------------------- [~mhusnain] you can talk with [~fbricon] about content of this doc. > Getting Started / Readme for new users after Dev Platform install is complete > ----------------------------------------------------------------------------- > > Key: JBDS-3738 > URL: https://issues.jboss.org/browse/JBDS-3738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Labels: Havoc > Fix For: 9.1.0.GA > > > Per discussion today, we need some sort of README / Getting Started Guide for new CDK users. > This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline. > Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22040) Changes in 'www' are not propagated to xcode build

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22040?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-22040. ---------------------------------- Resolution: Rejected This was observed due to JBIDE-22044 > Changes in 'www' are not propagated to xcode build > -------------------------------------------------- > > Key: JBIDE-22040 > URL: https://issues.jboss.org/browse/JBIDE-22040 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Priority: Critical > Fix For: 4.3.1.CR1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=490768 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22014) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Integration Tests]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22014?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22014. ---------------------------------- Assignee: Len DiMaggio Resolution: Done > For JBIDE 4.3.1.CR1: Prepare for Final/GA [Integration Tests] > ------------------------------------------------------------- > > Key: JBIDE-22014 > URL: https://issues.jboss.org/browse/JBIDE-22014 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [Integration Tests]: 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 Integration Tests 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-21995) Hostname is set to localhost when prompt for route is checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21995: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1074, https://github.com/jbosstools/jbosstools-openshift/pull/1077 > Hostname is set to localhost when prompt for route is checked > ------------------------------------------------------------- > > Key: JBIDE-21995 > URL: https://issues.jboss.org/browse/JBIDE-21995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22019?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22019: -------------------------------------- Assignee: Fred Bricon > For JBIDE 4.3.1.CR1: Prepare for Final/GA [OpenShift] > ----------------------------------------------------- > > Key: JBIDE-22019 > URL: https://issues.jboss.org/browse/JBIDE-22019 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.3.1.CR1 > > > For JBIDE 4.3.1.CR1 [OpenShift]: 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 OpenShift 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

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