[JBoss JIRA] (JBIDE-24354) Base New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24354?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24354:
-------------------------------
Fix Version/s: 4.4.4.Final
> Base New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24354
> URL: https://issues.jboss.org/browse/JBIDE-24354
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common, foundation, usage
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Base 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 Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Base 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-24345 #comment Create N&N for Base 4.4.4.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 Base for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Base, 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.4.4.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.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24355) OpenShift New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24355?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24355:
-------------------------------
Fix Version/s: 4.4.4.Final
> OpenShift New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24355
> URL: https://issues.jboss.org/browse/JBIDE-24355
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdk, openshift
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Andre Dietisheim,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed OpenShift 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 OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for OpenShift 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-24345 #comment Create N&N for OpenShift 4.4.4.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 OpenShift for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of OpenShift, 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.4.4.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.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24357) JSF New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24357?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24357:
-------------------------------
Fix Version/s: 4.4.4.Final
> JSF New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24357
> URL: https://issues.jboss.org/browse/JBIDE-24357
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsf, jsp/jsf/xml/html-source-editing
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.4.Final
>
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed JSF 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 JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for JSF 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-24345 #comment Create N&N for JSF 4.4.4.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 JSF for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of JSF, 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.4.4.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.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ]
Dmitrii Bocharov resolved JBDS-4070.
------------------------------------
Resolution: Duplicate
Resolving this issue as duplicate of https://issues.jboss.org/browse/JBIDE-24322. Please, find the fix and other details there.
> DevStudio / external OpenShift fails deployment
> -----------------------------------------------
>
> Key: JBDS-4070
> URL: https://issues.jboss.org/browse/JBDS-4070
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.1.0.GA
> Environment: DevStudio as used with an external OpenShift
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Labels: openshift_v3
> Fix For: 10.4.0.GA
>
> Attachments: OSDeployRecreate.docx, eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png
>
>
> If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result.
> The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports:
> 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ]
Dmitrii Bocharov updated JBDS-4070:
-----------------------------------
Steps to Reproduce:
0) Windows operating system
1) Remove rsync from the PATH. To check if rsync cannot be detected, simply try to run rsync command in the cmd cli. You can do it via multiple ways: a) go to the installation directory of the sygwin -> to the bin directory -> find there rsync binary and rename it. b) if you have cwRsync installed separately, then uninstall it, or also simply remove it. Finally, command which rsync must output "which: no rsync in <PATH env var>".
2) Create openshift connection in Openshift Explorer
3) create any eap application, e.g. jboss-eap70-openshift
4) wait till pod is built and run.
5) create server adapter
6) make changes in the sources and save them.
Publish will happen. If you continue to do publishes, it will lead to the nested directories.
was:
- Configure a Server Adapter to point to an external OpenShift
- Develop an EAP application
- Try to deploy the .ear/.war/.jar application to EAP as it runs on the external OpenShift
Workaround Description: Make sure to have rsync installed and added to the PATH env variable
Workaround: Workaround Exists
> DevStudio / external OpenShift fails deployment
> -----------------------------------------------
>
> Key: JBDS-4070
> URL: https://issues.jboss.org/browse/JBDS-4070
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.1.0.GA
> Environment: DevStudio as used with an external OpenShift
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Labels: openshift_v3
> Fix For: 10.4.0.GA
>
> Attachments: OSDeployRecreate.docx, eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png
>
>
> If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result.
> The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports:
> 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months