July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20147) Batch Property mapping issue with reference

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20147?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20147: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Batch Property mapping issue with reference > ------------------------------------------- > > Key: JBIDE-20147 > URL: https://issues.jboss.org/browse/JBIDE-20147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Environment: Mars > Tools 4.3.0 Beta1 > Reporter: Cody Lerum > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > After upgrading to Mars and JBT I started getting a validation warning on my batch configuration > If I have the following I get an error {{Property "INVOICE_JOB_ID" is not found in artifact "invoiceCreateBatchlet" and is not used in other properties.}} > {code} > @Inject > @BatchProperty(name = InvoiceCreatePartitionMapper.INVOICE_JOB_ID_KEY) > private String invoiceJobId; > {code} > In a different class > {code} > public static final String INVOICE_JOB_ID_KEY = "INVOICE_JOB_ID"; > {code} > However if have the following there is no warning. > {code} > @Inject > @BatchProperty(name = "INVOICE_JOB_ID") > private String invoiceJobId; > {code} > It appears that the validation logic cannot follow the reference -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20264: ----------------------------------------------- I cannot reproduce it in Linux. > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20264: -------------------------------------- Assignee: Viacheslav Kabanovich > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20264: ----------------------------------- Fix Version/s: 4.3.0.CR1 > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[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 edited comment on JBIDE-20257 at 7/15/15 10:48 AM: ----------------------------------------------------------------- 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 cluster admins are allowed to create projects directly. was (Author: jcantrill): 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, 10 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3264: ----------------------------------- [~crobson]: your thoughts? > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20283) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20283: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Webservices] Key: JBIDE-20283 URL: https://issues.jboss.org/browse/JBIDE-20283 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: webservices Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Webservices]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20284) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20284: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian] Key: JBIDE-20284 URL: https://issues.jboss.org/browse/JBIDE-20284 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: arquillian Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Arquillian]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20285) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Freemarker]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20285: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Freemarker] Key: JBIDE-20285 URL: https://issues.jboss.org/browse/JBIDE-20285 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: freemarker Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Freemarker]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20286) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20286: ---------------------------------- Summary: For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Central] Key: JBIDE-20286 URL: https://issues.jboss.org/browse/JBIDE-20286 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central, maven, project-examples Reporter: Nick Boldt Priority: Blocker For JBIDE 4.3.0.Beta2 [Central]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.3.0.Beta2x git push origin jbosstools-4.3.0.Beta2x {code} 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.CR1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran 4. Close (do not resolve) this JIRA when done. 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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