November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21136) Display projects on Import proposal in tree format

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21136?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-21136: ------------------------------------ Attachment: maven-import.png current-state.png > Display projects on Import proposal in tree format > -------------------------------------------------- > > Key: JBIDE-21136 > URL: https://issues.jboss.org/browse/JBIDE-21136 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Reporter: Lucia Jelinkova > Attachments: current-state.png, maven-import.png > > > It would be nice to display the projects in the tree format (as in Maven import) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21136) Display projects on Import proposal in tree format

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-21136: --------------------------------------- Summary: Display projects on Import proposal in tree format Key: JBIDE-21136 URL: https://issues.jboss.org/browse/JBIDE-21136 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: easymport Reporter: Lucia Jelinkova It would be nice to display the projects in the tree format (as in Maven import) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21135) Unify plugin names for easymport

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-21135: --------------------------------------- Summary: Unify plugin names for easymport Key: JBIDE-21135 URL: https://issues.jboss.org/browse/JBIDE-21135 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: easymport Affects Versions: 4.4.0.Alpha1 Reporter: Lucia Jelinkova At the moment there are 7 plugins related to Easymport. The plugin names very quite a lot - some refers to just Import framework, some to Easymport and some to smart import. Since most refer to "Easymport" I would suggest that format for all. Import framework (org.eclipse.e4.ui.importer) Easymport :: PDE support (org.eclipse.e4.ui.importer.pde) Easymport :: Java/JDT support (org.eclipse.e4.ui.importer.java) Easymport :: Java EE support (org.jboss.tools.playground.easymport.jee) Easymport :: Maven support (org.jboss.tools.playground.easymport.maven) Smart Import support for THyM (org.eclipse.thym.ui.importer) JavaScript support for smart import (org.eclipse.wst.jsdt.ui.importer) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21134) Move easymport plugins from playground component

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-21134: --------------------------------------- Summary: Move easymport plugins from playground component Key: JBIDE-21134 URL: https://issues.jboss.org/browse/JBIDE-21134 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: easymport Affects Versions: 4.4.0.Alpha1 Reporter: Lucia Jelinkova Easymport is in the default installation of JBDS so it might be time to move it from playground component? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21012: --------------------------------------------- Sounds good about JBIDE-21132 that was all I asked for - that we don't hide the *actual* issue that caused the publish to nexus to fail. i.e. lets fix/handle the cause of the problem instead of just the effect. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21133) Improve the 'Deploy Docker Image to Openshift' experience

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21133?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21133: ---------------------------------- Component/s: openshift > Improve the 'Deploy Docker Image to Openshift' experience > --------------------------------------------------------- > > Key: JBIDE-21133 > URL: https://issues.jboss.org/browse/JBIDE-21133 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Burr Sutter > Attachments: 00000568.png, Screenshot 2015-11-24 09.46.08.png > > > Deploy to Openshift from Docker Explorer (see screenshot below) > The resulting dialog (attached) > - promotes me for my Openshift - since I only have one connection - it should default to the one and only one connection > - Image: wants "repo", "name" and "tag" - well, with the PDK, this image is already "IN" OpenShift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20609: ---------------------------------------- Thanks [~fbricon] for the review {quote}clicking on the manage EA link shows a page with no content? I can literally do nothing. => what can we do to make it less confusing?{quote} What about calling the link "About Early Access"? What were you expecting to see when you clicked that link? {quote}apparently only AngularJS is EA on the 4.3.x branch, so I can't check what happens for connectors that only exist as EA. Are they still shown by default like arquillian in mickael's 1st video or did it change?{quote} It should be the same as on 1st video. {quote}I have literally no clue, before selecting one of the 2 angularjs versions, which one is EA, which one isn't. => can we add the category/certification back there?{quote} This certification label should be changed. It's not something on Central, but on discovery. It needs to be fixed in the catalog. But to emphasize Early-Access, I can make the pop-up have it with yellow background, like it happens in the Software page. However, I'm afraid it would bring too much attention to the EA one vs the regular one. WDYT? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Installer integration is currently not implemented yet. This will be the last piece. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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: ------------------------------------- https://github.com/jbosstools/jbosstools-base/pull/462 https://github.com/jbosstools/jbosstools-base/pull/467 PR's for master and maintenance respectively. > 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 > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20609: ------------------------------------- So I'm a bit confused by what's happening here: http://screencast.com/t/bTdLMu3Bj - clicking on the manage EA link shows a page with no content? I can literally do nothing. => what can we do to make it less confusing? - apparently only AngularJS is EA on the 4.3.x branch, so I can't check what happens for connectors that only exist as EA. Are they still shown by default like arquillian in mickael's 1st video or did it change? - I have literally no clue, before selecting one of the 2 angularjs versions, which one is EA, which one isn't. => can we add the category/certification back there? > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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