June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17440) Application wizard: Import application through Configure context menu has empty remote name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17440?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17440: ------------------------------------------ interesting enough, this issue wont happen if you start from new/import wizard, it only occurrs if you launch the wizard via configure in the project context menu > Application wizard: Import application through Configure context menu has empty remote name > ------------------------------------------------------------------------------------------- > > Key: JBIDE-17440 > URL: https://issues.jboss.org/browse/JBIDE-17440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Fix For: 4.2.0.Beta3 > > > While importing application through context menu of a project via Configure item (implemented as part of JBIDE-10546) on last wizard page is remote name text field for OpenShift application empty although checkbox for using default remote name is checked. It should be filled with default value "openshift" or any other. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17440) Application wizard: Import application through Configure context menu has empty remote name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17440?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-17440 at 6/27/14 10:39 AM: -------------------------------------------------------------------- interesting enough, was (Author: adietish): interesting enough, this issue wont happen if you start from new/import wizard, it only occurrs if you launch the wizard via configure in the project context menu > Application wizard: Import application through Configure context menu has empty remote name > ------------------------------------------------------------------------------------------- > > Key: JBIDE-17440 > URL: https://issues.jboss.org/browse/JBIDE-17440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Marián Labuda > Fix For: 4.2.0.Beta3 > > > While importing application through context menu of a project via Configure item (implemented as part of JBIDE-10546) on last wizard page is remote name text field for OpenShift application empty although checkbox for using default remote name is checked. It should be filled with default value "openshift" or any other. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2777: ----------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial,User Experience (was: Documentation (Ref Guide, User Guide, etc.)) > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, could-not-find-webconsole.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2777: ----------------------------------- Attachment: could-not-find-webconsole.png > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, could-not-find-webconsole.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-2777 at 6/27/14 10:18 AM: ------------------------------------------------------------------ I am now checking both url variants. We now have a link in the wizard page where one can edit domains: !edit-domain-link-validated.png! We check their availability once the user click the link. If none of the url variants seem valid we'll show an error to the user, telling it where he can normally find the web page we were looking for. Clicking on the link (in the dialog) will open a browser and allow the user to edit the url manually. !could-not-find-webconsole.png! was (Author: adietish): I am now checking both url variants. We now have a link in the wizard page where one can edit domains: !edit-domain-link-validated.png! We check their availability once the user click the link. If none of the url variants seem valid we'll show an error to the user, telling it where he can normally find the web page we were looking for. Clicking on the link (in the dialog) will open a browser and allow the user to edit the url manually. !could-not-find-webconsole.png! > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, could-not-find-webconsole.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-2777 at 6/27/14 10:17 AM: ------------------------------------------------------------------ I am now checking both url variants. We now have a link in the wizard page where one can edit domains: !edit-domain-link-validated.png! We check their availability once the user click the link. If none of the url variants seem valid we'll show an error to the user, telling it where he can normally find the web page we were looking for. Clicking on the link (in the dialog) will open a browser and allow the user to edit the url manually. !could-not-find-webconsole.png! was (Author: adietish): I am now checking both url variants. The link in the domain wizard is initially telling you that the link is being checked: !edit-domain-check-link-availability.png! Once the check occurred and the page was found the link gets enabled: !edit-domain-link-validated.png! > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2777: ----------------------------------- Attachment: (was: edit-domain-check-link-availability.png) > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, domain-wizard-edit-members.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2777: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/433 (was: https://github.com/jbosstools/jbosstools-openshift/pull/432) > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, domain-wizard-edit-members.png, edit-domain-check-link-availability.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2777: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/432 (was: https://github.com/jbosstools/jbosstools-openshift/pull/431) > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.Beta3 > > Attachments: application-wizard-manage-domains.png, domain-wizard-edit-members.png, edit-domain-check-link-availability.png, edit-domain-link-validated.png, edit-domain-members.png, explorer-edit-domain.png, explorer-manage-domains.png > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17241) Forge should use the m2e settings.xml during Maven artifact resolution

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17241?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-17241: ----------------------------------------- I implemented by reading it from Preferences everytime Forge is invoked > Forge should use the m2e settings.xml during Maven artifact resolution > ---------------------------------------------------------------------- > > Key: JBIDE-17241 > URL: https://issues.jboss.org/browse/JBIDE-17241 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > Fix For: 4.2.0.Beta3 > > > When I have a project like TicketMonster or any of the WFK examples in my workspace, I configure m2e to use a separate settings.xml file (say ~/.m2/contributor-settings.xml or ~/.m2/redhat-repos.xml) which point to the RedHat enterprise repositories or other repos. My usual settings.xml file lacks this. > Forge uses the ~/.m2/settings.xml file by default, even though the Eclipse workspace uses a different one. From the point of view of end-users this results in weird behavior in Forge. For example, Forge facets are not activated correctly because the Maven artifacts in the Red Hat enterprise repo could not be found. > It requires the user to modify the content of ~/.m2/settings.xml instead of just pointing to a different one, which is a bit unreasonable of Forge, given the current capabilites of m2e. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 June 2014