[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21193.
---------------------------------
{quote}One line fix was to revalidate later in the workflow, because all runtime detectors are asked to initialize all possible runtime definitions, not just the runtime definitions they created.{quote}
I don't really see why the cdk runtime detector doesn't ignore the paths that don't have a .cdk marker. Same way jboss runtime detectors will not create seam runtimes. Do they also revalidate later in the workflow?
But anyway, it is fixed now, the mutant servers are not created in jboss-devstudio-9.1.0.Beta1-v20151210-0557-B177-installer-standalone.jar
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21288) Add Manage Projects link to Deploy Docker Image dialog
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21288:
-------------------------------------
Summary: Add Manage Projects link to Deploy Docker Image dialog
Key: JBIDE-21288
URL: https://issues.jboss.org/browse/JBIDE-21288
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.CR1
Reporter: Marián Labuda
Assignee: Fred Bricon
Fix For: 4.3.1.Beta1
If there is no project for a OpenShift 3 connection it is not possible to proceed through Deploy Docker Image dialog opened via context menu of a OpenShift 3 connection. Because combo box for an OpenShift Project is empty and there is no Manage Projects link, one similar to the one in New OpenShift Application wizard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21288) Add Manage Projects link to Deploy Docker Image dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21288?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21288:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta1)
> Add Manage Projects link to Deploy Docker Image dialog
> ------------------------------------------------------
>
> Key: JBIDE-21288
> URL: https://issues.jboss.org/browse/JBIDE-21288
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: docker
> Fix For: 4.4.0.Alpha1
>
>
> If there is no project for a OpenShift 3 connection it is not possible to proceed through Deploy Docker Image dialog opened via context menu of a OpenShift 3 connection. Because combo box for an OpenShift Project is empty and there is no Manage Projects link, one similar to the one in New OpenShift Application wizard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21288) Add Manage Projects link to Deploy Docker Image dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21288?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21288.
-----------------------------------
Resolution: Done
> Add Manage Projects link to Deploy Docker Image dialog
> ------------------------------------------------------
>
> Key: JBIDE-21288
> URL: https://issues.jboss.org/browse/JBIDE-21288
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: docker
> Fix For: 4.4.0.Alpha1
>
>
> If there is no project for a OpenShift 3 connection it is not possible to proceed through Deploy Docker Image dialog opened via context menu of a OpenShift 3 connection. Because combo box for an OpenShift Project is empty and there is no Manage Projects link, one similar to the one in New OpenShift Application wizard.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20093) Application wizard: I cannot browse workspace when using local template/json
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20093?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20093.
---------------------------------
Verified on nightly build with OpenShift tooling of version 20151210-0635-B114.
> Application wizard: I cannot browse workspace when using local template/json
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20093
> URL: https://issues.jboss.org/browse/JBIDE-20093
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta1
>
> Attachments: templates-from-local-filesystem.png
>
>
> if I have projects cloned in openshift with kubernetes.json or templates I can't load them from the openshift app wizard.
> The wizard forces me to use the local file system which is rather limiting.
> Suggestion: support both workspace/filesystem buttons.
> Steps:
> # EXEC: launch New application wizard for v3 (create app from template)
> # ASSERT: application wizard pops up
> # EXEC: choose "Use a template from local filesystem", hit "Browse"
> !templates-from-local-filesystem.png!
> Result:
> I can browse the local filesystem
> Expected
> I would like to be able to pick a template from a workspace project
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21080) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21080.
---------------------------------
Verified in nightly build with OpenShift tooling of version 20151210-0635-B114.
> Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21080
> URL: https://issues.jboss.org/browse/JBIDE-21080
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.Beta1
>
>
> There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller).
> I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-3562.
-------------------------------
I believe everything is done here. Closing.
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21200) Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21200?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-21200:
-------------------------------------------
Fix Version/s: 4.3.1.Beta1
(was: 4.3.0.Beta1)
> Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21200
> URL: https://issues.jboss.org/browse/JBIDE-21200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Beta1
> Environment: Mac OS
> Reporter: Pavol Srna
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Right Click on 'user' text within <h:inputText> tag
> {code}
> org.eclipse.core.runtime.CoreException: Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem".
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:872)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:234)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:227)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:206)
> at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:724)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:806)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:665)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1164)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:636)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:313)
> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:56)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(EcoreEList.java:249)
> at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:356)
> at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:341)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.mergeIntoModel(ContributionRecord.java:250)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processAddition(MenuManagerRenderer.java:554)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.generateContributions(MenuManagerRenderer.java:529)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContributions(MenuManagerRenderer.java:494)
> at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:409)
> at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:381)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:811)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5746)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:280)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4149)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3691)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem.<init>(SetupTemplateContributionItem.java:55)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> ... 81 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21277) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [BrowserSim]
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21277?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov closed JBIDE-21277.
------------------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [BrowserSim]
> --------------------------------------------------------
>
> Key: JBIDE-21277
> URL: https://issues.jboss.org/browse/JBIDE-21277
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: browsersim
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [BrowserSim]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. 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, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim 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, 4 months
[JBoss JIRA] (JBIDE-21214) Domain modification via Credential preferences page doesn't work
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21214?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21214:
-------------------------------------
Good catch. That button probably shouldn't even be enabled. It's only purpose is to change the default username for that domain. Renaming of domains isn't currently supported.
> Domain modification via Credential preferences page doesn't work
> ----------------------------------------------------------------
>
> Key: JBIDE-21214
> URL: https://issues.jboss.org/browse/JBIDE-21214
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: Fedora 22 KDE 64 bit
> Reporter: Vlado Pakan
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> 1. Open Window > Preferences > JBoss Tools > Creddentials
> 2. Add Domain
> 3. Modify domain via Edit button and choose OK
> ERROR: Domain is not modified it shows previous domain name in prefences page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months