October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-929?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-929. ----------------------------------- Verified with JBDS 9.1.0.GA with the following behavior - the fuse project starter is available no matter if the fuse tooling is installed or not - if the tooling is not present then it will be automatically installed - if the tooling is present then a new fuse project is created [~fbricon], thank you! > Fuse project starter is available in Central only if we check EarlyAccess > ------------------------------------------------------------------------- > > Key: JBTIS-929 > URL: https://issues.jboss.org/browse/JBTIS-929 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 9.0.2.GA > Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Fred Bricon > Fix For: 9.0.2.GA > > > Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4114) Remove cygwin from Mac installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4114?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4114: -------------------------------- Story Points: 3 > Remove cygwin from Mac installer > -------------------------------- > > Key: JBDS-4114 > URL: https://issues.jboss.org/browse/JBDS-4114 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > > There is no need for cygwin on mac since there is bash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Misha Ali resolved JBDS-3903. ----------------------------- Resolution: Done > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3903: --------------------------------- Thanks, Xavier! The update is available here: https://access.redhat.com/documentation/en/red-hat-development-suite/1.1/... Setting this issue to resolved. > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23385) IllegalArgumentException when creating new JSF project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23385?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23385: -------------------------------------- Assignee: Alexey Kazakov > IllegalArgumentException when creating new JSF project > ------------------------------------------------------ > > Key: JBIDE-23385 > URL: https://issues.jboss.org/browse/JBIDE-23385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.2.AM2 > Environment: Devstudio 10.2.0.AM2 > Reporter: Radim Hopp > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > This is not reproducible allways (~1 out of 10). > When creating new JSF project (File->New->Other.. -> JBoss Tools Web ->JSF Project), sometimes I get > {noformat:title=can not connect() without a document}java.lang.IllegalArgumentException: can not connect() without a document > at org.eclipse.wst.sse.core.internal.FileBufferModelManager.connect(FileBufferModelManager.java:506) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._incrCount(ModelManagerImpl.java:672) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1327) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1274) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.init(StructuredModelWrapper.java:64) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:600) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > and > {noformat:title=release was requested on a model that was not being managed} > org.jboss.tools.common.validation.JBTValidationException: release was requested on a model that was not being managed > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:171) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: release was requested on a model that was not being managed > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1941) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1796) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.releaseFromRead(AbstractStructuredModel.java:1026) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.releaseFromRead(DOMModelImpl.java:880) > at org.eclipse.wst.html.core.internal.document.DOMStyleModelImpl.releaseFromRead(DOMStyleModelImpl.java:44) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.dispose(StructuredModelWrapper.java:89) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:627) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23385) IllegalArgumentException when creating new JSF project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23385?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23385: ----------------------------------- Fix Version/s: 4.4.x > IllegalArgumentException when creating new JSF project > ------------------------------------------------------ > > Key: JBIDE-23385 > URL: https://issues.jboss.org/browse/JBIDE-23385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.2.AM2 > Environment: Devstudio 10.2.0.AM2 > Reporter: Radim Hopp > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > This is not reproducible allways (~1 out of 10). > When creating new JSF project (File->New->Other.. -> JBoss Tools Web ->JSF Project), sometimes I get > {noformat:title=can not connect() without a document}java.lang.IllegalArgumentException: can not connect() without a document > at org.eclipse.wst.sse.core.internal.FileBufferModelManager.connect(FileBufferModelManager.java:506) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._incrCount(ModelManagerImpl.java:672) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1327) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1274) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.init(StructuredModelWrapper.java:64) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:600) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > and > {noformat:title=release was requested on a model that was not being managed} > org.jboss.tools.common.validation.JBTValidationException: release was requested on a model that was not being managed > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:171) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: release was requested on a model that was not being managed > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1941) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1796) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.releaseFromRead(AbstractStructuredModel.java:1026) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.releaseFromRead(DOMModelImpl.java:880) > at org.eclipse.wst.html.core.internal.document.DOMStyleModelImpl.releaseFromRead(DOMStyleModelImpl.java:44) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.dispose(StructuredModelWrapper.java:89) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:627) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23383) HTML buttons with default formatting do not show text in embedded browser

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23383?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-23383: ---------------------------------------- This is probably because embedded XulRunner doesn't render HTML5 correctly. > HTML buttons with default formatting do not show text in embedded browser > ------------------------------------------------------------------------- > > Key: JBIDE-23383 > URL: https://issues.jboss.org/browse/JBIDE-23383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Fix For: LATER > > Attachments: no-button-text.png > > > See the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23383) HTML buttons with default formatting do not show text in embedded browser

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23383?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23383: ----------------------------------- Fix Version/s: LATER > HTML buttons with default formatting do not show text in embedded browser > ------------------------------------------------------------------------- > > Key: JBIDE-23383 > URL: https://issues.jboss.org/browse/JBIDE-23383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Fix For: LATER > > Attachments: no-button-text.png > > > See the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23383) HTML buttons with default formatting do not show text in embedded browser

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23383?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23383: ----------------------------------- Component/s: visual-page-editor-core > HTML buttons with default formatting do not show text in embedded browser > ------------------------------------------------------------------------- > > Key: JBIDE-23383 > URL: https://issues.jboss.org/browse/JBIDE-23383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Fix For: LATER > > Attachments: no-button-text.png > > > See the attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23327) Hibernate New and Noteworthy for 4.4.2.AM2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23327?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23327. ---------------------------------- Resolution: Rejected Closing the jira. [~koen.aers] if you have anything for N&N then please create a PR ASAP. > Hibernate New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23327 > URL: https://issues.jboss.org/browse/JBIDE-23327 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Hibernate4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016