[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:
-------------------------------------
Summary: Manage projects wizard: Cannot create any new project via OpenShift Projects dialog (was: Cannot create any new project via OpenShift Projects dialog)
> 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
[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:
-------------------------------------
Labels: application_wizard openshift_v3 (was: )
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20266) v3 Application wizard: should be able to manage projects in application wizard
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-20266:
----------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20265) Openshift: NPE appears while searching app from existing cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20265?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20265:
------------------------------------------
The details pannel is implemented in ApplicationTemplateDetailViews. The switching of detail panel occurrs on changes in the detailViewModel (a databinding observable value). The ApplicationTemplateDetailViews should switch to the empty view when there's no selection and detailViewModel gets "null" (that's how I would expect things to work. The switching of detail panes in done in AbstractStackedDetailViews#getViewFor(detailViewModel, IDetailView... detailViews)
> Openshift: NPE appears while searching app from existing cartridges
> -------------------------------------------------------------------
>
> Key: JBIDE-20265
> URL: https://issues.jboss.org/browse/JBIDE-20265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Konstantin Marmalyukov
> Priority: Minor
> Attachments: Screenshot 2015-07-15 13.09.08.png, Screenshot 2015-07-15 13.11.11.png
>
>
> NPE appears while searching necessary cartridges and selecting any of them while adding new symbols into search field
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-18672:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Beta2)
> cannot run ionic tabs (the default) app with cordovasim
> -------------------------------------------------------
>
> Key: JBIDE-18672
> URL: https://issues.jboss.org/browse/JBIDE-18672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: Mac OS X, JavaFX
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: upstream
> Fix For: 4.3.x
>
>
> run:
> ionic start ionic-demo
> import ionic-demo
> run as > cordova sim
> try use the app, click back.
> Two issues:
> 1) cordova sim complains about app.appexit not being supported
> 2) when trying to click do not show again I get the following in the cordovasim error log:
> Outstanding resource locks detected:
> ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total
> 84 total resources being managed
> average resource age is 15.1 frames
> 0 resources at maximum supported age (0.0%)
> 16 resources marked permanent (19.0%)
> 17 resources have had mismatched locks (20.2%)
> 17 resources locked (20.2%)
> 30 resources contain interesting data (35.7%)
> 0 resources disappeared (0.0%)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-20084.
-----------------------------------
Verified on nightly build.
> Import of jboss-sandbox-quickstarts
> -----------------------------------
>
> Key: JBIDE-20084
> URL: https://issues.jboss.org/browse/JBIDE-20084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta2
>
>
> I tried to import jboss-sandbox-quickstarts (from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git) and I found following issues with it
> - it takes quite a long time (app 3 and a half minutes to import 9 projects
> - during import it seems to be "stuck" for a while and the following exception is logged
> {code}
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:76)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:97)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$4.run(ProjectConfigurationManager.java:521)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:26)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.enableMavenNature(ProjectConfigurationManager.java:518)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:44)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:236)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:93)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 35 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 41 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 44 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19771.
-----------------------------------
Verified on nightly build.
> Improve Available detectors dialog
> ----------------------------------
>
> Key: JBIDE-19771
> URL: https://issues.jboss.org/browse/JBIDE-19771
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: available-detectors.png
>
>
> At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned.
> Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-20110.
-----------------------------------
The described scenario works on the nightly build.
> Batch Diagram silently closes Palette view
> ------------------------------------------
>
> Key: JBIDE-20110
> URL: https://issues.jboss.org/browse/JBIDE-20110
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
>
> Case 1:
> 1. Open Studio.
> 2. Open Palette.
> 3. Open some batch job xml file.
> FAIL: Palette is silently closed.
> The code that does it, is commented with
> {code}
> /**
> * This is a workaround that ensures that the flyout pallete (inner
> * composite inside the diagram editor) is used instead of a separate
> * pallete view. The separate pallete view does not work with the diagram
> * editor currently.
> */
> {code}
> This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.
> There is another case when this silent close does not work.
> Case 2:
> 1. Open some batch job xml file.
> 2. Open Palette view.
> 3. Test work with the separate palette.
> 4. Close/Restart Eclipse.
> 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
> 6. Test work with the separate palette.
> [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.
> Separate Palette view does not work with Batch diagram in this usecase:
> 1. Open batch job editor.
> 2. Open separate palette. Make sure that it works.
> 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'.
> 4. Make sure that Palette does not work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months