[JBoss JIRA] (JBIDE-13918) Build LiveReload with Tycho
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13918?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13918:
----------------------------------------
[~xcoulon]: Compilation is currently failing
{code}
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.17.0:compile (default-compile) on project org.jboss.tools.livereload: Compilation failure: Compilation failure:
[ERROR] /home/mistria/git/jbosstools-livereload/plugins/org.jboss.tools.livereload/src/org/jboss/tools/livereload/internal/util/WtpUtils.java:[10,0]
[ERROR] public class WTPUtils {
[ERROR] ^^^^^^^^
[ERROR] The public type WTPUtils must be defined in its own file
[ERROR] 1 problem (1 error)
[ERROR] -> [Help 1]
{code}
> Build LiveReload with Tycho
> ---------------------------
>
> Key: JBIDE-13918
> URL: https://issues.jboss.org/browse/JBIDE-13918
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: Build/Releng, livereload
> Affects Versions: 4.1.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Xavier Coulon
> Fix For: 4.1.0.Alpha2
>
>
> Add necessary pom files so livereload can be built with Tycho
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13914) Have a test run that runs test plugins for each component in a fully installed JBT
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13914?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13914:
----------------------------------------
Tycho doesn't understand what is an "Eclipse installation", it only understand p2 and can't alter installation. Trying to get it running inside Maven will result in putting some Ant or Groovy scripts in the pom.
I don't see any benefit in integrating it in Tycho or a pom.xml. What would be the added value?
> Have a test run that runs test plugins for each component in a fully installed JBT
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13914
> URL: https://issues.jboss.org/browse/JBIDE-13914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha2
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha2
>
>
> You said you had a way to run tests against existing install.
> Thus lets get this rolling by having a way to run a components test plugins and its included Test classes in a fully loaded JBoss Tools installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13924) Filter LiveReload messages on changed file extension
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13924:
-------------------------------------
Summary: Filter LiveReload messages on changed file extension
Key: JBIDE-13924
URL: https://issues.jboss.org/browse/JBIDE-13924
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: livereload
Affects Versions: 4.1.0.Alpha2
Reporter: Xavier Coulon
Fix For: 4.1.0.Alpha2
LiveReload refresh/reload commands should only be sentot browsers if the following types of file changed:
- htm/html
- css
- js
- images (png, gif, jpg, jpeg)
other types of file should be ignored
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-13818.
--------------------------------------
Resolution: Done
test failure is not occurring on DEVENV any more thus resolving
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13806) OpenShift console does not show the maven build logs anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13806?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13806:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an OpenShift application imported to your workspace along with the server adapter created.
# EXEC: change some file
# EXEC: in *Servers* view, choose its server adapter and pick *Publish* from the context menu.
Result:
The console with the push log is not opened
Expected result:
After the push/publish is finished, the console with the output should be shown to the user.
Workaround Description: use tail files before you push. You'll spot the changes that happen on the PaaS
> OpenShift console does not show the maven build logs anymore
> ------------------------------------------------------------
>
> Key: JBIDE-13806
> URL: https://issues.jboss.org/browse/JBIDE-13806
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
>
> The OpenShift tooling does not show the maven build logs after some changes were published on openshift.
> The workaround is to tail log files to see the app server activity (and see when the app is redeployed)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years