November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21015) New Application wizard: Add multi-tag filtering to templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21015?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21015. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-21015 > URL: https://issues.jboss.org/browse/JBIDE-21015 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20715?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20715. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21084) Connection/application wizard: reconnects if you get back and forth to the connection page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21084?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21084. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Connection/application wizard: reconnects if you get back and forth to the connection page > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21084 > URL: https://issues.jboss.org/browse/JBIDE-21084 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1 > > > What makes this necessary is the internal behaviour of the connection page being used when application- or import-wizard are launched from central or file-menu. It there is a delegating wizard page which invokes either v2 or v3 wizard based on the server type that the user is choosing. Behind the scenes I see the conn wizard connecting several times when launched from central/file-menu. The delegating wizard page needs to connect in the WizardPage#getNextPage(), a method that is also used in PageChangingListener(s) which it's using to determine the page change direction (forward or backward). > how to reproduce: > # EXEC: launch application wizard > # ASSERT: connection page shows up > # EXEC: select an existing or create a new connection > # EXEC: get to the next page > # EXEC: get back to the connection page and hit "Next" again > Result: > You see the progress bar coming up and getting to the 2nd page again after some delay caused by the the wizard re-connecting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20565) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20565?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20565. --------------------------------- Verified on 2015-11-26 for 4.3.x branch. > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-20565 > URL: https://issues.jboss.org/browse/JBIDE-20565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21071) Deleting a project with really long name that contains an application lists it in the explorer again

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21071?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21071. --------------------------------- Closed as a duplicate. > Deleting a project with really long name that contains an application lists it in the explorer again > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-21071 > URL: https://issues.jboss.org/browse/JBIDE-21071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > I have a project with display name of about 64000 characters. Then I add an application (I tried with eap-basic). Then when I delete the project, it suddenly reappears in Opeshift Explorer and even has context menu (and all the actions result in an error). > There is a simple workaround though - close and reopen the Openshift Explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20974) Project combo not populated regression

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20974?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20974. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Project combo not populated regression > -------------------------------------- > > Key: JBIDE-20974 > URL: https://issues.jboss.org/browse/JBIDE-20974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.Beta1 > > > Projects not correctly populated after fix to JBIDE-20714 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20714) OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20714?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20714. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > OpenShift Project combo is empty in Deploy docker image dialog if opened via context menu of a project > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20714 > URL: https://issues.jboss.org/browse/JBIDE-20714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: docker > Fix For: 4.3.1.Beta1 > > Attachments: deploy_image.png > > > Deploying a docker image to a OpenShift 3 server via context menu of a project in tooling is not possible because there is no project listed in the combo labeled "OpenShift Project". See attached screenshot: > !deploy_image.png! > If deploying a docker image dialog is opened via context menu of a connection projects are listed here. Issue is only with dialog opened via context menu of a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20978. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- JBIDE-11714 seem to have introduced skipRequirements and made the bad assumption download-plugins was only used for large testing dependencies. > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- [~mickael_istria] what do you mean we don't want skipRequirements to have another value ? it is used to avoid spending several minutes on downloading runtimes like EAP, AS, etc. again and again, right ? so its still relevant to be able to do -DskipRequirements=true *explicitly* btw. the root cause of this issue is this jira: https://issues.jboss.org/browse/JBIDE-11714 > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- 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