November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21048) Download Runtimes should not require constantly typing credentials for each download

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21048?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21048: ----------------------------------- Assignee: Rob Stryker > Download Runtimes should not require constantly typing credentials for each download > ------------------------------------------------------------------------------------ > > Key: JBIDE-21048 > URL: https://issues.jboss.org/browse/JBIDE-21048 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > > Download runtimes, when used for downloading EAP / JPP / Fuse runtimes, requires typing in credentials and verifying them. This can be made simpler for the user, either by persisting the credentials directly or by referencing the (possible) credentialing framework (JBIDE-21043) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21048) Download Runtimes should not require constantly typing credentials for each download

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21048?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21048: ------------------------------------- Linking. > Download Runtimes should not require constantly typing credentials for each download > ------------------------------------------------------------------------------------ > > Key: JBIDE-21048 > URL: https://issues.jboss.org/browse/JBIDE-21048 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > > Download runtimes, when used for downloading EAP / JPP / Fuse runtimes, requires typing in credentials and verifying them. This can be made simpler for the user, either by persisting the credentials directly or by referencing the (possible) credentialing framework (JBIDE-21043) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21043) Create a credentialing framework

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21043?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21043: ------------------------------------- > what will a plugin store in its setup instead of the username/password ? Ideally it would store a domain / username combination. Some may not even need to store the hostname, as they're already limited to using jboss.org / rht credential systems (see dl.runtimes).... Or, as another idea (not yet coded), it could also allow "Default Username" as an option... so for each host you could have multiple usernames but mark one as the default. Clients who want can store host+username, others could store host+"default username" option, which would allow them to resolve not only the password but also the username. But this seems a niche case... users aren't often changing usernames and deleting the old ones, but it does happen. > i.e. how is it ensured that when I change the setting in my credentials page it will be updated in the other plugin ? The other plugins should be dynamically pulling the password. > when does it make sense to only add a domain ? A plugin may contribute a domain (possibly through extension point? Currently just hard-coded jboss.org and access.redhat.com). It may make sense to put the domain in there for a few purposes: 1) The plugin must query for usernames at a given domain. By contributing the domain directly, the plugins can ensure the domain is properly typed in and has the exact id they will query on, minimizing error for users. 2) Users can see where they need to add the credential, so it helps guide the user as well. > why not just entries with username + host that you then can show by domain or if you wanted by user ? Well, for example dl-runtimes or openshift may need to query on a specific domain string, looking for all usernames with a given host. Users may not be consistant with how they declare the domain. They may type in 'jira.jboss.org' instead of just jboss.org, and then dl.runtimes won't know to query on jira.jboss.org. I also made this design decision because the tree is also easily navigable now in the secure storage page, split by domain, and properly encrypted, and I feel easier to read through in the case of debugging or digging around... I admit the PR is a work in progress, and I welcome all feedback for enhancement to cover more usecases. I like the idea of having configurators respond to changes in the credential model and then update dependent models (such as mylyn jira / bz) that cannot automatically reference this new credential area. > Create a credentialing framework > -------------------------------- > > Key: JBIDE-21043 > URL: https://issues.jboss.org/browse/JBIDE-21043 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Attachments: JBIDE-21043.png, JBIDE-21043a.png > > > There should be a unified framework for storing credentials to various domains. As of now, download runtimes (in astools) requires redhat or jboss credentials, and I've heard that others are also storing the credentials for some of those domains as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21027: ---------------------------------------- Both issues are part of the same story, however a previous discussion made it important to have 2 distinct commits (one for JBIDE-21027 then the one for JBIDE-20609), as one is a bug vs the other is an enhancement. > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21027: ------------------------------------- Exactly, and I think both problems should be treated consistently. > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21035: ------------------------------------ Cool. Please update my PR to show what that change would look like. > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21035: ---------------------------------------- No objection. A change we can do as part of this migration is to replace the reference from JBT compare-version-with-baselines mojo by the Tycho one, which is included in 0.24.0 > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21035) Build with Tycho 0.24.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21035?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21035: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/207, https://github.com/jbosstools/jbosstools-build/pull/208 (was: https://github.com/jbosstools/jbosstools-build/pull/207) > Build with Tycho 0.24.0 > ----------------------- > > Key: JBIDE-21035 > URL: https://issues.jboss.org/browse/JBIDE-21035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {quote} > Tycho milestone 0.24.0 has been released and is available from maven central. > See the release notes [1] for details of enhancements and bug fixes in this release. > Thanks to: > Alexander Kurtakov > Lars Vogel > Mickael Istria > Mikolaj Izdebski > who contributed patches for this release. > And thanks and to everyone who helped us with testing the staged version. > Regards, > Tycho team > [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.24 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21047) Node / Bower / npm - Need to remove external bundle dependencies before contribution to eclipse

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-21047: ----------------------------------- Summary: Node / Bower / npm - Need to remove external bundle dependencies before contribution to eclipse Key: JBIDE-21047 URL: https://issues.jboss.org/browse/JBIDE-21047 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: nodejs Affects Versions: 4.3.0.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.4.0.Alpha1 Fortunately there is only one dependency to *org.jboss.tools.common* that must be removed before contribution to eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21003) Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21003?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21003: ------------------------------------ [~jcantrill] [~akazakov] [~xcoulon] If you want this in Beta0 we need to update our TP in the next 2 weeks. Please advise what features/plugins you want included in the 4.51.1.CR1 and 4.60.0.Alpha1 target platforms, and from which URLs to fetch them. > Update target platform for linxtools.docker.ui to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21003 > URL: https://issues.jboss.org/browse/JBIDE-21003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *Reason:* update linuxtools.docker to expose ImageSearch wizard > *Project page/sources:* https://bugs.eclipse.org/bugs/show_bug.cgi?id=480308 > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* Leave empty > *Include Sources:* Yes > *Affected JBoss Tools components:* jbosstools-openshift > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 2015