[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13843:
---------------------------------------
[~nickboldt] I have a related version. I got worried that the missing org.junit4 in M6 might break our RedDeer build.
We define these two p2 repos:
http://download.eclipse.org/releases/kepler - supposedly this is the latest kepler milestone
http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site - this contains SWTBot 2.0.5
So I thought: OK, the kepler repo now contains M6 -> no org.junit4 -> failed dependency of SWTBot 2.0.5.
But actually not. It seems that the kepler repo is an aggregate repo of all kepler milestones so far:
{code}
[INFO] Scanning for projects...
[INFO] Computing target platform for MavenProject: org.jboss.reddeer:org.jboss.reddeer.swt:0.2.0-SNAPSHOT @ /Users/rasp/git/reddeer/org.jboss.reddeer.swt/pom.xml
[INFO] Fetching p2.index (0B of 96B at 0B/s) from http://download.eclipse.org/releases/kepler/
[INFO] Fetching p2.index (128B of 96B at 0B/s) from http://download.eclipse.org/releases/kepler/
[INFO] 1 operation remaining.
[INFO] Adding repository http://download.eclipse.org/releases/kepler
[INFO] Fetching p2.index (0B of 244B at 0B/s) from http://download.eclipse.org/releases/kepler/201303220900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 244B at 0B/s) from http://download.eclipse.org/releases/kepler/201303220900/
[INFO] Fetching p2.index (0B of 245B at 0B/s) from http://download.eclipse.org/releases/kepler/201302080900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 245B at 0B/s) from http://download.eclipse.org/releases/kepler/201302080900/
[INFO] Fetching p2.index (0B of 243B at 0B/s) from http://download.eclipse.org/releases/kepler/201212210900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 243B at 0B/s) from http://download.eclipse.org/releases/kepler/201212210900/
[INFO] Fetching p2.index (0B of 92B at 0B/s) from http://download.eclipse.org/technology/epp/packages/kepler/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (116B of 92B at 0B/s) from http://download.eclipse.org/technology/epp/packages/kepler/
[INFO] Fetching p2.index (0B of 96B at 0B/s) from http://download.eclipse.org/releases/kepler/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (128B of 96B at 0B/s) from http://download.eclipse.org/releases/kepler/
[INFO] Adding repository http://download.eclipse.org/releases/kepler
[INFO] Fetching p2.index (0B of 244B at 0B/s) from http://download.eclipse.org/releases/kepler/201303220900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 244B at 0B/s) from http://download.eclipse.org/releases/kepler/201303220900/
[INFO] Fetching p2.index (0B of 245B at 0B/s) from http://download.eclipse.org/releases/kepler/201302080900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 245B at 0B/s) from http://download.eclipse.org/releases/kepler/201302080900/
[INFO] Fetching p2.index (0B of 243B at 0B/s) from http://download.eclipse.org/releases/kepler/201212210900/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (365B of 243B at 0B/s) from http://download.eclipse.org/releases/kepler/201212210900/
[INFO] Fetching p2.index (0B of 92B at 0B/s) from http://download.eclipse.org/technology/epp/packages/kepler/
[INFO] 1 operation remaining.
[INFO] Fetching p2.index (116B of 92B at 0B/s) from http://download.eclipse.org/technology/epp/packages/kepler/
[INFO] Adding repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site
[INFO] Adding repository http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site
[INFO] Resolving dependencies of MavenProject: org.jboss.reddeer:org.jboss.reddeer.swt:0.2.0-SNAPSHOT @ /Users/rasp/git/reddeer/org.jboss.reddeer.swt/pom.xml
[INFO] Downloading org.junit4
[INFO] Fetching download.php (0B of 1,74kB at 0B/s) from http://www.eclipse.org/downloads/download.php?format=xml&file=/releases/k...
[INFO] Fetching download.php (1,45kB of 1,74kB at 0B/s) from http://www.eclipse.org/downloads/download.php?format=xml&file=/releases/k...
{code}
And eventually junit4 was fetched from here:
{code}
[INFO] Fetching org.junit4_4.8.1.v20120705-112236.jar.pack.gz (0B of 6,18kB at 0B/s) from http://eclipse.c3sl.ufpr.br/releases/kepler/201302080900/plugins/
[INFO] 1 operation remaining.
[INFO] Fetching org.junit4_4.8.1.v20120705-112236.jar.pack.gz (2,55kB of 6,18kB at 0B/s) from http://eclipse.c3sl.ufpr.br/releases/kepler/201302080900/plugins/
{code}
Do you understand why it works like that? Is there a pure M6 p2 repo on eclipse.org?
Maybe we should move to using JBT TP instead.
> SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13843
> URL: https://issues.jboss.org/browse/JBIDE-13843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.0.Alpha2
>
>
> Eclipse 4.3M5a contains:
> {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code}
> But in Eclipse 4.3M6, the only JUnit available is:
> {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code}
> So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4.
--
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-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13599:
---------------------------------------
I have added javadocs, checked and applied Denis's PR.
As I know, there is no any issue anymore.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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 RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13818:
-------------------------------------------------
Bill DeCoste <wdecoste(a)redhat.com> made a comment on [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369]
Modified killtree logic
> 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