[JBoss JIRA] (JBIDE-21049) Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21049?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21049.
---------------------------------
Verified in devstudio 10.0.0.GA B5510. Both schemas are now included in the plugin and listed under Preferences -> XML -> XML Catalog.
> Add "wildfly-messaging-activemq-deployment_1_0.xsd" to xml catalog
> ------------------------------------------------------------------
>
> Key: JBIDE-21049
> URL: https://issues.jboss.org/browse/JBIDE-21049
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> WildFly 10 introduced a new schema "wildfly-messaging-activemq-deployment_1_0.xsd" for configuration of e.g. an ActiveMQ queue as part of a deployable archive, e.g. an EAR file (a file with the extension "...-jms.xml").
> This schema file is missing in the XSD catalog.
> Here is a sample xml instance:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <messaging-deployment xmlns="urn:jboss:messaging-activemq-deployment:1.0">
> <server>
> <jms-destinations>
> <jms-queue name="MessageBeanQueue">
> <entry name="jms/queue/MessageBeanQueue"/>
> </jms-queue>
> </jms-destinations>
> </server>
> </messaging-deployment>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20798) log filling up with "unable to retrieve a list of remote deployments"
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20798?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20798.
---------------------------------
I'm still not seeing this in devstudio 10.0.0.GA B5510, so closing.
> log filling up with "unable to retrieve a list of remote deployments"
> ---------------------------------------------------------------------
>
> Key: JBIDE-20798
> URL: https://issues.jboss.org/browse/JBIDE-20798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
> Attachments: Java_EE_-_JBoss_EAP_6_4_-_Eclipse_-__Users_max_Documents_workspace-deploy-demo.png
>
>
> when starting/stopping EAP 6.4 server I 'm getting my logs filled with:
> {code}
> Unable to retrieve a list of remote deployment scanners
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [
> {"subsystem" => "deployment-scanner"},
> {"scanner" => "*"}
> ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:236)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:234)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:122)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDefaultDeploymentScanner(AS7DeploymentScannerUtility.java:212)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadDefaultScannerFromServer(LocalJBoss7DeploymentScannerAdditions.java:148)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersAdded(LocalJBoss7DeploymentScannerAdditions.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.updateDeploymentScanners(AbstractDeploymentScannerAdditions.java:61)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions$1.run(AbstractDeploymentScannerAdditions.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [
> {"subsystem" => "deployment-scanner"},
> {"scanner" => "*"}
> ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
> ... 15 more
> {code}
> since these are done during startup and it is possible to see in the error then I would expect we did not log this by default for this case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-654:
-------------------------------------------
please remember that the whole handling of runtime detection is actually done by devstudio *after* install by telling it what folder to scan.
Thus lets not change any root folder, but of course have a proper named fuse runtime folder following the naming conventions used for jboss runtimes.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-654:
-------------------------------------------
[~leacu] no - please do not introduce differnet runtime folder names. it is very intentional that we have a *single* runtime folder where in there can be many.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3936:
-------------------------------------------
[~james.cobb] just read all your comment now and please be aware this was not something Alexey or I approved on alone - [~crobson] worked with Brand on this for us based on request on Harry and Todd's requests to have a uniform red hat developer branding.
I've asked [~crobson] to follow up here because she knows the details on how and what was discussed.
> devstudio.exe has eclipse icon
> ------------------------------
>
> Key: JBDS-3936
> URL: https://issues.jboss.org/browse/JBDS-3936
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 10.0.0.GA
>
> Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png
>
>
> [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon.
> http://i.imgur.com/ZKjeJGC.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22580) Cannot push already tagged image to docker registry
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22580:
-------------------------------------
Summary: Cannot push already tagged image to docker registry
Key: JBIDE-22580
URL: https://issues.jboss.org/browse/JBIDE-22580
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Final
Reporter: Marián Labuda
There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace
{code}Failed to push the selected Docker image into OpenShift registry
org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083)
at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22580) Cannot push already tagged image to docker registry
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22580:
----------------------------------
Labels: docker openshift_v3 (was: )
> Cannot push already tagged image to docker registry
> ---------------------------------------------------
>
> Key: JBIDE-22580
> URL: https://issues.jboss.org/browse/JBIDE-22580
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace
> {code}Failed to push the selected Docker image into OpenShift registry
> org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ]
Jan Richter resolved JBDS-3787.
-------------------------------
Resolution: Done
Disregard the last comment, the problem was on my side.
> Installer - Installation of each component should be optional
> -------------------------------------------------------------
>
> Key: JBDS-3787
> URL: https://issues.jboss.org/browse/JBDS-3787
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc, new_and_notworthy, user-docs
> Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png
>
>
> Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-3924:
----------------------------
Environment:
Fedora 22 (fixed, not 23)
Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
was:
Fedora 23
Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 22 (fixed, not 23)
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 10.x
>
> Attachments: devstudio10install.png, incomplete_install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3924:
---------------------------------
Sorry, I just confirmed, this is in the f22 machine, not the f23 one. I'll
update the environment info in the bug as well.
Thanks,
Misha Husnain Ali
Technical Writer 2, CCS Brisbane
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> jvm: java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 10.x
>
> Attachments: devstudio10install.png, incomplete_install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
