[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ]
nimo stephan commented on JBIDE-26740:
--------------------------------------
I don't think that jboss tools can do any magic to speed up the hot deployments like that with WAD or liberty.
So yes, you can close this issue. Thanks!
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.redhat.com/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Assignee: Robert Stryker
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27084) Add proxy support for odo based explorer
by Jeff MAURY (Jira)
Jeff MAURY created JBIDE-27084:
----------------------------------
Summary: Add proxy support for odo based explorer
Key: JBIDE-27084
URL: https://issues.redhat.com/browse/JBIDE-27084
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.14.0.Final
Reporter: Jeff MAURY
Fix For: 4.15.0.AM1
We should add proxy support for the odo based explorer. This requires to set up HTTPS_PROXY env variable when launching odo if proxy is required for the cluster url.
I would recommand the following changes:
* OpenShiftClient should be now private to the OdoCli
* Modify Odo interface so as to remove the OpenShiftClient from the parameters
* Add a new reset method to Odo interface that will be called when the context is reset or add a new OdoFactory that will be called when context is reset. We will allocate the OpenShiftClient here and compute the HTTP_PROXY env variable if proxy is required for this cluster
* Modify odo launch calls so as to pass this env var each time odo is launched
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-20346) "Jts" and "jts-distributed-crash-rec" quickstarts (EAP 6.4) contains XML validation errors
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-20346?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-20346.
---------------------------------
Fix Version/s: 4.14.0.Final
(was: 4.15.x)
Resolution: Out of Date
Closign as Out Of Date, Quickstarts in central were updated to 7.0 some time ago, so this is not relevant anymore.
> "Jts" and "jts-distributed-crash-rec" quickstarts (EAP 6.4) contains XML validation errors
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.redhat.com/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.14.0.Final
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ]
Josef Kopriva commented on JBIDE-26740:
---------------------------------------
[~nimo22] np, I am glad it works. Can I close this JIRA, or do you have any other issues/comments?
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.redhat.com/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Assignee: Robert Stryker
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27081) New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)
by Zbyněk Červinka (Jira)
[ https://issues.redhat.com/browse/JBIDE-27081?page=com.atlassian.jira.plug... ]
Zbyněk Červinka updated JBIDE-27081:
------------------------------------
Fix Version/s: 4.15.x
(was: 4.15.0.AM1)
> New JSF project with the 2.3 JSF version could not be build (WildFly 18 Runtime is used; on both Javas 8 and 11)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27081
> URL: https://issues.redhat.com/browse/JBIDE-27081
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.14.0.Final
> Reporter: Zbyněk Červinka
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.15.x
>
>
> {code:java}
> ERROR] Failed to execute goal on project project123: Could not resolve dependencies for project project123:project123:war:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1, org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1, org.infinispan:infinispan-core:jar:4.2.1.FINAL: Failure to find org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ]
nimo stephan commented on JBIDE-26740:
--------------------------------------
Yes, thanks. It works. The hot deployment with that approach needs approx. 30-40 seconds..
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.redhat.com/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Assignee: Robert Stryker
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month