[JBoss JIRA] (JBIDE-20966) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20966?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20966.
---------------------------------
Done.
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Central]
> ---------------------------------------------------------
>
> Key: JBIDE-20966
> URL: https://issues.jboss.org/browse/JBIDE-20966
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Central]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21194) Result from adbinfo on windows has different syntax
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21194?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21194.
---------------------------------
This is done and working the way Rob described. If you want it to be done differently, please create a new JIRA.
> Result from adbinfo on windows has different syntax
> ---------------------------------------------------
>
> Key: JBIDE-21194
> URL: https://issues.jboss.org/browse/JBIDE-21194
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift, server
> Affects Versions: 4.3.0.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> The result from adbinfo on linux is:
> {code}
> export key=value
> {code}
> The result on Windows is:
> {code}
> setx key value
> {code}
> The adbinfo runner needs to be aware of this difference and react accordingly when creating the openshift connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21175) [CDK] Require better logic to find vagrant.exe / vagrant command
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21175?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21175.
---------------------------------
This works properly on Windows now. There is an open JIRA for mac though.
> [CDK] Require better logic to find vagrant.exe / vagrant command
> ----------------------------------------------------------------
>
> Key: JBIDE-21175
> URL: https://issues.jboss.org/browse/JBIDE-21175
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift, server
> Affects Versions: 4.3.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> First step to support for windows is properly locating vagrant.exe. This isn't a windows-only issue, though, as [~mmalina] has already commented that his vagrant was in /usr/local/bin/vagrant rather than /usr/bin/vagrant
> So this is a concern on all OSes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20738) JMX Navigator Refresh Command is running in main UI Thread
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20738?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20738:
---------------------------------------
[~rob.stryker], is there an easy way to verify? I never had a problem with this. And is this refresh in the JMX navigator view, or properties of a connected JVM process?
> JMX Navigator Refresh Command is running in main UI Thread
> ----------------------------------------------------------
>
> Key: JBIDE-20738
> URL: https://issues.jboss.org/browse/JBIDE-20738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Refresh in JMX Navigator freezes UI because executed in main UI thread:
> {code}Thread [main] (Suspended (breakpoint at line 435 in org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm))
> owns: org.jboss.tools.jmx.local.internal.JvmConnectionWrapper (id=162)
> org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(javax.management.remote.JMXServiceURL) line: 435
> org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(java.lang.String, int) line: 465
> org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize() line: 445
> org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int, boolean) line: 233
> org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int) line: 213
> org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect() line: 121
> org.jboss.tools.jmx.ui.internal.actions.RefreshAction.refreshObjectNode(java.lang.Object) line: 107
> org.jboss.tools.jmx.ui.internal.actions.RefreshAction.run() line: 153
> org.jboss.tools.jmx.ui.internal.actions.RefreshAction(org.eclipse.jface.action.Action).runWithEvent(org.eclipse.swt.widgets.Event) line: 473
> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(org.eclipse.swt.widgets.Event, boolean) line: 595
> org.eclipse.jface.action.ActionContributionItem.access$2(org.eclipse.jface.action.ActionContributionItem, org.eclipse.swt.widgets.Event, boolean) line: 511
> org.eclipse.jface.action.ActionContributionItem$5.handleEvent(org.eclipse.swt.widgets.Event) line: 420
> org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84
> org.eclipse.swt.widgets.Display.sendEvent(org.eclipse.swt.widgets.EventTable, org.eclipse.swt.widgets.Event) line: 4481
> org.eclipse.swt.widgets.MenuItem(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1327
> org.eclipse.swt.widgets.Display.runDeferredEvents() line: 3819
> org.eclipse.swt.widgets.Display.readAndDispatch() line: 3430
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() line: 1127
> org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(org.eclipse.e4.ui.model.application.MApplicationElement, org.eclipse.e4.core.contexts.IEclipseContext) line: 1018
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(org.eclipse.e4.ui.model.application.MApplicationElement) line: 156
> org.eclipse.ui.internal.Workbench$5.run() line: 654
> org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 598
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 150
> org.eclipse.ui.internal.ide.application.IDEApplication.start(org.eclipse.equinox.app.IApplicationContext) line: 139
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 196
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 134
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 104
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 380
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 235
> sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method]
> sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 43
> java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 497
> org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 669
> org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 608
> org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1515
> org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1488
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months