March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18723. ------------------------------------ Fix Version/s: 4.5.3.Final (was: LATER) Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18824) Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18824?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18824: ------------------------------------- Labels: openshift_v2 (was: ) > Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18824 > URL: https://issues.jboss.org/browse/JBIDE-18824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.1.Final > Reporter: Andre Dietisheim > Labels: openshift_v2 > Fix For: LATER > > Attachments: duplicate-application-actions.png > > > In JBIDE-11903 we added Start and Stop to the Explorer and Server adapter. In the server adapter we already have default items for start, stop and restart. We should remove our items from the OpenShift submenu and use the default actions instead: > !duplicate-application-actions.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18723) Binary deployment from current JBDS state

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18723?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18723: ------------------------------------- Labels: openshift_v2 (was: ) > Binary deployment from current JBDS state > ----------------------------------------- > > Key: JBIDE-18723 > URL: https://issues.jboss.org/browse/JBIDE-18723 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: William DeCoste > Labels: openshift_v2 > Fix For: LATER > > > Be able to create a deployment snapshot (tar.gz) from the current JBDS state (war, ear, standalone.xml, markers, etc) without having to download a snapshot from a pre-existing app/gear. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18438) OpenShift: can complete New App Wizard without selecting gear profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18438?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18438. ------------------------------------ Fix Version/s: 4.5.3.Final (was: LATER) Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > OpenShift: can complete New App Wizard without selecting gear profile > --------------------------------------------------------------------- > > Key: JBIDE-18438 > URL: https://issues.jboss.org/browse/JBIDE-18438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.5.3.Final > > > In New OpenShift Application wizard, on page where select 'Gear Profile' - this field is initially blank and user can leave it blank and still successfully complete the wizard. So it works. > But I don't think it is a good user experience. User should not be able to move to next page until there is a value in this field. Perhaps this field should have a value to start with instead of being blank based on the users account? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16921) Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16921?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-16921. ------------------------------------ > Application wizard: <NEW CONNECTION> is preselected after removing first connection (out of 2) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16921 > URL: https://issues.jboss.org/browse/JBIDE-16921 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > > ASSERT: Have a connection (e.g. seconduser(a)somewhere.xx) in OpenShift Explorer. > EXEC: Add another connection starting with a letter that's first in the alphabetical order (there is alphabetical order e.g. firstuser(a)somewhere.xx). It'll be listed first in the Explorer . > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application. > ASSERT: Wizard is opened. First connection is preselected. > EXEC: close wizard > EXEC: Remove first connection from OpenShift explorer. > EXEC: Open OpenShift application wizard via File->New->OpenShift->New Application > RESULT: Connection dialog is show with <NEW CONNECTION> preselected > EXPECTED RESULT: Connection dialog is shown with remaining connection preselected -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17974) Add contextual help to OpenShift modals

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17974?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-17974. -------------------------------------- Fix Version/s: 4.5.3.Final (was: LATER) Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Add contextual help to OpenShift modals > --------------------------------------- > > Key: JBIDE-17974 > URL: https://issues.jboss.org/browse/JBIDE-17974 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Andre Dietisheim > Labels: openshift_v2, openshift_v3, uxtest > Fix For: 4.5.3.Final > > > Many of the openshift modals do not provide contextual help that JBDS users expect throughout the application. > Create OpenShift Application modal: > Help button/Icon provided in bottom left of modal. Upon clicking, the help panel does not actually provide anything that helps the user understand what they need to do with the various screens throughout this wizard. > https://www.evernote.com/shard/s230/sh/3c712331-988c-4531-9b3b-b706973a9f... > The following OpenShift related dialogs do not provide a help icon/button at all and probably should: > - Configure OpenShift Markers (right click project -> OpenShift -> Configure Markers...) > - Domains (OpenShift Explorer pane -> right click OpenShift account -> Manage domains...) > - SSH Keys (OpenShift Explorer pane -> right click OpenShift account -> Manage SSH keys...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17974) Add contextual help to OpenShift modals

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17974?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-17974. ------------------------------------ > Add contextual help to OpenShift modals > --------------------------------------- > > Key: JBIDE-17974 > URL: https://issues.jboss.org/browse/JBIDE-17974 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Andre Dietisheim > Labels: openshift_v2, openshift_v3, uxtest > Fix For: 4.5.3.Final > > > Many of the openshift modals do not provide contextual help that JBDS users expect throughout the application. > Create OpenShift Application modal: > Help button/Icon provided in bottom left of modal. Upon clicking, the help panel does not actually provide anything that helps the user understand what they need to do with the various screens throughout this wizard. > https://www.evernote.com/shard/s230/sh/3c712331-988c-4531-9b3b-b706973a9f... > The following OpenShift related dialogs do not provide a help icon/button at all and probably should: > - Configure OpenShift Markers (right click project -> OpenShift -> Configure Markers...) > - Domains (OpenShift Explorer pane -> right click OpenShift account -> Manage domains...) > - SSH Keys (OpenShift Explorer pane -> right click OpenShift account -> Manage SSH keys...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17904) Server adapter: make .gitignore addition smarter and add comments to ignored files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17904?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-17904. ------------------------------------ > Server adapter: make .gitignore addition smarter and add comments to ignored files > ---------------------------------------------------------------------------------- > > Key: JBIDE-17904 > URL: https://issues.jboss.org/browse/JBIDE-17904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > currently *Any* openshift app creation/import we add the following blindly: > {code} > target > .settings/* > !.settings/.jsdtscope > .classpath > {code} > These does not make much sense for most apps besides java. > Can't we be a bit more intelligent about it ? > i.e. if the project is not a maven project, don't add 'target' > if project is not a java project do not add .classpath > And then I suggest adding comments to the .gitignore to make it clear what they do: > {code} > # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. > .settings/* > # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings > !.settings/.jsdtscope > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17672) Contribute changes to EGit commit/push operation so that we can nicely fit in our custom behaviour

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17672?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-17672. ------------------------------------ > Contribute changes to EGit commit/push operation so that we can nicely fit in our custom behaviour > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-17672 > URL: https://issues.jboss.org/browse/JBIDE-17672 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > > In JBIDE-10541 we made the EGit commit dialog come up before we publish the project to OpenShift. We did that by providing a modified copy of the EGit CommitUI class. We should contribute the changes that we did to CommitUI so that we can get rid of our copy. > When doing this we should also include streaming git responses to the Eclipse console as in Eclipse bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=418653 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17904) Server adapter: make .gitignore addition smarter and add comments to ignored files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17904?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-17904. -------------------------------------- Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Server adapter: make .gitignore addition smarter and add comments to ignored files > ---------------------------------------------------------------------------------- > > Key: JBIDE-17904 > URL: https://issues.jboss.org/browse/JBIDE-17904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > currently *Any* openshift app creation/import we add the following blindly: > {code} > target > .settings/* > !.settings/.jsdtscope > .classpath > {code} > These does not make much sense for most apps besides java. > Can't we be a bit more intelligent about it ? > i.e. if the project is not a maven project, don't add 'target' > if project is not a java project do not add .classpath > And then I suggest adding comments to the .gitignore to make it clear what they do: > {code} > # if you want *all* eclipse settings to be shared comment this out, otherwise leave in. > .settings/* > # keep .jsdtscope to share javascript validations exclusions to avoid too many false positive warnings > !.settings/.jsdtscope > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 March 2018