[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
[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
[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
[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
[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