October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20715) Add validation for a project name in case of duplicates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20715?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20715: ----------------------------------- Assignee: Fred Bricon > Add validation for a project name in case of duplicates > ------------------------------------------------------- > > Key: JBIDE-20715 > URL: https://issues.jboss.org/browse/JBIDE-20715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.3.1.Beta1 > > > There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21001: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-jst/pull/546, https://github.com/jbosstools/jbosstools-jst/pull/547, https://github.com/jbosstools/jbosstools-discovery/pull/316, https://github.com/jbosstools/jbosstools-discovery/pull/315 (was: https://github.com/jbosstools/jbosstools-jst/pull/542, https://github.com/jbosstools/jbosstools-jst/pull/543, https://github.com/jbosstools/jbosstools-discovery/pull/316/files#diff-90..., https://github.com/jbosstools/jbosstools-discovery/pull/315) > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21001) Version of AngularJS in Central is older than version used in jbosstools-jst

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21001?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21001: ---------------------------------------- Thanks [~nickboldt] for the PRs. I rebased and merged the 544 (master) but now I'm actually not sure we should use the EA site there. I like the idea to use the real EA site to download angularJS plugins for our tests. If we have incorrect version of angular then the test won't build. But we use different EA TPs during development and production and we should the correct one all the time in the pom.xml. So this approach will require frequent updates of the pom.xml, won't it? I also created two more PRs https://github.com/jbosstools/jbosstools-jst/pull/546 https://github.com/jbosstools/jbosstools-jst/pull/547 to include angularjs plugins to the test environment. But we can't push them before https://github.com/jbosstools/jbosstools-discovery/pull/316 because currently the EA site has an old angularjs plugins 0.10.0 instead of the required 1.0 > Version of AngularJS in Central is older than version used in jbosstools-jst > ---------------------------------------------------------------------------- > > Key: JBIDE-21001 > URL: https://issues.jboss.org/browse/JBIDE-21001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Version of AngularJS used to build jbosstools-jst [1]: > * 1.0.0.201508312121 > [1] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > Version of AngularJS (angularjs-eclipse-feature) included in Early Access site [2] for JBT 4.3.0.Final / JBDS 9.0.0.GA: > * 0.10.0.201506182210 > [2] https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.3.x/... > So, we should put the newer AngularJS in the EA site. > But... it seems that the org.jboss.tools.jst.angularjs features & plugins don't actually depend on any of these: > {code} > org.eclipse.angularjs.ui_1.0.0.201508312121.jar > org.eclipse.angularjs.core_1.0.0.201508312121.jar > angularjs-eclipse-feature_1.0.0.201508312121.jar > {code} > So... other than the JBT/JBDS EA connectors, I can't see any reference to a specific version of angular, which begs the question: why does the jbosstools-jst build declare a dependency [3] on a specific update site mirror, such as [4] ? > [3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xm... > [4] http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21006) Connection wizard: switching to <New Connection> resets token but form is still valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21006?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21006: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: switching to <New Connection> resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-21006 > URL: https://issues.jboss.org/browse/JBIDE-21006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20507) Remove cursor from a retrieve token styled text

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20507?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20507: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.Beta1) > Remove cursor from a retrieve token styled text > ----------------------------------------------- > > Key: JBIDE-20507 > URL: https://issues.jboss.org/browse/JBIDE-20507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > > In a New Connection dialog there is a styled text with link "Enter a token or retrieve a new one." Problem is that styled text contains cursor. Cursor is shown on a position after clicking on the position inside the styled text. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21006) Connection wizard: switching to <New Connection> resets token but form is still valid

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21006: ---------------------------------------- Summary: Connection wizard: switching to <New Connection> resets token but form is still valid Key: JBIDE-21006 URL: https://issues.jboss.org/browse/JBIDE-21006 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.1.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21006) Connection wizard: switching to <New Connection> resets token but form is still valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21006?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21006: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Connection wizard: switching to <New Connection> resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-21006 > URL: https://issues.jboss.org/browse/JBIDE-21006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20978) Connection wizard: switching to <New Connection> resets token but form is still valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20978: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.x > Connection wizard: switching to <New Connection> resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20996) DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20996: ------------------------------------- The downloadruntimes api doesn't currently have any ability for dl-rt providers to actually provide feedback or custom logic =/ this would require some api extensions, and they'd have to be carefully considered so as not to just be a band-aid solution that fixes only one usecase. Such band-aids that add api for only one use-case tend to lead to cluttered code later on if repeated several times. > DV 6.2 is shipped withou EAP. Can we do something about it in context of Download Runtime wizard? > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-20996 > URL: https://issues.jboss.org/browse/JBIDE-20996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > > It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV 6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV 6.2 installator requires EAP 6.4 already present on user's machine (and the installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to exit wizard, install EAP 6.4 and then download (again) and install DV 6.2. > Is there anything we could do to make this workflow easier. > Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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: ------------------------------------- When using the terminal view to launch vagrant up, there are lots of errors if your environment variables include bash functions. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=469184 > 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 > > 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, 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 October 2015