[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-23294.
---------------------------------
CDK 2.x is not supported any more, resolution of this jira is rejected and we are not going to fix anything in CDK 2.x tooling, thus, I am closing this.
> Console is badly rendering some characters when starting Container Development Environment
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-23294
> URL: https://issues.jboss.org/browse/JBIDE-23294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.3.Final
>
> Attachments: screenshot-1.png
>
>
> - there is a special character before the [KProgress
> - what means K for KProgress?
> {noformat}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> [KProgress: 10%
> [KProgress: 20%
> [KProgress: 90%
> [K==> default: Matching MAC address for NAT networking...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-13407.
---------------------------------
Closing.
> Jar signing for JBT plugins/features
> ------------------------------------
>
> Key: JBIDE-13407
> URL: https://issues.jboss.org/browse/JBIDE-13407
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, updatesite
> Affects Versions: 3.3.2.Final, 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.5.3.AM3
>
> Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, dialog_do-you-trust-these-certs.png, jbds-signed-plugins.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.png
>
>
> Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product.
> Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25847) Fuse Tools New and Noteworthy for 4.5.3.Final
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25847?page=com.atlassian.jira.plugi... ]
Tomáš Sedmík closed JBIDE-25847.
--------------------------------
verified with master branch
> Fuse Tools New and Noteworthy for 4.5.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-25847
> URL: https://issues.jboss.org/browse/JBIDE-25847
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: fusetools, fusetools-extras
> Reporter: Jeff MAURY
> Assignee: Aurélien Pupier
> Priority: Critical
> Labels: task
> Fix For: 4.5.3.Final
>
>
> Lars Heinemann,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Fuse Tools 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 Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Fuse Tools 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... {code}JBIDE-25839 #comment Create N&N for Fuse Tools 4.5.3.Final #close{code}... 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 Fuse Tools for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.5.3.Final since the AM3 release of Fuse Tools, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.3.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25700:
------------------------------------------
[~rhuss] this is my impression, too, could be a prob in rsync even. Thanks for getting back, helping to figure out how to fix this!
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25700 at 4/16/18 4:44 AM:
-------------------------------------------------------------------
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the --no-perms=true):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
And then, i checked for further options (like --no-o or --no-g) but those are not supported by oc unfortunately.
was (Author: adietish):
[~rhuss] we do run oc rsync using --no-perms (see comment above). Here's the exact command that we run (notice the --no-perms=true):
{code}
/usr/local/Cellar/openshift-cli/3.7.0/bin/oc rsync --token=<TOKEN> --server=https://open.paas.redhat.com -n camel-ose-springboot-xml --exclude=.git --exclude=.npm --no-perms=true --insecure-skip-tls-verify=true <LOCAL FILESYSTEM> <POD>:/deployments/BOOT-INF/classes/{code}
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Roland Huß (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Roland Huß commented on JBIDE-25700:
------------------------------------
Sorry, I haven't follow the whole discussion so I missed that you already tried --no-perms=true
But then it looks for me like an issue of oc itself, because I couldn't explain it otherwise that it would do a 'chgrp' even when --no-perms=true is given. would be probably woth to ask on #openshift-dev or via a GitHub link in https://github.com/openshift/origin
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.5.x
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months