July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20120) Batch.xml references are not considered in editor

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20120?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20120. ----------------------------------- Verified on nightly build. > Batch.xml references are not considered in editor > ------------------------------------------------- > > Key: JBIDE-20120 > URL: https://issues.jboss.org/browse/JBIDE-20120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: job-listener-suggestions.png, job-listener-validation.png > > > I created 2 job listeners - one with \@Named annotation and one with reference in META-INF/batch.xml file. > When I invoke content assist, the one from batch.xml file is not referenced by its id but a full class name is suggested instead. > Also, when I type the id from the batch.xml file manually, it is not recognized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3482) JBDS contains reference to JBT TP site

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-3482?page=com.atlassian.jira.plugin.... ] Rastislav Wagner updated JBDS-3482: ----------------------------------- Attachment: JBTTP.png > JBDS contains reference to JBT TP site > -------------------------------------- > > Key: JBDS-3482 > URL: https://issues.jboss.org/browse/JBDS-3482 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform, updatesite > Affects Versions: 9.0.0.Beta1 > Reporter: Rastislav Wagner > Attachments: JBTTP.png > > > Try installing something (I tried Maven Seam, AngularJS) from central and JBT TP site will appear in Preferences -> Available Software Sites -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3482) JBDS contains reference to JBT TP site

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBDS-3482: -------------------------------------- Summary: JBDS contains reference to JBT TP site Key: JBDS-3482 URL: https://issues.jboss.org/browse/JBDS-3482 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central, target-platform, updatesite Affects Versions: 9.0.0.Beta1 Reporter: Rastislav Wagner Try installing something (I tried Maven Seam, AngularJS) from central and JBT TP site will appear in Preferences -> Available Software Sites -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19995) Diagram's layout is not preserved after workspace restart

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19995?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19995. ----------------------------------- Verified on nightly build. > Diagram's layout is not preserved after workspace restart > --------------------------------------------------------- > > Key: JBIDE-19995 > URL: https://issues.jboss.org/browse/JBIDE-19995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: after.png, before.png > > > When using batch editor (diagram tab) I want to be able to design and save my own created layout. At the moment, the layout is reset to some kind of defaults after workspace restart. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20119) Restartable attribute of job element should restrict values

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20119?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20119. ----------------------------------- Verified on nightly build > Restartable attribute of job element should restrict values > ----------------------------------------------------------- > > Key: JBIDE-20119 > URL: https://issues.jboss.org/browse/JBIDE-20119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > At the moment, there is no validation for restartable attribute of job element. According to specification, if specified, only "true" and "false" values are allowed. > _Specifies whether or not this job is restartable . It must specify true or false. This is an optional attribute. The default is true._ > Also, content assist should suggest these values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20136) Batch diagram generates references in <next> element

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20136?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-20136. ----------------------------------- Verified on nightly build. > Batch diagram generates references in <next> element > ---------------------------------------------------- > > Key: JBIDE-20136 > URL: https://issues.jboss.org/browse/JBIDE-20136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: diagram.png, editor.png > > > I created two steps in batch diagram editor without the ID specified and connected them with "Next on" element. In source view, the "to" values contained some unusual values like "StepNode#0" (see attachmets). > For "Next" element is the behaviour different - editor would not allow me to create connection at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19852?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19852: --------------------------------------- JBoss DV 6.2 will contain this: https://bugzilla.redhat.com/show_bug.cgi?id=1225450 So we should be able to test this around end of August. > Set default path for runtimes downloaded and installed via java -jar > -------------------------------------------------------------------- > > Key: JBIDE-19852 > URL: https://issues.jboss.org/browse/JBIDE-19852 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard. > The same for runtime detection after the download and installation is finished. > Example scenario: > 1. Select JBoss DV 6.1 for download&installation > 2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV) > 3. Click Finish - DV is downloaded and it's installer executed > ASSERT: /home/<user>/downloadedDV is default installation path in installer > 4. In the installer select different installation folder (for example /home/<user>/DV) > 5. Finish installer > ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20257: --------------------------------------- I'm not sure it's quite correct. If I log in via CLI on local openshift server with credentials demo:changeme, the same credentials used in tooling to connect to the localhost:8443, it works. > 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 > 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] (JBIDE-20257) 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 resolved JBIDE-20257. ----------------------------------- Resolution: Rejected This is not a bug. This means the user does not have permissions to create projects. It requires someone to use the CLI to explicitly grant the appropriate permissions. [~adietish] this error is manifested to the user as a warning dialog, but this was my concern: is it clear enough to the user that they do not have permissions? I'm not sure if it makes more sense to provide a different dialog to the user ourselves or ask for a better error message from the server. We could also update the rest client to provide a friendlier message but I feel like that would be the wrong solution. > 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 > 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] (JBIDE-19989) Improve id validation in batch diagram editor

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19989?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19989. ----------------------------------- Verified on nightly build. > Improve id validation in batch diagram editor > --------------------------------------------- > > Key: JBIDE-19989 > URL: https://issues.jboss.org/browse/JBIDE-19989 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: id-contains-spaces.png, id-is-empty.png > > > When I create a new step in Diagram tab, there is a validation if the id is empty. > !id-is-empty.png|thumbnail! > However, it allows me to enter "First step" which is not a valid id string but you can see the error only on the Source tab. > !id-contains-spaces.png|thumbnail! -- 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