[JBoss JIRA] (JBDS-3861) Can't donwload some example projects from central
by Jan Richter (JIRA)
Jan Richter created JBDS-3861:
---------------------------------
Summary: Can't donwload some example projects from central
Key: JBDS-3861
URL: https://issues.jboss.org/browse/JBDS-3861
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 10.0.0.Alpha1
Environment: Devstudio 10.0.0.Alpha1-v20160427-0539-B5240
Reporter: Jan Richter
Trying to download some example projects from central simply opens a progress dialog, which quickly disappears and nothing happens. So far I found it happening with HTML5 project, AngularJS forge and Java EE Web Project - but there might be more.
Note that in JBT master they all work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21117) Livereload tests fail after migration to jetty 9.3.5
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21117?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21117.
-------------------------------
The issue looks long gone now, closing.
> Livereload tests fail after migration to jetty 9.3.5
> ----------------------------------------------------
>
> Key: JBIDE-21117
> URL: https://issues.jboss.org/browse/JBIDE-21117
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> {code}Results :
> Failed tests:
> LiveReloadServerTestCase.shouldForwardRequestOnProxiedServerWithScriptInjectionAndDefaultCharset:845
> Expecting:
> <"">
> to contain:
> <"Hello, World!">
> LiveReloadServerTestCase.shouldForwardRequestOnProxiedServerWithScriptInjectionAndCustomCharset:872
> Expecting:
> <"">
> to contain:
> <"Hello, World!">
> Tests run: 97, Failures: 2, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] jbosstools-livereload .............................. SUCCESS [ 0.286 s]
> [INFO] livereload.plugins ................................. SUCCESS [ 0.008 s]
> [INFO] org.jboss.tools.livereload.core .................... SUCCESS [ 4.714 s]
> [INFO] org.jboss.tools.livereload.ui ...................... SUCCESS [ 0.620 s]
> [INFO] livereload.tests ................................... SUCCESS [ 0.007 s]
> [INFO] org.jboss.tools.livereload.test .................... FAILURE [04:39 min]
> [INFO] livereload.features ................................ SKIPPED
> [INFO] org.jboss.tools.livereload.feature ................. SKIPPED
> [INFO] org.jboss.tools.livereload.test.feature ............ SKIPPED
> [INFO] livereload.site .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 06:09 min
> [INFO] Finished at: 2015-11-20T09:21:23-08:00
> [INFO] Final Memory: 117M/2226M
> [INFO] ------------------------------------------------------------------------{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21485) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21485?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21485.
-------------------------------
Verified in 4.4.0.Alpha1 with WST 1.9.0.Alpha1 B850.
> webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21485
> URL: https://issues.jboss.org/browse/JBIDE-21485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules.
> The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later.
> The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb.
> See also: https://issues.jboss.org/browse/JBIDE-20802
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21888) Pod is not created when docker image is deployed to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21888?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21888.
---------------------------------
Verified in JBDS 10.0.0.Alpha1 B5240.
> Pod is not created when docker image is deployed to OpenShift
> -------------------------------------------------------------
>
> Key: JBIDE-21888
> URL: https://issues.jboss.org/browse/JBIDE-21888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months