[JBoss JIRA] (JBDS-4743) When saving an xhtml file, getting JSF error popup
by Fabi Yo (Jira)
Fabi Yo created JBDS-4743:
-----------------------------
Summary: When saving an xhtml file, getting JSF error popup
Key: JBDS-4743
URL: https://issues.jboss.org/browse/JBDS-4743
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: jsf
Affects Versions: 12.9.0.GA
Environment: JBDS 12.9 on macOS mojave
Reporter: Fabi Yo
Attachments: Schermafbeelding 2018-11-07 om 9.42.32 AM.png
I am working on an xhtml file which contains JSF tags. I can work normally in it. After a while (random) I get this popup saying:
'Refreshing JSF information about: ..... '
An internal error occured.
See more info in the picture in attachment
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4740) Add a build slave that is capable of building Flatpak versions of Eclipse products
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4740?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal edited comment on JBDS-4740 at 11/7/18 2:05 AM:
--------------------------------------------------------------
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set [1].
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label, or should it be, [~jrichter1]?
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
was (Author: odockal):
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set ().
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label, or should it be, [~jrichter1]?
> Add a build slave that is capable of building Flatpak versions of Eclipse products
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4740
> URL: https://issues.jboss.org/browse/JBDS-4740
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> I'm filing a Jira ticket as suggested in Mattermost.
> In order to explore shipping our Eclipse-based products as Flatpak applications, (initially SCL and maybe eventually also JBDS) I need a build slave for the Jenkins[1] that is capable of generating Flatpaks.
> The newly released RHEL 7.6 has a sufficiently new version of *flatpak* and *flatpak-builder* packages. Please also ensure there is *java-1.8.0-openjdk-devel* and a recent maven installed.
> Please consider adding such a builder.
> [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4740) Add a build slave that is capable of building Flatpak versions of Eclipse products
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4740?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal edited comment on JBDS-4740 at 11/7/18 2:05 AM:
--------------------------------------------------------------
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set [1].
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label, or should it be, [~jrichter1]?
[1] https://ci-rhos.centralci.eng.rdu2.redhat.com/dashboard/project/images
was (Author: odockal):
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set [1].
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label, or should it be, [~jrichter1]?
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
> Add a build slave that is capable of building Flatpak versions of Eclipse products
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4740
> URL: https://issues.jboss.org/browse/JBDS-4740
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> I'm filing a Jira ticket as suggested in Mattermost.
> In order to explore shipping our Eclipse-based products as Flatpak applications, (initially SCL and maybe eventually also JBDS) I need a build slave for the Jenkins[1] that is capable of generating Flatpaks.
> The newly released RHEL 7.6 has a sufficiently new version of *flatpak* and *flatpak-builder* packages. Please also ensure there is *java-1.8.0-openjdk-devel* and a recent maven installed.
> Please consider adding such a builder.
> [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4740) Add a build slave that is capable of building Flatpak versions of Eclipse products
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4740?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal edited comment on JBDS-4740 at 11/7/18 2:04 AM:
--------------------------------------------------------------
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set ().
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label, or should it be, [~jrichter1]?
was (Author: odockal):
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set.
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label.
> Add a build slave that is capable of building Flatpak versions of Eclipse products
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4740
> URL: https://issues.jboss.org/browse/JBDS-4740
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> I'm filing a Jira ticket as suggested in Mattermost.
> In order to explore shipping our Eclipse-based products as Flatpak applications, (initially SCL and maybe eventually also JBDS) I need a build slave for the Jenkins[1] that is capable of generating Flatpaks.
> The newly released RHEL 7.6 has a sufficiently new version of *flatpak* and *flatpak-builder* packages. Please also ensure there is *java-1.8.0-openjdk-devel* and a recent maven installed.
> Please consider adding such a builder.
> [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4740) Add a build slave that is capable of building Flatpak versions of Eclipse products
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4740?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal commented on JBDS-4740:
-------------------------------------
[~mat.booth] I have created a PR (linked). It got flatpak-builder installation and setting up flatpak repo.
Also as of your other requests, there is installed java-1.8.0-openjdk-devel by default (or in scripts already). But maven is usually configured by jenkins. So this should be probably solved as well from the jenkins side.
Please, check on rhel7-x64-jbds-flatpak image that is available in openstack images set.
Note that flatpak script can be added to provisioned snapshots using "flatpak" label, it is not part of jbds label.
> Add a build slave that is capable of building Flatpak versions of Eclipse products
> ----------------------------------------------------------------------------------
>
> Key: JBDS-4740
> URL: https://issues.jboss.org/browse/JBDS-4740
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build
> Reporter: Mat Booth
> Assignee: Ondrej Dockal
> Priority: Major
>
> I'm filing a Jira ticket as suggested in Mattermost.
> In order to explore shipping our Eclipse-based products as Flatpak applications, (initially SCL and maybe eventually also JBDS) I need a build slave for the Jenkins[1] that is capable of generating Flatpaks.
> The newly released RHEL 7.6 has a sufficiently new version of *flatpak* and *flatpak-builder* packages. Please also ensure there is *java-1.8.0-openjdk-devel* and a recent maven installed.
> Please consider adding such a builder.
> [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-26452 at 11/6/18 4:35 PM:
----------------------------------------------------------------
Requirements for proxy solution:
* Supports HTTP and HTTPS protocols
* Clear and configurable logging and other tools
* runs on linux
* Open Source solution
* License usable "in house" (can be use for profit = in enterprise environment)
* Project is be alive/maintained - can we maintain own fork?
* Community
* Code on github - preferably
* uses issue tracking system
Requirements for putting proxy into action:
* easy to deploy solution
* does not require user knowledge of proxy configuration - minimalist config
* can be updated at place
* RH certificate can be used
was (Author: odockal):
Requirements for proxy solution:
* Supports HTTP and HTTPS protocols
* Clear and configurable logging and other tools
* Open Source solution
* License usable "in house" (can be use for profit = in enterprise environment)
* Project is be alive/maintained - can we maintain own fork?
* Community
* Code on github - preferably
* uses issue tracking system
Requirements for putting proxy into action:
* easy to deploy solution
* does not require user knowledge of proxy configuration - minimalist config
* can be updated at place
* RH certificate can be used
> Explore existing proxy server set up solutions outside RH
> ---------------------------------------------------------
>
> Key: JBIDE-26452
> URL: https://issues.jboss.org/browse/JBIDE-26452
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Environment: Linux
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-26452 at 11/6/18 4:34 PM:
----------------------------------------------------------------
Requirements for proxy solution:
* Supports HTTP and HTTPS protocols
* Clear and configurable logging and other tools
* Open Source solution
* License usable "in house" (can be use for profit = in enterprise environment)
* Project is be alive/maintained - can we maintain own fork?
* Community
* Code on github - preferably
* uses issue tracking system
Requirements for putting proxy into action:
* easy to deploy solution
* does not require user knowledge of proxy configuration - minimalist config
* can be updated at place
* RH certificate can be used
was (Author: odockal):
Requirements for proxy solution:
* Supports HTTP and HTTPS protocols
* Clear and configurable logging and other tools
* Open Source solution
* License usable "in house" (can be use for profit = in enterprise environment)
* Project is be alive/maintained - can we maintain own fork?
* Community
* Code on github
Requirements for putting proxy into action:
* easy to deploy solution
* does not require user knowledge of proxy configuration - minimalist config
* can be updated at place
* RH certificate can be used
> Explore existing proxy server set up solutions outside RH
> ---------------------------------------------------------
>
> Key: JBIDE-26452
> URL: https://issues.jboss.org/browse/JBIDE-26452
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Environment: Linux
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months