April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3871: ----------------------------------- Assignee: Denis Golovin > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3842) Migrate to Eclipse Neon

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3842?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3842: --------------------------------- Fix Version/s: 10.0.0.Alpha2 (was: 10.0.0.Alpha1) > Migrate to Eclipse Neon > ----------------------- > > Key: JBDS-3842 > URL: https://issues.jboss.org/browse/JBDS-3842 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 10.0.0.Alpha2 > > > This Epic is for tasks related to Devstudio migration to Eclipse Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21674: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Enable hierarchical view by default in Project Explorer > ------------------------------------------------------- > > Key: JBIDE-21674 > URL: https://issues.jboss.org/browse/JBIDE-21674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Xavier Coulon > Fix For: 4.4.x > > > Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects). > After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21674: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > Enable hierarchical view by default in Project Explorer > ------------------------------------------------------- > > Key: JBIDE-21674 > URL: https://issues.jboss.org/browse/JBIDE-21674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Xavier Coulon > Fix For: 4.4.x > > > Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects). > After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features are shown in Help->About->Installation Details->Features

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20431: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Make sure all installed features are shown in Help->About->Installation Details->Features > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common/jst/core, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22278) OpenShift Explorer should be made visible when a new Connection is created

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22278?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22278: -------------------------------- Description: OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. Could be done through a connection listener in the UI activator was:OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. Fix Version/s: 4.4.x Story Points: 2 > OpenShift Explorer should be made visible when a new Connection is created > -------------------------------------------------------------------------- > > Key: JBIDE-22278 > URL: https://issues.jboss.org/browse/JBIDE-22278 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Fix For: 4.4.x > > > OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. > Could be done through a connection listener in the UI activator -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22278) OpenShift Explorer should be made visible when a new Connection is created

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22278: ----------------------------------- Summary: OpenShift Explorer should be made visible when a new Connection is created Key: JBIDE-22278 URL: https://issues.jboss.org/browse/JBIDE-22278 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Fred Bricon OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22265) Application wizard: Allow users to reset values of all template parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22265?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22265: ----------------------------------------------- As in JBIDE-22263, the following enhancements are done: 1. Button 'Reset All' is added. 2. Modified values are rendered in italics. 3. Buttons 'Reset' and 'Reset All' are enabled only when they can reset something. > Application wizard: Allow users to reset values of all template parameters > -------------------------------------------------------------------------- > > Key: JBIDE-22265 > URL: https://issues.jboss.org/browse/JBIDE-22265 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > At the moment we allow users to reset a specific value in the table containing template parameters in New OpenShift Application wizard. It would be nice to have option to reset all template parameters (get default values for all) to have it consistent across wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21621) Include proper version of RedDeer to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21621?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21621: ------------------------------------ If it's genuinely a snapshot the snapshots/ is reasonable. Don't just throw it in development if it's a pre-release of a milestone. :D > Include proper version of RedDeer to TP > --------------------------------------- > > Key: JBIDE-21621 > URL: https://issues.jboss.org/browse/JBIDE-21621 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Vlado Pakan > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ {quote}Then we have to go all the way and remove build label from version and stop changing versions for plugins/features all together.{quote}If you mean removing the BUILD_ALIAS = Alpha, Beta, CR, Final/GA, I'm not adverse to that idea. But we can still make THIS change and then work to convince people the ALIAS is no longer required. :D Note also that AFAIK this doc is still in effect: https://developer.jboss.org/wiki/JBossProjectVersioning > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016