July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20257) Manage projects wizard: Cannot create any new project via OpenShift Projects dialog

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20257: --------------------------------------- Speaking to Jordan LIggit: Users, if allowed by an admin can self provision docs using: https://docs.openshift.org/latest/rest_api/openshift_v1.html#v1-projectre... https://docs.openshift.org/latest/admin_guide/selfprovisioned_projects.html We need to modify the implementation to allow for this since currently only admins are allowed to create projects directly. > Manage projects wizard: Cannot create any new project via OpenShift Projects dialog > ----------------------------------------------------------------------------------- > > Key: JBIDE-20257 > URL: https://issues.jboss.org/browse/JBIDE-20257 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Labels: manage_projects_wizard > Fix For: 4.3.0.Beta2 > > > In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below: > {code} > Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope > com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169) > at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is happening also on locally running OpenShift v3 and also on staging v3 server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3264) Remove welcome/intro page

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3264: -------------------------------------- [~fbricon] Didn't you tell me that you were going to ask someone for UX advices today? Can you please also ask about that? > Remove welcome/intro page > ------------------------- > > Key: JBDS-3264 > URL: https://issues.jboss.org/browse/JBDS-3264 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 9.0.0.Beta2 > > > The welcome page for JBDS is really useless. It doesn't provide any value to the user. Moreover, it looks quite old-fashioned. > In such case, it would be better to remove it and prevent users from seeing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-20070: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Fix minor issues in RedDeer import > ---------------------------------- > > Key: JBIDE-20070 > URL: https://issues.jboss.org/browse/JBIDE-20070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: dialog.png > > > When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not). > List of minor issues: > - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there > - features has listed "Maven" but plugins and tests have "Maven, Java" > - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19715: ----------------------------------- Fix Version/s: LATER (was: 4.3.0.Beta2) > Get rid of "fullSite", stick with "repository" > ---------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: LATER > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19768: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.CR1 > > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19598: ----------------------------------- Fix Version/s: LATER (was: 4.3.0.Beta2) > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: LATER > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15339: ------------------------------------ With the completion of the mojo in JBIDE-19056 do we still need this? [~maxandersen] [~mickael_istria] WDYT? > Create version/change auditor/reporting tool > -------------------------------------------- > > Key: JBIDE-15339 > URL: https://issues.jboss.org/browse/JBIDE-15339 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: versioning > Fix For: 4.3.x > > > Plugin/Feature Version Auditor > Goal: be able to more easily see if a feature or plugin needs to be upversioned > Goal: be able to more easily see if a commit in github has been built into the jars in an update site > Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) > Output: generate a report of: > plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs > Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.) > May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch ) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20266) v3 Application wizard: should be able to manage projects in application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20266?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20266: ------------------------------------- Attachment: manage-domains-link.png > v3 Application wizard: should be able to manage projects in application wizard > ------------------------------------------------------------------------------ > > Key: JBIDE-20266 > URL: https://issues.jboss.org/browse/JBIDE-20266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: manage-domains-link.png > > > In the v3 application wizard one has to select the project to create the application in. As a user I should be able to manage (create, delete, etc.) projects when in the application wizard. > In v2 this is done via a link "manage domains" next to the combo to select the domain for the application. > !manage-domains-link.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20266) v3 Application wizard: should be able to manage projects in application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20266?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20266: ------------------------------------- Description: In the v3 application wizard one has to select the project to create the application in. As a user I should be able to manage (create, delete, etc.) projects when in the application wizard. In v2 this is done via a link "manage domains" next to the combo to select the domain for the application. !manage-domains-link.png! was: In the v3 application wizard one has to select the project to create the application in. As a user I should be able to manage (create, delete, etc.) projects when in the application wizard. In v2 this is done via a link "manage domains" next to the combo to select the domain for the application. > v3 Application wizard: should be able to manage projects in application wizard > ------------------------------------------------------------------------------ > > Key: JBIDE-20266 > URL: https://issues.jboss.org/browse/JBIDE-20266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > In the v3 application wizard one has to select the project to create the application in. As a user I should be able to manage (create, delete, etc.) projects when in the application wizard. > In v2 this is done via a link "manage domains" next to the combo to select the domain for the application. > !manage-domains-link.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20257) Manage projects wizard: Cannot create any new project via OpenShift Projects dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20257: ------------------------------------- Labels: manage_projects_wizard (was: ) > Manage projects wizard: Cannot create any new project via OpenShift Projects dialog > ----------------------------------------------------------------------------------- > > Key: JBIDE-20257 > URL: https://issues.jboss.org/browse/JBIDE-20257 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Labels: manage_projects_wizard > Fix For: 4.3.0.Beta2 > > > In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below: > {code} > Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope > com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169) > at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is happening also on locally running OpenShift v3 and also on staging v3 server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015